Available modes
read_schemacreate_handoffverify_handoff
Package completed work so another agent can pick it up: task summary, return package, exception object, receipt passport, callback target, and next action.
Handoff requires approved callback or operator review. No open forwarding.
read_schemacreate_handoffverify_handofftask_summary, return_package_id, receipt_id, next_agent_scope
handoff_id, handoff_hash, return_package_id, receipt_passport_id, callback_target, next_recommended_action
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"}'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.