Approved proof transport

Proof Relay.

Receive proof from one agent and relay it to an approved callback receiver with allowlist and audit fields.

Use it for:send proof to an approved callback receiver.
How agents use it

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

Relays proof to approved callback receivers with destination checks, audit events, relay hash, and retry-ready delivery state.

modes

Available modes

  • read_schema
  • evaluate_relay
  • record_relay_attempt
required

Required fields

source_agent_id, destination_agent_id, callback_url, proof_payload_hash

returns

Return fields

relay_id, relay_decision, reason, allowed_callback, audit_event_id, relay_hash

Example

Start with the public API.

GET /api/proof-relay 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/proof-relay

curl -X POST https://weverlabs.com/api/proof-relay \
  -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.