Connect an app or agent

Last updated 14 October 2026

You can let an AI assistant (Claude, ChatGPT and others that support MCP), a chat integration (Telegram or X, for example) or your own script use Edge for you. You approve it once, in your own wallet, on an Edge page; after that it calls Edge with a token and needs no private key and no signing code.

Edge offers the same operations through two doors: an MCP server at https://edge.polytrade.app/mcp for AI apps, and an HTTP API at https://edge.polytrade.app/api/v1 for scripts. The OpenAPI document is at https://edge.polytrade.app/api/v1/openapi.json.

In this release, connected apps can read your account and, if you allow creator actions below, act on all your baskets on their own, without asking you each time, and claim your earnings to your own wallet. They cannot start agents, exit agents or move money anywhere else.

Connect once

Claude and other MCP apps

Add https://edge.polytrade.app/mcp as a remote MCP server. The app opens Edge's consent page in your browser; you connect your wallet there, choose what the app may do, and sign. The app then holds the token, not you.

A script on a server, or a chat integration

Use device login, which needs no browser on the machine running the script:

1. Register a client once: POST https://edge.polytrade.app/oauth/register with a JSON body of client_name and "grant_types": ["urn:ietf:params:oauth:grant-type:device_code", "refresh_token"]. Keep the client_id it answers.
2. Start a login: POST https://edge.polytrade.app/oauth/device with client_id and scope=read creator. It answers a user_code and a link.
3. Approve it yourself: open https://edge.polytrade.app/link, enter the code, connect your wallet and sign.
4. Collect the tokens: poll POST https://edge.polytrade.app/oauth/token with grant_type=urn:ietf:params:oauth:grant-type:device_code, your client_id and the device_code, every 5 seconds, until it answers your tokens. Polling faster answers slow_down.

An access token lasts 15 minutes. Get a new one with grant_type=refresh_token on the same endpoint; keep the refresh token as you would a password.

What you approve

The consent page lists each permission in these words. You tick the ones the app may have:

• read: See your baskets, agents and balances.
• creator: Publish baskets, change and reshuffle all your baskets, and claim your earnings to your own wallet.

With the creator permission ticked, the page also says:

This app can change the tokens in all your baskets, publish new ones and claim your earnings to your own wallet. Anyone copying your baskets still gets 24 hours' notice before a change takes effect. Publishing, editing and reshuffling all count toward the daily limit below, and you can switch publishing off.

and you set two limits:

• Most changes a day, from 1 to 200 (default 20). Publishes, changes and reshuffles that succeed count toward it over the last 24 hours, counted by the hour; claims and pre-checks do not. A call over the limit answers 429 creator_daily_cap.
• May publish new baskets, on by default. When it is off, publishing answers 403 publish_not_allowed.

A permission lasts at most 30 days. You can see and revoke every connection on the Connected agents page; a revoked app is cut off within 30 seconds. A permission given before the creator tools existed cannot use them (they answer 403 grant_outdated): connect the app again.

Money only goes to you. No operation takes a recipient or an address. A claim always pays the wallet that signed the permission, whoever makes the call. While an agent wallet is funded, Edge holds its key, as it does for agents you start in the app.

Operations

This is the list this deployment serves right now. Each one is the same operation through either door: the HTTP path is /api/v1/ plus its name with dots as slashes, and the MCP tool is edge_ plus its name with dots as underscores. The OpenAPI document has every input and answer in full.

Calling the API

• Authorization. Send Authorization: Bearer <access token> on every call.
• Inputs. A GET takes its input as query parameters; a POST takes a JSON body.
• Retries are safe with a key. Every operation that changes something needs an Idempotency-Key header of 1 to 64 characters (letters, digits and _ . : -). A retry with the same key gets the first answer back instead of running twice. An answer marked retryable frees the key, so you can try again with it. Use a new key for a change you mean to make again.
• Over MCP, most apps cannot send a key. Without one, the same write with the same input within about 10 minutes is treated as one and the repeat gets the first answer. Changing a basket's tokens always runs, since running it again is safe: it answers unchanged or withdrawn. An app that can set _meta.idempotencyKey on the tool call gets the same rules as the header.
• Errors come back as { "error": { "code", "message", "retryable", "details"? } }. Over MCP an error is a result with isError: true, with the same body in structuredContent.error.
• Long operations may answer 202 with an operation id; poll it with the operation check above.

