Twelve sample records — one per instrument class.
Every class in the suite has a sandbox record. Click one to load it into the console below. Each answers sandbox: true — demonstration fixtures, never the register.
Call the API. Live.
These run against production right now — keyless, because every endpoint below is public by design.
Drive the registry like an agent.
JSON-RPC 2.0 against /mcp — the same surface your AI connects to. The sandbox key rides along as the Bearer, so you can see exactly what a scoped agent key does.
The gates, demonstrated — not described.
An API that enforces property rights must be willing to say no, in the open. Fire each one and read the refusal.
A write, over MCP
Ask the read-only surface to endorse a note. It refuses at the HTTP layer — the refusal is the rule: an API key proves possession, never authority to bind an institution.
A key without the scope
Present a Bearer key that doesn't carry ai_read_only. Unknown or wrongly-scoped keys get nothing at all — a write-scoped credential can never normalise this surface.
An endorsement that cannot exist
Try to endorse an electronic air waybill. A carriage contract passes no title, so the register refuses — 403 instrument_not_negotiable, for any authenticated caller.
Three steps to a live integration.
Build against the sandbox
Keyless or with the sandbox key. Reads only — by design. Point an MCP client at /mcp and ask it to verify EPN-2026-SAMPLE-0001.
Become a verified counterparty
Issuance is by qualification, not open signup. Apply through KYI — Know Your Issuer, or write to the desk.
Get production keys
Scoped ai_read_only agent keys and session issuance for your institution. Request them via the registry desk — read the API documentation first.
sample records are fixtures and say so · nothing on this page can move an obligation · iset.finance