Provenance
observed · 7 Aug
Freshness
fresh
Dispute
none
Revision
sha256:aebd33dc0dab…

Agent report card

Can an agent use Resend Email API through Email operations?

Grade B: Only part of the applicable terms is machine-readable.

Resend / active

Agent ReadinessBLimited
Coverage
complete: 11/11
Freshness
fresh
Last tested
Evidence
observed: not disputed

Five-stage assessment

Where agent autonomy holds and where it breaks

First break: Evaluate

  1. Evaluate

    Limited

    Only part of the applicable terms is machine-readable.

    An ARD declaration has not been established.

    An agent can discover the product and funnel from the tested public entrypoints.

    Eligibility can be decided from explicit public criteria.

    Pricing or the absence of a charge is explicit and machine-readable.

    Evidence and actions

    ARD declaration unknown

    missing: unknown

    An ARD declaration has not been established.

    ard_declaration: Unknown

    Decidable eligibility

    supported: fresh

    Eligibility can be decided from explicit public criteria.

    Resend's Terms of Service explicitly define eligibility requirements, such as requiring users to be at least 18 years old and capable of forming a binding contract.

    decidable_eligibility: Ready: tested 7 Aug

    Method http 1

    Machine discovery

    supported: fresh

    An agent can discover the product and funnel from the tested public entrypoints.

    Machine discovery of Resend's Email API endpoints, base URLs, and parameters is clearly available from the API reference documentation.

    machine_discovery: Ready: tested 7 Aug

    Method http 1

    Readable pricing

    supported: fresh

    Pricing or the absence of a charge is explicit and machine-readable.

    Pricing tiers, monthly email allocations, and overage pay-as-you-go rates are explicitly documented on the pricing page.

    readable_pricing: Ready: tested 7 Aug

    Method http 1

    Structured terms limited

    supported: fresh

    Only part of the applicable terms is machine-readable.

    Terms of service are available as standard readable HTML web documents rather than a dedicated machine-readable structured format like JSON/schema.

    structured_terms: Limited: tested 7 Aug

    Method http 1

    What would improve this stage

    • Publish complete applicable terms in a stable machine-readable document.

  2. Sign up

    Limited

    The identity flow is only partly supported or requires human intervention.

    A stable signup entrypoint is available.

    The tested signup flow exposes machine-operable controls.

    No CAPTCHA was encountered on the tested signup path.

    The tested signup path does not require phone or SMS verification.

    Evidence and actions

    CAPTCHA-free signup

    supported: fresh

    No CAPTCHA was encountered on the tested signup path.

    The Resend signup page loaded directly with email and password input fields and social sign-in options without presenting a CAPTCHA challenge.

    captcha_free: Ready: tested 7 Aug

    Method headless 1

    Machine-operable signup

    supported: fresh

    The tested signup flow exposes machine-operable controls.

    The signup page presents explicit machine-operable input fields for email and password along with a submission trigger.

    machine_operable_form: Ready: tested 7 Aug

    Method headless 1

    Phone-free signup

    supported: fresh

    The tested signup path does not require phone or SMS verification.

    The signup form requires only email and password inputs or OAuth options without requesting phone or SMS verification.

    phone_verification_free: Ready: tested 7 Aug

    Method headless 1

    Stable signup entrypoint

    supported: fresh

    A stable signup entrypoint is available.

    A stable HTTP signup page is directly accessible at https://resend.com/signup.

    stable_entrypoint: Ready: tested 7 Aug

    Method http 1

    Supported identity flow limited

    supported: fresh

    The identity flow is only partly supported or requires human intervention.

    Resend documents scoped API key permissions and key creation, but initial account setup and key management require interactive dashboard or team admin actions.

    supported_identity_flow: Limited: tested 7 Aug

    Method headless 1

    What would improve this stage

    • Provide scoped, revocable machine authorization and document every required human approval boundary.

  3. Pay

    Ready

    The required price or no-charge status is explicit before commitment.

    Machine-operable checkout has not been established.

    A supported payment rail has not been established.

    The tested funnel can complete without sales intervention.

    Evidence and actions

    Explicit price

    supported: fresh

    The required price or no-charge status is explicit before commitment.

    Resend explicitly states monthly plan pricing on its pricing page, including Free at $0/mo, Pro at $20/mo, Scale at $90/mo, and explicit overage rates.

    explicit_price: Ready: tested 7 Aug

    Method http 1

    Machine-operable checkout unknown

    supported: fresh

    Machine-operable checkout has not been established.

    The signup page provides initial registration forms, but full machine-operable billing checkout controls are not established in the provided evidence.

    machine_operable_checkout: Unknown: tested 7 Aug

    Method headless 1

    Sales-free purchase

    supported: fresh

    The tested funnel can complete without sales intervention.

    Users can sign up directly via self-service account registration without requiring sales intervention.

    sales_intervention_free: Ready: tested 7 Aug

    Method headless 1

    Supported payment rail unknown

    supported: fresh

    A supported payment rail has not been established.

    Payment rail availability during the billing checkout flow is not established in the provided signup evidence.

    supported_payment_rail: Unknown: tested 7 Aug

    Method headless 1

  4. Provision

    Ready

    Usable credentials or delegated access are delivered through a documented flow.

    Automatic activation has not been established.

    A bounded provisioning delay has not been established.

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Evidence and actions

    Automatic activation unknown

    supported: fresh

    Automatic activation has not been established.

    The retained evidence does not establish whether automatic activation occurs upon onboarding.

    automatic_activation: Unknown: tested 7 Aug

    Method headless 1

    Bounded provisioning delay unknown

    supported: fresh

    A bounded provisioning delay has not been established.

    The evidence does not document a specific bounded delay guarantee for account or email resource provisioning.

    bounded_delay: Unknown: tested 7 Aug

    Method http 1

    Credential delivery

    supported: fresh

    Usable credentials or delegated access are delivered through a documented flow.

    API keys are secret tokens created and managed via the dashboard, API, or CLI to authenticate requests.

    credential_delivery: Ready: tested 7 Aug

    Method headless 1

    Machine-readable provisioning status

    supported: fresh

    Provisioning exposes machine-readable progress, terminal states, and reconciliation.

    Email sending responses return a machine-readable JSON payload containing a unique resource identifier.

    machine_readable_status: Ready: tested 7 Aug

    Method http 1

  5. Operate

    Ready

    A documented API or tool interface is available for operation.

    An agent protocol interface has not been established.

    Authentication is documented and usable within an agent authorization boundary.

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Evidence and actions

    Agent protocol interface unknown

    missing: unknown

    An agent protocol interface has not been established.

    agent_protocol_interface: Unknown

    API or tool access

    supported: fresh

    A documented API or tool interface is available for operation.

    Resend provides a documented REST API interface at api.resend.com supporting endpoints for sending emails, managing domains, API keys, and webhooks.

    api_tool_access: Ready: tested 7 Aug

    Method http 1

    Delegated recovery

    supported: fresh

    Credential rotation, revocation, retry, and recovery paths are documented within delegated authority.

    Resend documents programmatic API key lifecycle management including creating, listing, and deleting keys via API and CLI, alongside token revocation endpoints.

    delegated_recovery: Ready: tested 7 Aug

    Method http 1

    Documented limits and errors

    supported: fresh

    Limits, structured errors, retry behavior, and idempotency semantics are documented where applicable.

    Resend documents structured error responses, rate limits, HTTP status codes, and support for Idempotency-Key headers on email requests.

    documented_limits_errors: Ready: tested 7 Aug

    Method http 1

    Usable authentication

    supported: fresh

    Authentication is documented and usable within an agent authorization boundary.

    Resend uses Bearer token authentication with API keys passed in the HTTP Authorization header for API requests.

    usable_authentication: Ready: tested 7 Aug

    Method http 1

