Prove that Resend accepted the email request. The accepted level proves that Resend holds an email record for the request. It does not prove that the message left the provider.

Contract identity.
FactValue
Contract idresend.email.accepted
Version1.0.0
Hashc8227388e474f64c
Completion levelaccepted
CertificationCommunity
SkillResend 0.1.0
Valid for provider API versions1.5.1

What is the intent?

Hand the email to Resend.

What is the subject and the action?

MemberValue
Subject typeresend.email
Subject identityemail_id = $action.result.id
Canonical effectmessage.send
Provider operationPOST /emails
Idempotencyidempotency_key through Idempotency-Key, retry is safe

How does the evidence correlate with this operation?

StrategyAssuranceKeysRequired
resource_idstrongemail_id from $action.result.idyes
idempotency_keystrongidempotency_key from $operation.idno
fingerprintweakto from $input.to; subject from $input.subjectno

Which evidence does the contract require?

Minimum evidence level E2. An independent channel is required. Minimum channels: 1.

ChannelLevelIndependenceVerifierDescription
email_readbackE2provider readbackhttpRead the email record. The http verifier returns the parsed Email object, so a condition path is $observed.email_readback.last_event.
sent_events_by_intentE3provider eventwebhookThe email.sent events for the same recipient and subject since the operation started. A count above one shows a second send. The webhook verifier returns {events, count, latest, earliest, types, duplicates_dropped}, so a condition reads the count.

Which conditions must all hold for VERIFIED?

ConditionMeaningPathOperatorExpectedEvidence
record_created_in_windowThe provider created the email record after the operation started.$observed.email_readback.created_attime_after$operation.created_atemail_readback
record_presentThe provider holds the email record with the returned id.$observed.email_readback.ideq$action.result.idemail_readback

Which conditions give CONTRADICTED?

ConditionClassReasonPathOperatorExpected
wrong_recipientwrong subjectThe message went to a different recipient.$observed.email_readback.tone$input.to
record_predates_operationpre existing stateThe provider record is older than the operation. It proves nothing.$observed.email_readback.created_attime_before$operation.created_at
more_than_one_recipientpartial completionThe record lists more than one recipient. This contract proves the outcome for one recipient. Use one operation per recipient.$observed.email_readback.toarray_length{"min":2}
duplicate_email_presentduplicate side effectResend sent more than one email for this recipient and subject since the operation started. Do not retry.$observed.sent_events_by_intent.countgt1

Which observed states map to a verdict before completion?

RuleMatchVerdictReason
terminal_failure$observed.email_readback.last_event in ["failed","suppressed"]FAILEDThe provider reports that the message failed, bounced, or was suppressed.
canceled$observed.email_readback.last_event eq "canceled"CONTRADICTEDThe schedule of the message was canceled. The provider will not send it.

How long does the runtime observe?

Timing memberValue
Initial delay2000 ms
Poll interval10000 ms
Backoffexponential factor 2, max 120000 ms
Maximum attempts60
Timeout3600000 ms
Stale read window30000 ms
On timeoutUNVERIFIABLE (evidence_unavailable_before_timeout)

Where do these rules come from?

  • resend.openapi#/paths/~1emails/post: resend.openapi, retrieved 2026-09-05
  • resend.openapi#/paths/~1emails/post/responses/200: resend.openapi, retrieved 2026-09-05
  • resend.openapi#/paths/~1emails~1{email_id}/get: resend.openapi, retrieved 2026-09-05
  • resend.openapi#/components/schemas/Email/properties/created_at: resend.openapi, retrieved 2026-09-05
  • resend.openapi#/components/schemas/Email/properties/id: resend.openapi, retrieved 2026-09-05
  • resend.openapi#/paths/~1emails~1{email_id}/get/responses/200: resend.openapi, retrieved 2026-09-05

Can resend.email.accepted return VERIFIED from the action response alone?

No. The minimum evidence level is E2. The action response is E1. The completion conditions read email_readback.

What happens after the timeout?

The verdict is UNVERIFIABLE with the reason evidence_unavailable_before_timeout. The operation ends.