No. Anthropic Claude API returns a success response when it accepts the request. Provely proves all_succeeded and ended 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: 26 of 26 cases passed, 0 critical false VERIFIED
Provider API versions2023-06-01
Default provider API version2023-06-01
Compiled2026-09-05
Manifest hash1570330057d84a4b
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
A batch that ended is not a batch whose requests succeeded. The level reads request_counts and refuses a batch that holds an error, an expiry, or a cancellation.anthropic.message_batch.all_succeededE2proven
Every request of the batch succeeded, errored, was canceled, or expired. The level proves that the work stopped. It proves no result of any request.anthropic.message_batch.endedE2proven
An outcome outside Anthropic Claude API, 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 Anthropic Claude API 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
all_succeededanthropic.message_batch.all_succeeded v1.0.0A batch that ended is not a batch whose requests succeeded. The level reads request_counts and refuses a batch that holds an error, an expiry, or a cancellation.E2Provisional
endedanthropic.message_batch.ended v1.0.0Every request of the batch succeeded, errored, was canceled, or expired. The level proves that the work stopped. It proves no result of any request.E2Provisional

Which ways can a Anthropic Claude API action look done and not be?

ContractCaseVerdict
anthropic.message_batch.all_succeededduplicate side effectCONTRADICTED
anthropic.message_batch.all_succeededpre existing stateCONTRADICTED
anthropic.message_batch.all_succeededwrong subjectCONTRADICTED
anthropic.message_batch.endedduplicate side effectCONTRADICTED
anthropic.message_batch.endedpre existing stateCONTRADICTED
anthropic.message_batch.endedwrong subjectCONTRADICTED

What did the last conformance run show?

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

The certification of each contract.
ContractCertification
anthropic.message_batch.all_succeededProvisional
anthropic.message_batch.endedProvisional

The weakest contract is anthropic.message_batch.all_succeeded. 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 effect22
error after execution22
error before execution22
evidence unavailable22
pre existing state22
stale readback22
still transitional22
terminal failure22
terminal success33
timeout after commit22
version mismatch22
wrong subject22
wrong terminal state11

The conformance artifact digest is eae45ca3048c69c3. 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.

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
anthropic.docs.batch_objectdocs2026-09-09authored
anthropic.docs.batchesdocs2026-09-09authored
anthropic.docs.filesdocs2026-09-09authored
anthropic.docs.versionsdocs2026-09-09authored
anthropic.openapiopenapi2026-09-09authored

How do I verify a Anthropic Claude API action?

Verify a Anthropic Claude API action with Provely

  1. Begin the operation.Call begin with the contract anthropic.message_batch.all_succeeded and the input. Keep the operation id.
  2. Make the Anthropic Claude API call you make today.Send the request with the correlation metadata that begin returned.
  3. Submit the acknowledgement.Call action_result with the Anthropic Claude API response. This is evidence level E1. It is not completion.
  4. Verify.Call verify. The runtime reads the evidence that the contract names, from Anthropic Claude API 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 all_succeeded level prove the ended level?

No. A batch that ended is not a batch whose requests succeeded. The level reads request_counts and refuses a batch that holds an error, an expiry, or a cancellation. Every request of the batch succeeded, errored, was canceled, or expired. The level proves that the work stopped. It proves no result of any request. Use anthropic.message_batch.ended to prove ended.

What does the agent say while the Anthropic Claude API 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 Anthropic Claude API API versions does the skill support?

2023-06-01. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.

Does Provely need write access to Anthropic Claude API?

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