ao-notary-bridge
Registry code: dd5aa0711e391ead
Cryptographic proof-of-existence notarization for AI agents. Free tier + paid $0.01 USDC via x402.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.aotrust.link/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is ao-notary-bridge live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is ao-notary-bridge free to use?
- Not measured yet.
- What tools does ao-notary-bridge have?
- 5 tools: notary_quote, notary_free, notary_notarize, notary_verify, notary_notarize_paid.
- Is ao-notary-bridge safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- degraded → live
- topic
- crypto & onchain
- used for
- create cryptographic proof of existence
- notarize work artifact on-chain
- get notarization quote
- verify notarization
- takes → gives
- text, data, payments → data
- tools
- 2 reads3 changes data
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-09
concentrated, shared-payto
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
notary_quote reads unknown never probed
Request a notarisation quote for a work artifact. Returns the cost ($0.01 USDC or NEAR equivalent), a quote_id valid for 600 seconds, the sink account to send payment to, and the PDR schema version. Step 1 of the notarisation flow: quote -> pay -> notarize -> verify.
{ "type": "object", "properties": { "work_hash": { "type": "string", "default": "" }, "pdr_version": { "type": "string", "default": "2.3" } }, "additionalProperties": false }arguments 14 linesnotary_free changes data unknown never probed
Create a free cryptographic proof of existence (PDR) for a digital artifact without payment. Dual mode: pass work_hash (Mode A, client-computed SHA-256 hex) OR content (Mode B, raw text/code ≤60KB — server hashes it, zero retention). Subject to rate limits (5/IP/day, 1000/day global). Returns shield_id, pdr_b64, and verify_url. For on-chain settlement proof, use notary_notarize_paid ($0.01 USDC on Base).
{ "type": "object", "properties": { "content": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null }, "metadata": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null }, "work_hash": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null }, "prev_work_hash": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null } }, "additionalProperties": false }arguments 50 linesnotary_notarize changes data unknown never probed
Submit a work artifact for on-chain notarisation (NEAR_DIRECT payment path). PREREQUISITE: Send the NEAR amount from notary_quote to the sink account, then provide the resulting tx_hash here. The server verifies the on-chain payment and submits the notarisation. Payment binding: pass payer_account (the NEAR account that paid) and bind_sig — a base64 Ed25519 NEP-413 signature over 'AOTrust AITP-BIND v1 work_hash:<64hex> tx_hash:<tx_hash>'. Returns job_id — use notary_verify to poll for the signed PDR. Step 3 of the notarisation flow: quote -> pay -> notarize -> verify.
{ "type": "object", "required": [ "work_hash", "tx_hash" ], "properties": { "tx_hash": { "type": "string" }, "bind_sig": { "type": "string", "default": "" }, "metadata": { "type": "string", "default": "{}" }, "agent_sig": { "type": "string", "default": "" }, "work_hash": { "type": "string" }, "agent_pubkey": { "type": "string", "default": "" }, "artifact_uri": { "type": "string", "default": "" }, "payer_account": { "type": "string", "default": "" } }, "additionalProperties": false }arguments 40 linesnotary_verify reads unknown never probed
Verify a notarisation by job_id. Returns status (pending/anchored/error). If anchored, returns the full PDR record (base64, 239 bytes) with Ed25519 signature verification. Step 4 of the notarisation flow: quote -> pay -> notarize -> verify. Can be polled repeatedly until status changes from 'pending' to 'anchored'.
{ "type": "object", "required": [ "job_id" ], "properties": { "job_id": { "type": "string" } }, "additionalProperties": false }arguments 12 linesnotary_notarize_paid changes data unknown never probed
Notarize a work hash on AOTrust (mainnet NEAR + Base USDC receipt). $0.01 USDC via x402-over-MCP: call without payment to receive PaymentRequired; retry with params._meta['x402/payment'] = signed PaymentPayload (EIP-3009, scheme exact, eip155:8453). HTTP clients: POST /notarize with x-payment header.
{ "type": "object", "required": [ "work_hash" ], "properties": { "agent_sig": { "type": "string", "default": "" }, "work_hash": { "type": "string" }, "agent_pubkey": { "type": "string", "default": "" }, "prev_work_hash": { "type": "string", "default": "" } }, "additionalProperties": false }arguments 24 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddd5aa0711e391ead.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dd5aa0711e391ead/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dd5aa0711e391ead?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.