Notary API — v1.0.0
Plain HTTP + JSON. No SDK, no account, no API key — attribution is a string you choose (agent), not a credential. For the payment mechanics themselves, see Protocol.
One real call, start to finish
Free-tier request — no payment header needed under the daily limit:
curl -X POST https://stillosdigitalholdings.com/notary/agent-clearance \
-H "Content-Type: application/json" \
-d '{"agent":"docs-example","counterparty_name":"Example Corp"}'Past the free tier, the same call returns 402 with exact payment terms:
HTTP/1.1 402 Payment Required
{
"accepts": [{
"scheme": "exact",
"network": "base",
"asset": "USDC",
"amount": "0.25",
"payTo": "0x…"
}]
}Retry the identical request with an X-PAYMENT header carrying proof of settlement to get the real, signed response:
curl -X POST https://stillosdigitalholdings.com/notary/agent-clearance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <base64 payment proof>" \
-d '{"agent":"docs-example","counterparty_name":"Example Corp"}'
HTTP/1.1 200 OK
{
"verdict": "CLEAR",
"receipt_hash": "…",
"signature": "…",
"signed_at": "2026-08-19T00:00:00.000Z"
}A working, live version of this exact flow — click a button, watch the real request and real response — is on the Agent Clearance page.
Error codes
| Code | Meaning |
|---|---|
| 200 | Success — payment verified (if required) and signed response returned. |
| 400 | Bad request — a required field is missing or malformed. The response names the field. |
| 402 | Payment required — free tier used up or the route has none. Response includes exact x402 terms. |
| 429 | Rate limit reached — a real anti-abuse limit, distinct from the 402 paywall. |
| 503 | The specific endpoint's module is temporarily unavailable. Retry later. |
Rate limits & SLA (representative)
Every route publishes its own free-tier limit, price, and p95 latency target. Representative examples:
| Route | Free tier | Rate limit | p95 latency |
|---|---|---|---|
| agent-clearance | 2/agent/day | 10/min | 2000ms |
| grade-strategy | 2/agent/day | 5/min | 500ms |
| screen-entity | 5/agent/day | 10/min | 2000ms |
| claim-verdict | 3/agent/day + rep. bonus | 10/min | 2000ms |
| dispute | none ($1/filing) | 6/min | — |
This table is a sample, not the full catalog — it can drift out of sync with reality if hand-maintained. The live, authoritative, machine-readable version of every route's limits and price is /notary/catalog and /.well-known/stillos.json.
Environment
One production environment — there is no separate sandbox/test API. Use a small free-tier call to test your integration before scaling volume; free-tier responses are real, signed data, not stubs.
Data retention
Covered in full in our Privacy Policy. In short: we retain what's needed to serve the request and settle payment, and the signed receipt itself (that's the product).
Uptime & incidents
Live, real status (not a hand-updated page) at /status.
Changelog
No separate changelog is published yet. The commit history on still-os-public-edge is the real record in the meantime.
Support
info@stillosdigitalholdings.com · +1 (307) 302-7392. Security-specific reports: see /security. Accountability model and dispute process: /governance.