No. Resend returns a success response when it accepts the request. Provely proves accepted, bounced, delivered and sent as separate promises.

Skill facts from the signed manifest.
FactValue
Skill version0.1.0
PublisherBuilt and signed by Provely.
CertificationProvisional
Last conformance run2026-09-05T12:00:00Z: 62 of 62 cases passed, 0 critical false VERIFIED
Provider API versions1.5.1
Default provider API version1.5.1
Compiled2026-09-05
Manifest hash69f6f52647c24887
Manifest hash checkthe document hashes to the value the manifest states
Signaturevalid, key provely-skill-2026-09, trusted by this build

What does this page prove?

ClaimProven byEvidenceStatus
The accepted level proves that Resend holds an email record for the request. It does not prove that the message left the provider.resend.email.acceptedE2proven
The bounced level proves the bounced state on the email record and the email.bounced event. Use it when the intent is to confirm a rejection, for example before a suppression.resend.email.bouncedE2 + E3proven
The delivered level proves the delivered state on the email record and the email.delivered event. It does not prove that a person read the message. This level needs the email.delivered webhook.resend.email.deliveredE2 + E3proven
The sent level proves the email.sent event of this email. It does not prove that the recipient mail server accepted the message. This level needs the email.sent webhook.resend.email.sentE2 + E3proven
An outcome outside Resend, such as a bank credit or a person who read a messagenot provenno E5 channelnot proven
The agent report that the action workednever countsE0not proven

Which completion levels does the Resend skill expose?

Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.

LevelContractPromiseEvidenceCertification
acceptedresend.email.accepted v1.0.0The accepted level proves that Resend holds an email record for the request. It does not prove that the message left the provider.E2Provisional
bouncedresend.email.bounced v1.0.0The bounced level proves the bounced state on the email record and the email.bounced event. Use it when the intent is to confirm a rejection, for example before a suppression.E2 + E3Generated draft
deliveredresend.email.delivered v1.0.0The delivered level proves the delivered state on the email record and the email.delivered event. It does not prove that a person read the message. This level needs the email.delivered webhook.E2 + E3Generated draft
sentresend.email.sent v1.0.0The sent level proves the email.sent event of this email. It does not prove that the recipient mail server accepted the message. This level needs the email.sent webhook.E2 + E3Generated draft

Which ways can a Resend action look done and not be?

ContractCaseVerdict
resend.email.acceptedduplicate side effectCONTRADICTED
resend.email.acceptedpartial completionCONTRADICTED
resend.email.acceptedpre existing stateCONTRADICTED
resend.email.acceptedwrong subjectCONTRADICTED
resend.email.bouncedduplicate side effectCONTRADICTED
resend.email.bouncedpartial completionCONTRADICTED
resend.email.bouncedpre existing stateCONTRADICTED
resend.email.bouncedwrong subjectCONTRADICTED
resend.email.deliveredduplicate side effectCONTRADICTED
resend.email.deliveredpartial completionCONTRADICTED
resend.email.deliveredpre existing stateCONTRADICTED
resend.email.deliveredwrong subjectCONTRADICTED
resend.email.sentduplicate side effectCONTRADICTED
resend.email.sentpartial completionCONTRADICTED
resend.email.sentpre existing stateCONTRADICTED
resend.email.sentwrong subjectCONTRADICTED

What did the last conformance run show?

The last conformance run on 2026-09-05T12:00:00Z passed 62 of 62 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.

The certification of each contract.
ContractCertification
resend.email.acceptedProvisional
resend.email.bouncedGenerated draft
resend.email.deliveredGenerated draft
resend.email.sentGenerated draft

The weakest contract is resend.email.accepted. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.

The conformance result by case class.
Case classPassedTotal
duplicate side effect55
error after execution44
error before execution44
evidence unavailable55
idempotent retry44
pre existing state44
stale readback44
still transitional44
terminal failure44
terminal success44
timeout after commit44
version mismatch44
webhook duplicate44
webhook out of order44
wrong subject44

The conformance artifact digest is 2d50bca3d2409f10. The harness signs the run, so a reader can check that these numbers come from that run.

What remains uncertain?

The level is Provisional because of it. Provely does not guess a rule that a source does not state.

What happens to a Resend verdict when Resend is down?

Nothing changes about the verdict. Provely records whether Resend answered when it read it, and it reads what Resend publishes about itself. Both explain an answer. Neither decides one. Read how Provely records integration uptime.

Resend publishes a machine-readable status document at https://resend-status.com/api/v2/summary.json. Provely reads it on a schedule and stores what it says. A Statuspage v2 summary document. The page is not hosted by Atlassian, and it answers the same shape.

Source: Resend status page · retrieved 2026-09-07

A Resend status page is second-hand. It is often late, and it is often narrower than the outage. A verdict never rests on it.

Where do these facts come from?

Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.

SourceKindRetrievedExcerpt
resend.docs.idempotencydocs2026-09-05authored
resend.docs.webhooksdocs2026-09-05authored
resend.openapiopenapi2026-09-05trimmed

How do I verify a Resend action?

Verify a Resend action with Provely

  1. Begin the operation.Call begin with the contract resend.email.accepted and the input. Keep the operation id and the idempotency key.
  2. Make the Resend call you make today.Send the Idempotency-Key header with the key that begin returned. A retry then cannot create a second side effect.
  3. Submit the acknowledgement.Call action_result with the Resend response. This is evidence level E1. It is not completion.
  4. Verify.Call verify. The runtime reads the evidence that the contract names, from Resend and not from the agent, and evaluates the contract.
  5. Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.

Questions developers ask

Does the accepted level prove the sent level?

No. The accepted level proves that Resend holds an email record for the request. It does not prove that the message left the provider. The sent level proves the email.sent event of this email. It does not prove that the recipient mail server accepted the message. This level needs the email.sent webhook. Use resend.email.sent to prove sent.

What does the agent say while the Resend action is still in progress?

It says: "The action is accepted but not yet verified. Operation: <id>." The verdict is PENDING. The runtime observes again on the contract timing policy.

Which Resend API versions does the skill support?

1.5.1. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.

Does Provely need write access to Resend?

No. The agent keeps its write key. The verifier reads with a separate read-only credential where Resend permits it, and it never shares that credential with the agent.