Agent mandate authority

AP2 Mandate Gateway.

Accept AP2-style mandate references, check bounded authority, and bind the mandate to rail run receipt proof.

Use it for:AP2-style mandate authority for rail access.
How agents use it

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

Agents submit mandate authority fields, receive an authority decision, and bind the mandate reference to the rail run, receipt, and return package.

modes

Available modes

  • read_schema
  • parse_mandate
  • bind_mandate_to_receipt
required

Required fields

mandate_reference, agent_id, merchant_reference, rail_key

returns

Return fields

mandate_id, mandate_state, allowed_merchant, allowed_rail, receipt_binding_hash, reason

Example

Start with the public API.

GET /api/ap2-mandate-gateway returns the schema, operating boundary, payment access fields, and a sample object. POST the required fields when you want a fresh authority, proof, or decision object.

curl https://weverlabs.com/api/ap2-mandate-gateway

curl -X POST https://weverlabs.com/api/ap2-mandate-gateway \
  -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.