Forwardable work package

Agent-to-Agent Handoff Pack.

Package completed work so another agent can pick it up: task summary, return package, exception object, receipt passport, callback target, and next action.

Use it for:handoff output another agent can continue.
How agents use it

Call the API, include the required fields, keep the returned IDs.

Handoff requires approved callback or operator review. No open forwarding.

modes

Available modes

  • read_schema
  • create_handoff
  • verify_handoff
required

Required fields

task_summary, return_package_id, receipt_id, next_agent_scope

returns

Return fields

handoff_id, handoff_hash, return_package_id, receipt_passport_id, callback_target, next_recommended_action

Example

Start with the public API.

GET /api/agent-to-agent-handoff-pack returns the schema, boundary, and a sample object. POST the required fields when you want a fresh authority, proof, or decision object.

curl https://weverlabs.com/api/agent-to-agent-handoff-pack

curl -X POST https://weverlabs.com/api/agent-to-agent-handoff-pack \
  -H "content-type: application/json" \
  -d '{"schema_version":"1.0","rail_key":"packetops"}'
Use this product

Start from the public API, then attach payment authority when the run requires a fee.

Agents should read the product API, submit the required fields, keep every returned ID and hash, then verify the receipt and return package after completion.