Example (Node, a connected script)

const EDGE = "https://edge.polytrade.app";
const token = process.env.EDGE_ACCESS_TOKEN; // from device login; refresh it with /oauth/token

export async function call(path, body) {
  const res = await fetch(`${EDGE}/api/v1/${path}`, {
    method: "POST",
    headers: {
      authorization: `Bearer ${token}`,
      "content-type": "application/json",
      "idempotency-key": `${path.replace(/\//g, "-")}-${Date.now()}`,
    },
    body: JSON.stringify(body),
  });
  return { status: res.status, body: await res.json() };
}

// Replace the tokens of one of your baskets:
// await call("baskets/update", { id: "my-basket", tokens: [...] });

Weights and cross-chain baskets

• A token's weight is a fraction of its basket, and the weights add up to 1: 0.25 is 25%. Weights that add up to about 100 are refused with a message saying so.
• A cross-chain basket splits the budget between chains in legs. A leg's weightPct is a whole percent from 1 to 99, and the legs add up to 100. Inside each leg, the token weights add up to 1 again.
• To publish one, send "tier": "cross" and two or more legs; you can leave tokens out. Legs without tier are refused rather than published as a single-chain basket.
• To change one, send legs and no tokens, with every chain the basket has and the tokens each will hold. The split between chains and the list of chains cannot change, because copiers are already funded on each; leave weightPct out or send it as it is. A single-chain basket is changed with tokens alone.
• Read, change, send back. What the basket read answers is in the same shape and units, so you can edit it and send it back.

Publishing a cross-chain basket (the body of the publish call):

{
  "name": "Two chain memes",
  "tier": "cross",
  "legs": [
    { "chain": "base", "weightPct": 60, "tokens": [
      { "addr": "0x…", "symbol": "AAA", "dec": 18, "weight": 0.5 },
      { "addr": "0x…", "symbol": "BBB", "dec": 18, "weight": 0.5 } ] },
    { "chain": "solana", "weightPct": 40, "tokens": [
      { "addr": "…pump", "symbol": "CCC", "dec": 6, "weight": 1 } ] }
  ]
}

Which tokens a basket can hold

Every publish, change and reshuffle checks each token on Edge's servers, the same way the app does. If any token fails, the call answers 400 rug_filtered, nothing is changed, and details.rejected lists each token that failed with the check, what Edge measured (got) and what it needs (need). Drop those tokens and try again. A token Edge could not check right now answers 503 vetting_unavailable; retry it later.

• quote_liquidity: at least $50,000 of liquidity on the USDC, ETH or SOL side of its pools. This is often about half of the total pool liquidity most sites show, so a token showing $75,000 in total can still fail.
• pool_age: its oldest market is at least 72 hours old.
• volume: at least $25,000 traded in the last 24 hours against USDC, ETH or SOL.
• buy_failed, sell_failed, unverifiable: a test buy and sell must go through.
• buy_tax, transfer_tax: the token itself may take at most 1% on a trade.
• sell_tax: a test round trip may lose at most 10%, pool fees included.
• freezable, seizable (Solana): the token's issuer must not be able to freeze holders or move their tokens.

The checks run in this order and only the first failure is reported for each token. Well known tokens Edge already lists, and the quote assets themselves, are not checked.

What does not change for people copying your baskets

A change made through an app is treated exactly like one made in the Edge app:

• 24 hours' notice. If anyone copies a basket, a change to its tokens waits 24 hours before it takes effect, so copiers can see it and exit. The answer gives effectiveAt.
• Screening. Every change goes through the same token screen and identity checks as a new basket.
• No turning a basket AI-managed. An update cannot add or change an AI prompt.
• Copiers' agents pace the rebalance. Each run moves only part of the basket.
• A copied basket stays up. You can withdraw a basket only while nobody copies it and nothing has been put into it; otherwise the withdraw answers 409 has_copiers and nothing changes.

Change a basket only when you have something to say: every change restarts the 24-hour notice your copiers see.

How copying, fees and risks work is on the main docs page. The Terms cover the apps you connect, and are drafts pending legal review.