Overview FAQ Getting started Account model Co-signer Networks Fees & gas Payments Trading Earn AI agents Proposals Recovery Security Support

AI agents

Connecting an AI agent.

How an AI agent connects to a Summo account, what it can see and request, and how its requests are approved.

01What Agent Access is

Agent Access connects an AI agent the account holder already uses, such as Claude or ChatGPT, to their Summo account. The agent can read the account and file requests for actions such as a swap, a perpetual futures order or a payment. The account holder approves each request on their phone, or sets an agent’s requests to be approved there automatically.

The agentHolds no key and signs nothing.

The account holder’s phoneSigns every action the agent requests, approved by the account holder or, if they choose, automatically.

SummoHolds one of the account’s three keys and cannot move funds on its own.

Summo does not provide the agent, review what it asks for, or recommend any request. The account holder decides what to approve, and which agents, if any, are approved automatically.

02Connecting an agent

Claude, ChatGPT and Codex connect by signing in, in three steps. Other AI apps that support MCP sign-in connect the same way.

1On a computer, add Summo’s MCP server to the agent with the server address below. The steps for each app follow.
2The agent opens a Summo sign-in page that shows a short code and a QR code.
3In the Summo app, go to More, then Connected agents. Tap Scan code to scan the page’s QR code, or Enter sign-in code to type the code. Check which app is asking, then approve with Face ID.

A sign-in code works once and expires after 10 minutes. Never enter a code or open a sign-in page that someone else sent.

Summo shows Claude, ChatGPT and Codex by name. Any other app is shown by its web address, as “an app from example.com”, with a note that Summo has not checked it. Connect only apps you trust.

After the approval, go back to the agent. It finishes signing in and then appears in Connected agents. If it does not finish, Connected agents says so.

Server address

https://mcp.summo.cash

Claude apps

On claude.ai in a web browser, or in Claude Desktop, go to Customize, then Connectors, and add a custom connector with the server address. Under Authentication, choose Sign in now.

The connector then works in the Claude phone app too. Adding it from the phone may not finish.

Claude Code

Run:

claude mcp add --transport http summo https://mcp.summo.cash

Then run /mcp and choose Summo to sign in.

ChatGPT

On chatgpt.com, go to Plugins, select the plus button, then Add custom MCP server. Enter the server address as the server URL, choose OAuth, accept the warning and select Create as a plugin.

Then install the plugin before using it in a conversation.

Codex

Run:

codex mcp add summo --url https://mcp.summo.cash

codex mcp login summo

03Other agents

Agents that cannot sign in this way, such as OpenClaw or Hermes Agent, connect with an access code instead.

1In the Summo app, go to More, then Connected agents, tap Enter sign-in code, then No sign-in page? Get an access code. Name the agent and approve with Face ID.
2Add the code to the agent’s settings as shown below. The app shows the code only once.

Anyone with the code can act as that agent, so keep it private.

OpenClaw

Set SUMMO_ACCESS_CODE to the access code in the environment OpenClaw runs in, then run:

openclaw mcp set summo '{"url":"https://mcp.summo.cash","transport":"streamable-http","headers":{"Authorization":"Bearer ${SUMMO_ACCESS_CODE}"}}'

Hermes Agent

Add to ~/.hermes/config.yaml, with the access code in place of YOUR_ACCESS_CODE:

mcp_servers:
  summo:
    url: "https://mcp.summo.cash"
    headers:
      Authorization: "Bearer YOUR_ACCESS_CODE"

Then run /reload-mcp in Hermes.

Any other agent

Connect to the server address and send this header on every request:

Authorization: Bearer YOUR_ACCESS_CODE

Agents that call an HTTP API instead of MCP can use the same code. Instructions for agents are at summo.cash/agents/SKILL.md and the API description at summo.cash/agents/openapi.json.

04What an agent can see

A connected agent can read the account’s balances, its positions in perpetual futures (with their unrealized profit and loss), prediction markets and Earn, its recent activity, and its own addresses for receiving tokens, as the app’s Receive screen shows them. It can also look up the tokens, markets, prediction events and Earn vaults listed in Summo, the price history of perpetual futures markets, and an estimate for a swap.

An agent never sees the account holder’s name, email address or contacts.

05What an agent can request

A request names one action and its values. Requests can be filed for the following actions; further types are added over time.

SwapExchanges one token for another on one network, or between Ethereum-compatible networks.

Perpetual futures orderOpens a position, or closes an open one. A new position can include a stop-loss, approved with the order, which then closes the position if the price reaches it, with no further approval.

Perpetual futures depositAdds funds from the account to the perpetual futures balance.

Prediction market orderBuys one side of a prediction market, in the countries where prediction markets are available.

Earn depositDeposits into an Earn vault.

SendSends assets to an address or to a Summo username.

QR PayPays a Pix code, or a payment QR from another country QR Pay covers, such as M-Pesa in Kenya. Requires a verified account.

Swaps are limited to tokens verified by Summo. A send or a payment goes through the same checks as one the account holder starts, and the request shows who is paid.

An agent can tell Summo, in one sentence, about something it was asked for that Summo cannot do yet. Agents are instructed to leave personal details out of these reports, which Summo uses to learn what to add.

06Approving a request

Each agent’s requests are approved manually or automatically, as the account holder sets for that agent with Approve automatically in Connected agents. The setting is off when an agent connects.

Manual approvalEach request arrives in the app’s Approvals screen, with a notification, and opens on a screen of its own that shows what the agent asked for, with prices and fees quoted live. The account holder approves it there with Face ID, or declines it. An approved request is carried out on that screen.

Automatic approvalTurning it on for an agent requires Face ID. The account holder’s phone then approves and carries out each request from that agent within five minutes of filing, with no tap, and a notification follows each one. Automatic approval can be turned off for an agent at any time in its settings. A request not carried out within five minutes waits for manual approval, as does a swap between networks.

Both go through the same checks as an action the account holder starts in the app, including the account’s spending limits. Under automatic approval, a request over a limit is refused when the agent files it. Spending limits apply to sends, swaps and payments, not to perpetual futures or prediction market orders.

Automatic approval comes with an app update. Until the app on the phone has it, the setting does not appear and every request waits for manual approval.

A request waits up to 12 hours, or less when the agent sets a shorter time, from 5 minutes, as it files it. One that is not approved by then expires, and nothing is sent. The agent can follow the status of its requests, and can withdraw one until it is approved.

An agent can attach a one-line note to a request. The app shows the note labelled as the agent’s own, not checked by Summo, and never uses it in a notification or in the description of the request.

07Security

An agent holds no key and signs nothing. Every action it requests is signed on the account holder’s own phone, whether they approve it themselves or have set the agent’s requests to be approved automatically. Summo holds one of the account’s three keys and cannot move funds on its own. See the account model.

Guardians, recovery, spending limits and trusted addresses are outside Agent Access, even with approval. An agent cannot reach the recovery phrase or any key, change the profile or settings, connect the account to other apps, or buy with a card.

08Pausing and disconnecting

Connected agents lists every connected agent with when it was last used. An agent can be paused, resumed or disconnected at any time. Pausing or disconnecting an agent cancels its waiting requests, and a disconnected agent loses access immediately. Turning off Approve automatically takes effect at once, and the agent’s waiting requests then need manual approval. An agent whose requests are declined, refused or fail repeatedly is paused automatically. Up to five agents can be connected at once.