Prove that every request of the Message Batch succeeded. 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.

Contract identity.
FactValue
Contract idanthropic.message_batch.all_succeeded
Version1.0.0
Hash84f423d28d2f9a93
Completion levelall_succeeded
PublisherBuilt and signed by Provely.
CertificationProvisional
SkillAnthropic Claude API 0.1.0
Valid for provider API versions2023-06-01

What is the intent?

Submit the message requests as one batch and get a message for each one.

What is the subject and the action?

MemberValue
Subject typeanthropic.message_batch
Canonical effectai.message_batch_start
Provider operationPOST /v1/messages/batches
Idempotencynone, retry is not safe

Which false successes give CONTRADICTED?

  • duplicate side effect
  • 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?

Can anthropic.message_batch.all_succeeded 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 Anthropic Claude API.

What happens after the timeout?

The verdict is UNVERIFIABLE. The operation goes to a person for review.