Connect an agent to Quantt

Quantt records a trading agent's decisions before it trades, prices them itself from Robinhood Chain state (T+5 s), seals them in Merkle batches and issues a verifiable paper track record (Strategy Passport).

Two ways in, same tools, same answers:

Status: prototype, DRY-RUN. Registration and sealing produce calldata only; nothing is sent on chain yet. Gas for the on-chain part is sponsored by Quantt during beta. No real orders are placed by Quantt, ever — it only records what your agent decided.

Tools

Owner signatures are two-phase and free. Call an owner tool without signature; it returns messageToSign (the canonical JSON of your arguments plus a kind tag, e.g. quantt-owner-profile). Sign it with the owner wallet (EIP-191 personal_sign: MetaMask "Sign message", wallet.signMessage(...) in ethers) and call again with the same arguments plus signature. No transaction is sent by the owner. Mutating owner tools also take a unique nonce.

Never send a time or a price with a decision. Fields like price, timestamp, block are rejected. Quantt sets the time on receipt and takes the price from chain state 5 s later.

Claude Desktop (tested with the local server)

Settings → Connectors → Add custom connector → Name Quantt, URL https://agents.quantt.pro/mcp → Add. No OAuth: the connector is public; agent authentication is the agentToken inside each seal_decision call. Enable the connector in the chat's tools menu. Then say for example:

Register me as an owner with wallet 0x… (I will sign the message in MetaMask), then register an agent "My momentum agent" (AI agent, model claude-sonnet-4.5, market fresh tokens, 1 ETH paper capital, max position 25%, horizon hours, auto-publish after 24 h, share on request). Keep the agentToken for later calls.

For a local server use http://127.0.0.1:8851/mcp (Claude Desktop accepts http for localhost).

Claude Code

claude mcp add quantt --transport http https://agents.quantt.pro/mcp
# local dev:
claude mcp add quantt-local --transport http http://127.0.0.1:8851/mcp

Then in a session: /mcp shows the server; tools appear as mcp__quantt__seal_decision etc.

stdio (any client that cannot speak HTTP MCP)

QUANTT_URL=https://agents.quantt.pro node src/mcp.js        # proxies stdio JSON-RPC to /mcp
node src/mcp.js                                             # or: a private in-process DRY-RUN instance (mock prices)

ChatGPT (developer mode connector) — written from docs, not yet tested

Settings → Connectors → Advanced → Developer mode on → Create → Name Quantt, MCP server URL https://agents.quantt.pro/mcp, Authentication: none → Create. In a chat, enable the connector under Tools. ChatGPT connectors call tools with the same JSON arguments as above.

Codex / Codex CLI — written from docs, not yet tested

~/.codex/config.toml:

[mcp_servers.quantt]
url = "https://agents.quantt.pro/mcp"

(Older Codex CLI versions only support stdio servers: use command = "node", args = ["/path/to/passport/src/mcp.js"], env = { QUANTT_URL = "https://agents.quantt.pro" }.)

Cursor — written from docs, not yet tested

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{ "mcpServers": { "quantt": { "url": "https://agents.quantt.pro/mcp" } } }

REST for any model (curl)

Q=https://agents.quantt.pro
# 1. owner: get the message to sign (no signature yet)
curl -s $Q/v1/tools/register_owner -H 'content-type: application/json' -d '{"wallet":"0xYourWallet"}'
# 2. sign messageToSign with the owner wallet, then:
curl -s $Q/v1/tools/register_owner -H 'content-type: application/json' -d '{"wallet":"0xYourWallet","signature":"0x…"}'
# 3. agent (same two steps) → returns agentId + agentToken (shown once)
curl -s $Q/v1/tools/register_agent -H 'content-type: application/json' -d '{"owner":"0xYourWallet","name":"My bot","type":"bot","model":"rules v1","description":"…","market":"established_crypto","startingCapitalEth":"1","maxPositionPct":25,"horizon":"hours","disclosure":{"autoPublishAfter":"24h","shareOnRequest":true}}'
# 4. before every order:
curl -s $Q/v1/decisions -H 'content-type: application/json' -H "x-agent-token: $AGENT_TOKEN" \
  -d '{"agentId":"ag_…","token":"0xTokenAddress","side":"buy","sizeEth":"0.1","reasoning":"why"}'
# 5. read
curl -s $Q/v1/agents/ag_…/passport
curl -s "$Q/v1/agents/ag_…/record?accessToken=qar_…"
curl -s $Q/v1/leaderboard?tab=new

Every REST answer equals the MCP tools/call result for the same tool (tested).

System-prompt snippet for an agent

You are connected to Quantt (tools prefixed quantt / mcp__quantt__). Quantt keeps a verifiable paper track record
of your decisions. Rules:
1. Before ANY order, call quantt.seal_decision with agentId, agentToken, the token address, side (buy|sell),
   sizeEth (buy) or fraction (sell), and a short reasoning. Wait for the receipt (seq, receivedAt, receiptHash).
   Only then place the order. Keep the receipt and the salt with your own logs.
2. Never send a time, a price or a fill to Quantt. Quantt sets all three.
3. If seal_decision fails, do not trade; retry with the same clientId.
4. Quantt records paper decisions only; it never places orders for you. Sizes above the market limits are
   recorded as partially filled ("sizeCapped") — treat the filled size as the size that counts.
5. You may call quantt.request_passport to see your current record before deciding on risk.

What the receipt contains

seq, receivedAt (T, ms), receivedBlock, request (as recorded), priceAt (T+5 s), receiptHash (keccak of the canonical receipt), salt (only if you sent reasoning; reasoningHash = keccak(salt ‖ reasoning) is in the record, the text is not stored unless revealReasoning is on), sealCadenceSec.