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.
Resend / active
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayLimited
- ProvisionReady
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
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.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
Resend's Terms of Service state that the service is intended for access and use by individuals who are at least eighteen years old and possess full legal authority, right, and capacity to enter into the agreement.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Resend explicitly provides pricing details including a free tier, explicit add-on pricing such as $20/month for domains and $30/month for dedicated IPs, as well as pay-as-you-go rates for emails beyond quotas and automations ($0.0015 per run).
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
Resend's API reference documents the service introduction, stating that all requests use HTTPS and the stable base URL https://api.resend.com, with Bearer token authentication.
Are verified structured discovery artifacts available?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
The Terms of Service are retrievable and readable, explicitly defining the Agreement between Plus Five Five, Inc. and the User governing the use of resend.com services.
Does the vendor deliberately describe access for web agents?
missing: unknownCurrent admissible evidence does not resolve this finding.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
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: freshCurrent admissible evidence does not resolve this finding.
The sign-up page displays an email and password registration form with password requirements, but the retained evidence does not establish whether an agent can complete the access controls, navigation, validation, and handoffs deterministically.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
A stable canonical route to begin obtaining access exists at https://resend.com/signup, which provides a 'Create a Resend account' registration form with email/password and social login options.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
No CAPTCHA challenge is directly observed on the captured sign-up page targets, but the evidence does not explicitly confirm or guarantee the complete absence of CAPTCHA across the entire registration flow.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Resend provides scoped, revocable API keys with permissions such as full_access or sending_access that can be created and managed via the dashboard, CLI, or API, but obtaining initial dashboard keys requires manual human copying as key values cannot be viewed or edited after creation.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The captured registration form does not mention or display phone verification, but the retained evidence does not explicitly declare whether phone verification is absent, optional, or required later in the flow.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
Self-service is tier- or condition-limited, or a bounded vendor review exposes status.
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: freshCurrent admissible evidence does not resolve this finding.
The documentation states that users can upgrade, downgrade, or modify their current plan from the Billing page, but the retained evidence does not document a deterministic flow for an agent to construct checkout, hand off approval safely, and resume.
Is the exact commercial commitment disclosed before authorization?
supported: freshCharge or no-charge status, currency, recurrence, and material conditions are disclosed.
Resend discloses commercial commitments including a Free plan ($0/mo for 3,000 emails/mo), a Pro plan ($20/mo for 50,000 emails/mo with overage at $0.90 / 1,000), a Scale plan ($90/mo for 100,000 emails/mo with overage at $0.90 / 1,000), and pay-as-you-go automation runs ($0.0015 / run).
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The evidence notes that users can update payment information by adding or changing credit card details on the Billing page, but it does not detail a rail for scoped delegation or human-confirmed payment authorization.
Is a direct self-service path to paid access documented?
supported: freshSelf-service is tier- or condition-limited, or a bounded vendor review exposes status.
Resend provides a direct self-service path to upgrade or manage subscriptions via the Billing page in Settings, but the top-tier Enterprise plan requires contacting sales ("Contact us").
What would improve this stage
- Document a direct purchase path or bounded vendor review with machine-readable status.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
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: freshCredentials, grants, or configuration are delivered through a documented agent-usable flow.
Resend documents programmatic delivery of newly created API keys via HTTP POST request responses, returning the secret token string in the JSON payload.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshA synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
The synchronous POST /emails API endpoint immediately returns a JSON response containing the created email's usable ID upon successful request completion.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
API keys and email sending operations can be programmatically triggered via direct HTTP requests, the Resend CLI, or official API SDKs.
Only part of the credential lifecycle is agent-operable.
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?
missing: unknownCurrent admissible evidence does not resolve this finding.
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Resend documents that API keys can be created, edited (name, permission, domain), listed, and deleted via the Dashboard, API, or CLI. However, the evidence does not document programmatic secret rotation, compromise recovery, or key value viewing after creation.
Can an agent handle applicable failure modes safely?
supported: freshApplicable limits, errors, retry, idempotency, cancellation, and reconciliation semantics are documented.
Resend documents HTTP status codes, explicit error types (e.g., validation_error, rate_limit_exceeded), retry actions, idempotency key rules, and rate limit reduction mechanisms.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
Resend documents request-time authentication using API keys sent as Bearer tokens in the Authorization header, with options for restricted authority such as sending-only access.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Resend documents stable operation contracts including HTTP methods, endpoints, required request body parameters, response JSON schemas, and structured error responses across errors and send-email resources.
- email-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Resend provides stable machine-operable interfaces including an HTTP REST API, CLI, and SDKs (such as Node.js, Python, Go, and Ruby) for both error handling and email sending targets.
- email-api
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
- 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.
Startup offers
Resend on the startup-offers board
- $25,000 in credits for 12 months$25,000 in credits for current YC batch
- $15,000 in credits for YC alumni$15,000 in credits for YC alumni
Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4xg7f2qx5a9t4kn8yc1
- Projection
- sha256:82f3b6ab6fc04247020755cbe8f682750d0469c061980d51a9529bcf0c982167
- Policy
- service-use-2026-08-20-public-evidence-r9 · sha256:57bf95fd6d0fe6fe9173a68b60e8d8dc2179b357c88ff4349675a72d0e1d4139
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration