ProvelyProve 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.
| Fact | Value |
|---|---|
| Contract id | resend.email.accepted |
| Version | 1.0.0 |
| Hash | c8227388e474f64c |
| Completion level | accepted |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Resend 0.1.0 |
| Valid for provider API versions | 1.5.1 |
What is the intent?
Hand the email to Resend.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | resend.email |
| Canonical effect | message.send |
| Provider operation | POST /emails |
| Idempotency | idempotency_key through Idempotency-Key, retry is safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- partial completion
- pre existing state
- wrong subject
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
resend.openapi#/paths/~1emails/post: resend.openapi, retrieved 2026-09-05resend.openapi#/paths/~1emails/post/responses/200: resend.openapi, retrieved 2026-09-05resend.openapi#/paths/~1emails~1{email_id}/get: resend.openapi, retrieved 2026-09-05resend.openapi#/components/schemas/Email/properties/created_at: resend.openapi, retrieved 2026-09-05resend.openapi#/components/schemas/Email/properties/id: resend.openapi, retrieved 2026-09-05resend.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 action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from Resend.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation ends.