What works

  • Pay: The required price or no-charge status is explicit before commitment.
  • Provision: Usable credentials or delegated access are delivered through a documented flow.
  • Operate: A documented API or tool interface is available for operation.

What blocks agents

  • Evaluate: Only part of the applicable terms is machine-readable.
  • Sign up: The identity flow is only partly supported or requires human intervention.

Improve the report

Correct it, rerun it, or improve the funnel

Every request carries the exact profile revision, projection, declaration, and Catalog release.

Report outdated evidenceRequest reassessmentClaim this vendorView the exact declaration
Method, policy, and immutable identifiers

Complete, fresh evidence for the core service lifecycle first applies hard stage severity, then grades the share of applicable evidenced signals that are constrained. Optional blocker probes affect the grade when established and remain visible as unknown when public evidence cannot establish them.

Any incomplete, contradictory, unsupported, or non-fresh required evidence produces an unrated profile. A failed Evaluate, Sign up, or Pay stage derives D; a failed Provision or Operate stage derives F; otherwise constrained-signal ratio derives A+ through C.

Profile ID
arp_01kzf0m4xg7f2qx5a9t4kn8yc1
Revision
sha256:aebd33dc0dab9bde3927139d2d3bd5e8a9175d808431b5302cdc3caf4aa41a41
Projection
sha256:d419b2a8c22f5c9b4cc34778dd1de4ea41c6d69a349408c13df6201eb1934c90
Policy
service-lifecycle-2026-08-08-calibrated: sha256:334e56852b5c38e178fcea839cfba680fb82dd96693842d933776baed21d63df
Base Catalog release
sha256:5082ec07047a2324648f569d234cc64342ce2707b2f3d77fde8fc06af517cee6