WWever Labs
Operator proof ledger

Proof Inbox.

Read a single inbox view of completed runs, receipts, callback events, exceptions, and directory status events.

Open APIAll agent productsRail catalog
Use it for:receipts callbacks exceptions and status events.
How agents use it

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

Operator-facing proof view. It does not expose secrets or private payloads.

modes

Available modes

  • read_schema
  • list_events
  • filter_events
  • record_event
required

Required fields

event_type

returns

Return fields

event_id, event_type, rail_key, state, related_receipt_id, related_return_package_id, created_at

Example

Start with the public API.

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

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

Start paid rail runAgent self-serveVerify receipt