sourcey
Add your company

agents:log.jsonSKILL.mdmcp.jsonopenapi.yml

← Resend

Agent report card

Can an agent use Resend Email API through Email operations?

Grade B: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

Observedrev sha256:5f0b1a9cbf42…barrier checks 0/5 verified

Agent ReadinessBLimited

Five-stage assessment

Where agent autonomy holds and where it breaks

Five states · each from its own evidence · lifecycle order, not a journey
  1. EvaluateReady
  2. Sign upLimited
  3. PayLimited
  4. ProvisionReady
  5. OperateLimited
  1. 01

    Evaluate

    Ready

    The exact service and stable evaluation or access entrypoints are publicly discoverable.

    Resend documents its RESTful API introduction and base URL as https://api.resend.com, requiring HTTPS and Bearer token authentication with an API Key.

    Applicable terms are stable, readable, retrievable, and materially complete.

    Eligibility conditions and required inputs are explicit and decidable.

    Price or no-charge status, variables, currency, and material conditions are explicit.

    Verified structured artifacts accelerate discovery of the evaluation surface.

    Web-agent access policy is explicit and verified for the assessed resources.

    Evidence and actions6 signals

    Can an agent decide every material eligibility condition before commitment?

    supported: fresh

    Eligibility conditions and required inputs are explicit and decidable.

    Resend's Terms of Service state that the service is intended for individuals at least 18 years old with the full authority, right, and capacity to enter into the agreement.

    eligibility_decidability: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent estimate cost or confirm no-charge status before commitment?

    supported: fresh

    Price or no-charge status, variables, currency, and material conditions are explicit.

    Resend provides explicit pricing details, including a Free tier ($0/mo for 3,000 emails/mo), Pro ($20/mo for 50,000 emails/mo plus $0.90 per 1,000 extra emails), Scale ($90/mo for 100,000 emails/mo plus $0.90 per 1,000 extra emails), and explicit pay-as-you-go automation pricing ($0.0015 per run).

    pricing_decidability: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent find the exact service and its stable entrypoints?

    supported: fresh

    The exact service and stable evaluation or access entrypoints are publicly discoverable.

    Resend documents its RESTful API introduction and base URL as https://api.resend.com, requiring HTTPS and Bearer token authentication with an API Key.

    service_discovery: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Are verified structured discovery artifacts available?

    supported: fresh

    Verified structured artifacts accelerate discovery of the evaluation surface.

    Resend provides a verified structured documentation index artifact at /docs/llms.txt to discover all available pages.

    structured_evaluation_discovery: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent retrieve and understand the applicable commitment terms?

    supported: fresh

    Applicable terms are stable, readable, retrievable, and materially complete.

    Resend makes its complete Terms of Service agreement publicly retrievable and readable at https://resend.com/legal/terms-of-service.

    terms_access: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Does the vendor deliberately describe access for web agents?

    supported: fresh

    Web-agent access policy is explicit and verified for the assessed resources.

    Resend explicitly declares web agent access policy metadata allowing indexing and following (robots: index, follow, googlebot: index, follow).

    verified_web_agent_access: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

  2. 02

    Sign up

    Limited

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    Resend provides machine credentials in the form of API keys with specific permissions (e.g. full access vs sending access) that can be created, updated, and deleted via API or Dashboard, but keys cannot be viewed after creation and manual handling or copying may be involved.

    A stable canonical route begins the required access bootstrap.

    Evidence and actions5 signals

    Can an agent operate the access controls and safe handoffs deterministically?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The Resend sign-up form exposes email and password fields with validation hints and OAuth options; whether the required controls, validation, navigation and handoffs are machine-operable was not established by the single captured page.

    access_control_operability: Unknown: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Is there a stable route to begin obtaining service access?

    supported: fresh

    A stable canonical route begins the required access bootstrap.

    A stable canonical route to begin obtaining service access exists at https://resend.com/signup, featuring a 'Create a Resend account' form.

    access_entrypoint_stability: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent obtain access without an unsupported CAPTCHA boundary?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The Resend sign-up form renders email, password and Google or GitHub options; the captured first page does not establish whether a CAPTCHA appears on submission or a supported agent alternative exists.

    captcha_compatible_access: Unknown: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent obtain scoped, revocable authority for this service?

    supported: fresh

    Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.

    Resend provides machine credentials in the form of API keys with specific permissions (e.g. full access vs sending access) that can be created, updated, and deleted via API or Dashboard, but keys cannot be viewed after creation and manual handling or copying may be involved.

    delegated_identity_access: Limited: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can required phone verification be completed through a supported boundary?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The captured Resend sign-up form shows no phone field; the quotes do not establish whether phone verification appears later in the flow or how such a step would resume.

    phone_verification_compatible: Unknown: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    What would improve this stage

    • Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
  3. 03

    Pay

    Limited

    Self-service is tier- or condition-limited, or a bounded vendor review exposes status.

    Resend provides a documented self-service path to upgrade, downgrade, or modify plans (such as Pro and Scale) via the Billing settings page without vendor review, but Enterprise plans require contacting sales.

    Charge or no-charge status, currency, recurrence, and material conditions are disclosed.

    Evidence and actions4 signals

    Can an agent construct checkout, hand off approval safely, and resume?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The retained evidence for Resend describes managing subscriptions and adding payment methods in the billing settings, but it does not establish deterministic agent checkout construction, bounded authorization handoff, and resumption.

    checkout_operability: Unknown: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Is the exact commercial commitment disclosed before authorization?

    supported: fresh

    Charge or no-charge status, currency, recurrence, and material conditions are disclosed.

    Resend explicitly discloses commercial commitments on its pricing page, including fixed plans ($0/mo Free, $20/mo Pro, $90/mo Scale in USD) and variable pay-as-you-go rates ($0.90 per 1,000 extra emails and $0.0015 per automation run).

    commitment_disclosure: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can payment be authorized within scoped agent or explicit human authority?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The evidence describes updating payment information and credit card details in the Billing section, but it does not document scoped delegation or explicit human-confirmed payment authorization rails with receipts.

    payment_authorization: Unknown: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Is a direct self-service path to paid access documented?

    supported: fresh

    Self-service is tier- or condition-limited, or a bounded vendor review exposes status.

    Resend provides a documented self-service path to upgrade, downgrade, or modify plans (such as Pro and Scale) via the Billing settings page without vendor review, but Enterprise plans require contacting sales.

    self_service_purchase: Limited: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    What would improve this stage

    • Document a direct purchase path or bounded vendor review with machine-readable status.
  4. 04

    Provision

    Ready

    Provisioning is machine-triggerable or follows deterministically from an allowed handoff.

    API keys and email sending operations can be programmatically created and initiated via the documented API and CLI endpoints.

    Credentials, grants, or configuration are delivered through a documented agent-usable flow.

    A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.

    Evidence and actions3 signals

    Can usable access material be delivered securely to an authorized agent?

    supported: fresh

    Credentials, grants, or configuration are delivered through a documented agent-usable flow.

    Resend provides a documented POST /api-keys programmatic endpoint that creates and returns new API key credentials with a 'token' property in a JSON response object.

    access_material_delivery: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent determine successful provisioning completion and reconcile asynchronous failure?

    supported: fresh

    A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.

    The POST /emails endpoint synchronously returns a usable created resource containing an 'id' property upon success.

    provisioning_completion: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can provisioning be initiated within supported agent authority?

    supported: fresh

    Provisioning is machine-triggerable or follows deterministically from an allowed handoff.

    API keys and email sending operations can be programmatically created and initiated via the documented API and CLI endpoints.

    provisioning_operability: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

  5. 05

    Operate

    Limited

    Only part of the credential lifecycle is agent-operable.

    Resend documents programmatically creating, listing, updating names, and deleting API keys via API/CLI, as well as scoping permissions (full_access vs sending_access) and domain restrictions. However, automated credential rotation or secret compromise recovery procedures remain manual or unaddressed.

    Every essential target has a stable documented agent-usable interface alternative.

    Request-time authentication is documented and usable under scoped agent authority.

    Essential operations have stable readable request, response, and effect semantics.

    Applicable limits, errors, retry, idempotency, cancellation, and reconciliation semantics are documented.

    Evidence and actions6 signals

    Is an agent-native protocol interface verified against the essential targets?

    supported: fresh

    Current admissible evidence does not resolve this finding.

    The retained excerpts describe REST or RPC interfaces, SDKs and CLIs for Resend Email API; they contain no first-party statement that an agent-native protocol interface is absent, and several navigation excerpts mention MCP resources without establishing coverage of the assessed targets.

    agent_protocol_interface: Unknown: tested 6 Sept

    • email-api

    Method public-semantic-assessment 2026-09-06

    Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?

    supported: fresh

    Only part of the credential lifecycle is agent-operable.

    Resend documents programmatically creating, listing, updating names, and deleting API keys via API/CLI, as well as scoping permissions (full_access vs sending_access) and domain restrictions. However, automated credential rotation or secret compromise recovery procedures remain manual or unaddressed.

    credential_lifecycle: Limited: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent handle applicable failure modes safely?

    supported: fresh

    Applicable limits, errors, retry, idempotency, cancellation, and reconciliation semantics are documented.

    Resend explicitly documents HTTP response codes, error types, rate limits (429 rate_limit_exceeded with response headers advice), quotas (daily/monthly exceeded), idempotency key requirements and conflict behaviors (409 concurrent_idempotent_requests, invalid_idempotent_request), and retry suggestions.

    failure_contract: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Can an agent authenticate service operations with scoped authority?

    supported: fresh

    Request-time authentication is documented and usable under scoped agent authority.

    Resend documents request-time bearer token authentication using API keys via the 'Authorization: Bearer YOUR_API_KEY' header, supporting scoped authorization such as full_access or restricted sending_access.

    operation_authentication: Ready: tested 6 Sept

    Method public-semantic-assessment 2026-09-06

    Are essential operation inputs, outputs, and effects stable and decidable?

    supported: fresh

    Essential operations have stable readable request, response, and effect semantics.

    Both essential targets (Errors documentation and Send Email endpoint) have defined, stable request methods (POST /emails), schema parameters (from, to, subject, html, template), required fields, HTTP response status codes, and return body structures.

    operation_contract: Ready: tested 6 Sept

    • email-api

    Method public-semantic-assessment 2026-09-06

    Can an agent perform every essential assessment target through a usable interface?

    supported: fresh

    Every essential target has a stable documented agent-usable interface alternative.

    Every essential target has a usable, documented HTTP REST API interface alongside CLI and SDK alternatives.

    target_interface_access: Ready: tested 6 Sept

    • email-api

    Method public-semantic-assessment 2026-09-06

    What would improve this stage

    • Provide scoped expiry, rotation, revocation, compromise, and recovery operations.

What works

  • Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
  • Provision: Provisioning is machine-triggerable or follows deterministically from an allowed handoff.

What blocks agents

No stage is established as blocked.

Where autonomy is limited

  • Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
  • Pay: Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
  • Operate: Only part of the credential lifecycle is agent-operable.

What this grade establishes

14 of 14 graded signals have current supporting evidence. 0 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.

How the grade is derived

A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.

Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.

Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.

Startup offers

Resend on the startup-offers board

catalog record →

Distribution

The grade’s badge

One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.

Live sourcey badge for Resend Agent Readiness grade B
[![sourcey record](https://sourcey.com/badges/agent-readiness/arp_01kzf0m4xg7f2qx5a9t4kn8yc1.svg)](https://sourcey.com/log/resend/agent-readiness/resend-email-api/email-operations)

Improve the report

Correct it, rerun it, or improve the funnel.

Report outdated evidenceRequest reassessmentClaim this record
Profile
arp_01kzf0m4xg7f2qx5a9t4kn8yc1
Projection
sha256:f5e4ec48bff5ded58221cda88edd045d60776714bd1adc2e131b1cf4837c18cc
Policy
service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d

Every request carries these exact identifiers.How report cards are assessed →View the exact declaration