Start with the core idea — every action is a verifiable receipt — then wire up generate and verify.
An agent action produces an R+2 receipt: signed (ed25519), hash-chained, independently verifiable. You don't trust DCS — you check the math.
curl -X POST https://dcs-receipts-production.up.railway.app/receipts/generate \
-H "content-type: application/json" \
-d '{"action":{"kind":"build","target":"acme.com","summary":"deploy"}}'
curl -X POST https://dcs-receipts-production.up.railway.app/receipts/verify \
-H "content-type: application/json" \
-d '{"receipt": <paste the receipt JSON> }'
→ { "valid": true }
Or look up by id: GET https://dcs-receipts-production.up.railway.app/verify/:id. Try it in the browser on the verify tool.
Live network metrics: GET https://dcs-agentic-gateway-production.up.railway.app/analytics/receipts-issued (fields: total, by_status, cycles_total).