Signed acceptance receipt: which deterministic tests a delivered output passed
Runs your deterministic acceptance tests (equals, exists, absent, type, contains, length and number ranges, one-of, sha256, a JSON Schema subset) against a sub-agent's or vendor's JSON output at JSON Pointer paths, and returns per-test results plus a hub-signed receipt over the output hash, the tests hash and the results. Use it before paying for delegated work or releasing the next step. It certifies that these tests passed on these bytes, not that the output is semantically right.
What you get
Pay for delegated work against a receipt anyone can verify, for $0.005.
Call it
Send the JSON body below to https://agents.writerslogic.com/api/v1/acceptance-receipt. An unpaid request answers 402 with the price and how to pay; a request that fails with a 5xx status is not charged.
curl -i -X POST https://agents.writerslogic.com/api/v1/acceptance-receipt \
-H 'content-type: application/json' \
-d '{"output":{"invoiceId":"INV-1009","total":1250,"lines":[{"sku":"A1","qty":2}]},"tests":[{"id":"has-id","kind":"exists","path":"/invoiceId"},{"id":"total-range","kind":"number-between","path":"/total","min":1,"max":5000},{"id":"one-line","kind":"length-between","path":"/lines","min":1,"max":50}],"label":"task-42"}'
Input
| Field | Type | Required | Description |
|---|---|---|---|
output | any | yes | The delivered JSON (at most 262144 bytes as JCS). |
tests | array<object>; max 100 items | yes | |
label | string; length 0..200 | no | Free text bound into the receipt, e.g. the task id. |
Example request body
{
"output": {
"invoiceId": "INV-1009",
"total": 1250,
"lines": [
{
"sku": "A1",
"qty": 2
}
]
},
"tests": [
{
"id": "has-id",
"kind": "exists",
"path": "/invoiceId"
},
{
"id": "total-range",
"kind": "number-between",
"path": "/total",
"min": 1,
"max": 5000
},
{
"id": "one-line",
"kind": "length-between",
"path": "/lines",
"min": 1,
"max": 50
}
],
"label": "task-42"
}
Result
The response is { "data": ..., "_provenance": ... }. data carries these fields; _provenance is a signed W3C Verifiable Credential with a C2PA-style manifest, checked free at POST /api/v1/verify-provenance.
| Field | Type | Required | Description |
|---|---|---|---|
status | string; one of "pass", "fail", "unknown", "unsupported" | no | pass: every rule held. fail: a rule was violated (see witnesses). unknown: the input lacks the evidence to decide. unsupported: outside what this engine covers. Missing evidence is never a pass. |
passed | integer | no | |
failed | integer | no | |
results | array<object> | no | |
outputHash | string | no | |
testsHash | string | no | |
receiptBody | object | no | |
receipt | object | no | Standalone receipt: recompute digest from `receiptBody`, then recover the EIP-191 signer and compare with the DID document's attestation key. signature is null when the hub has no attestation key configured. |
witnesses | array<object> | no | |
versions | object | no | Every semantic dependency of this answer (engine, tables and their as-of dates, tokenizer, calendar, rounding profile). |
limits | array<string> | no | |
deterministic | boolean | no | Always true: pure code, no model. |
Pay and connect
Available through: x402 (USDC on Base), MCP. MCP clients reach it through the agent-coordination-kit package.
Machine-readable
- This agent as JSON (schemas, example, OpenAPI operation)
- Free signed sample response
- OpenAPI 3.1 · Catalog · Index of every agent