RCO Records - Record of Cleared Orders

io.github.allooloo/rco-records · v2.3.0 · ecommerce

RCO Records - Record of Cleared Orders is healthy: it completed an MCP handshake in 342 ms and exposes 5 tools.

The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.

Endpoint: https://mcp.rco-records.ai/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count5
Latency342 ms
Last checked (UTC)2026-10-30T07:05:24.035Z

Health history

Checked (UTC)StatusLatencyError
2026-10-30T07:05:24.035ZHealthy342

Tools (5)

write_receiptWrite one v1 receipt for a read a gate has cleared. Authenticated: Authorization: Bearer <writer token>. Idempotent on (writer, subject, subject_type, market, rule_version, cleared_at, answer_hash). Returns the receipt.
verify_receiptReturn one receipt by id (rco:… for v1, dec_… for v0) with the verification result (hash, id, signature) and the public key (JWK) that checks it. Public.
list_receiptsYour own receipts only — the rows whose caller is your customer key — by seq range (from_seq, to_seq, after_seq) or date range (from, to: YYYY-MM-DD, to inclusive), limit ≤ 500. Authorization: Bearer <customer key>. Refuses without a key.
get_statementA signed statement of your slice for a month (month: YYYY-MM) or a date range (from, to: YYYY-MM-DD, to exclusive): count, first and last seq, slice digest, the chain tip at issue, Ed25519 signature by Allooloo. Authorization: Bearer <customer key>.
issue_auditor_keyIssue a read-only sub-key on your own slice for your auditor (list_receipts and get_statement only). Authorization: Bearer <customer key>. The key value is returned once.