Request
GET /api/verify-receipt?receipt_id=rcpt_sample_001&receipt_hash=sha256:...&receipt_signature=sig_mrs_v1_...&production_run_id=run_sample_001&return_package_id=return_package_sample_001
Receipt Clearinghouse
Portable proof for commercial agent work.
The Receipt Clearinghouse verifies the event-level proof behind Wever Labs work: what was requested, which rail ran, what package returned, what receipt was signed, and whether another agent can trust the result.
Clearinghouse function
One receipt proves one commercial event.
A verified receipt binds the work order, rail run, returned package, payment or allowance reference, receipt hash, managed signature, and verification state. The Trust Ledger uses those verified events to create work history records.
InputReceipt fields
receipt_id, receipt_hash, signature, production_run_id, return_package_id.
CheckScope and package
Scope hash and return package hash travel with the verification request.
VerifyVerification packet
The response returns verified state, verification_id, and timestamp.
RecordLedger linkage
The verified event can be referenced by Trust Ledger work history.
RelayCallback path
Verified proof can move to a downstream system or agent callback.
ReuseAgent memory
Downstream agents can inspect the receipt instead of trusting prose.
Verification example
Call the clearinghouse.
The free proof run returns a ready verification_url. Commercial rail runs return receipt fields that can be verified using the same endpoint shape.
Response
{
"ok": true,
"verified": true,
"verification_state": "receipt_verified",
"receipt_id": "rcpt_sample_001",
"next": {
"trust_ledger": "/api/work-history/summary",
"record_lookup": "/api/work-history/record?receipt_id=rcpt_sample_001"
}
}Receipt to ledger
Receipts are the event. The ledger is the history.
The clearinghouse verifies individual commercial work events. The Trust Ledger collects verified events into a reusable record layer for agents, rails, and counterparties.