WWever Labs
Proof object

Receipt Passport.

Create a short, portable proof object for a completed rail run. Agents use it to verify receipt state without carrying the full run payload.

Open APIAll agent productsRail catalog
Use it for:portable receipt proof.
How agents use it

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

This creates proof metadata only. It does not custody funds or change settlement state.

modes

Available modes

  • read_schema
  • create_passport
  • verify_passport
required

Required fields

receipt_id, production_run_id, return_package_id, receipt_hash, receipt_signature

returns

Return fields

passport_id, passport_hash, verification_id, rail_key, return_package_id, receipt_id, callback_hash, transcript_hash, payment_authority_type, issued_at

Example

Start with the public API.

GET /api/receipt-passport 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/receipt-passport

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