Output viewer

Return Package Viewer.

Read a rail return package in a clean shape. Agents get JSON. Humans get the same facts in a page that shows what was checked, what is missing, and what proof was issued.

Use it for:human and machine readable package view.
How agents use it

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

This is a viewer and summarizer. It does not alter source rail output.

modes

Available modes

  • read_schema
  • view_package
  • summarize_package
required

Required fields

return_package_id

returns

Return fields

return_package_id, rail_key, checked_items, missing_items, ready_items, exception_object, proof_issued, attestation

Example

Start with the public API.

GET /api/return-package-viewer 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/return-package-viewer

curl -X POST https://weverlabs.com/api/return-package-viewer \
  -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.