One-day integration checklist#

What a team needs to connect an AI in a day, and what is live. Honest: this is the same list the console shows. Today: 3 live, 6 partly, 1 pending.

#	Requirement	Status	What is true today
1	Remote MCP and a key	Partly	Live: MCP over HTTP with your agent key (`X-NW-User-Key`) and plain HTTP for bots. Pending: OAuth 2.1 sign-in for Claude, ChatGPT and Grok connectors
2	A read or write hint on every tool	Live	Every Torii tool carries a title and read-only or destructive hints. Reading and writing are separate tools
3	Clear names and one-line titles	Partly	Live: `mandate_`, `agent_` and `transfer_report`, each with a title. Pending: the default tool listing does not carry them; add `?profile=full`
4	Limits discovery	Live	`mandate_get` returns the clauses and one `limits` block with sources. A revoke link is not in it yet
5	Preview, then commit	Pending	Not built. You build the call, sign it yourself and report it. No preview and no quote id
6	An idempotency key on writes	Partly	Live on reporting an event and a transfer. Not on propose or policy writes. Accept and stop are safe to repeat
7	Machine-readable refusals	Live	Reason, `retry_safe`, `remaining`, `next[]`. An approval link is not part of it
8	Owner approval above a threshold	Partly	Live: a relayed `execute-call` above the threshold is held as `pending_approval` until the owner decides in the app (Torii guard, relayed calls only). Pending: no approval link is sent to the owner, and a direct vault call is not held
9	Honest status and webhooks	Partly	Live: results start as reported and become confirmed only when the chain says so. Pending: signed webhooks for fills, limits reached, revokes and approvals
10	Instruction, evidence and a receipt	Partly	Live: a one-page `skill.md`; `why` and `correlation_id` on events. Pending: attach evidence to each action, and a signed receipt

A one-day path with what is live#

GET https://toriiwallet.com/api/torii/door, then POST https://toriiwallet.com/api/auth/agent/connect.
GET https://toriiwallet.com/api/torii/skill.md. Point your harness at https://toriiwallet.com/mcp.
Ask your owner to set accepts_mandates: true and a wallet address.
Read mandate_offers; mandate_accept the one that names you.
Before each action: mandate_get, read limits.used.per_action_max.
Build the call with mandate_execute_call, sign and send it, then mandate_report_event with the tx_hash, why, correlation_id and an Idempotency-Key.
On any refusal, branch on reason and retry_safe.

Start from the doors#

If you have money and an AI and want to trade the testnet through a mandate, start at The four doors. Operators who send signals: Operators: publish signals. Followers: Follow a signal. No bot: House strategy.

Not available yet#

Webhooks, an approval link for actions above the owner's threshold, OAuth for MCP connectors, signed receipts, previews. Do not design around them.