For agents.

Mandate

• Your model reasons. Artifice supplies research, tools, risk, memory, and execution.
• Bring any model. Access is open. No token gating.
• Non-custodial where possible. Agents do not hold funds. The operator sets risk policy.
• Destructive actions require confirmation. Prefer propose-then-confirm before live size.

Origins

Human docs on this host. Live API on https://app.jester.trade. Do not send keys or payments to artifice.systems.

Discover

Fetch these in order. The live manifest and OpenAPI are the contract. This page is orientation.

Auth

• x-api-key or PAYMENT-SIGNATURE on the API origin. Never on artifice.systems.
• Payment and keys cannot mint or revoke keys, delete the account, or change the password. Those stay session-only.
• Inspect remaining quota with GET /api/delegated/usage (or jester_usage). That GET does not consume the daily POST cap.

MCP

Stdio bridge jester-mcp-bridge (npm). Your host starts it. It authenticates with your key and talks to the API origin over HTTPS.

1. Get a key from Console Keys or app.jester.trade/ai. Store it privately.
2. Node.js 18+ on the machine that runs the host.
3. Add the stdio server. The host runs npx -y jester-mcp-bridge. You do not clone a repo.
4. Restart the host. Ask it to list tools. You should see jester_* names.
5. Verify read-only first: portfolio, positions, strategy discovery. Do not place trades.

{
  "mcpServers": {
    "jester": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "jester-mcp-bridge"],
      "env": {
        "JESTER_API_KEY": "<your-key>",
        "JESTER_BASE_URL": "https://app.jester.trade"
      }
    }
  }
}

{
  "mcpServers": {
    "jester": {
      "command": "npx",
      "args": ["-y", "jester-mcp-bridge"],
      "env": {
        "JESTER_API_KEY": "<your-key>",
        "JESTER_BASE_URL": "https://app.jester.trade"
      }
    }
  }
}

{
  "mcpServers": {
    "jester": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "jester-mcp-bridge"],
      "env": {
        "JESTER_API_KEY": "${JESTER_API_KEY}",
        "JESTER_BASE_URL": "https://app.jester.trade"
      }
    }
  }
}

claude mcp add jester -s project \
  --env JESTER_API_KEY=<your-key> \
  --env JESTER_BASE_URL=https://app.jester.trade \
  -- npx -y jester-mcp-bridge

{
  "servers": {
    "jester": {
      "command": "npx -y jester-mcp-bridge",
      "env": {
        "JESTER_API_KEY": "<your-key>",
        "JESTER_BASE_URL": "https://app.jester.trade"
      }
    }
  }
}

grok mcp add jester \
  --command "npx -y jester-mcp-bridge" \
  --env JESTER_API_KEY=<your-key> \
  --env JESTER_BASE_URL=https://app.jester.trade

Verify with:

Use Jester tools to show my portfolio summary and open positions. Do not place trades.

x402

Pay, then continue. x402 is usage billing over HTTP. Agents discover an endpoint, receive its price, pay, and retry. No seats. No checkout. Keys remain optional.

1. Call the API origin (app.jester.trade). Do not call artifice.systems for trades.
2. If the response is 402, read the payment requirements in the body.
3. Pay from any wallet. Retry the same request with PAYMENT-SIGNATURE.
4. A verified settlement is identity. An account is created if the wallet is new.
5. Or send x-api-key instead, and skip payment when the key is already authorized.
6. Check remaining quota with GET /api/delegated/usage before heavy POST workloads.

Live payment requirements come from the 402 response and OpenAPI. Console chat uses settlement: "x402" on the signed-in session. Fees and on-chain settle follow the live manifest — fetch it, do not assume a price from this page.

HTTP

Same identity as MCP: x-api-key or PAYMENT-SIGNATURE on https://app.jester.trade.

mcp:mutate keys must propose then confirm. Immediate execute exists for platform:trade / webhook keys — prefer propose-then-confirm unless the operator has explicitly chosen otherwise. Full catalog: onboarding JSON and OpenAPI on the API origin.

Surfaces

Safety

• Use a dedicated key per agent. Store it privately. Rotate on suspected exposure. Revoke unused keys.
• Start read-only. Then a small test. Then live size.
• Review pair, side, size, stop, target, and risk before confirming.
• Backtests and optimizer ranks are research, not guarantees.
• Pause or revoke if proposals look wrong, risk settings look wrong, or a key may have leaked.
• You remain responsible for reviewing risk and permissions.

Do not

• Do not use this marketing site as the trading API host.
• Do not sniff /api/miniapp/* without a Telegram WebApp or terminal session.
• Do not use payment or an API key to mint keys, delete the account, or change the password.
• Do not share keys in chat, logs, or screenshots.
• Do not skip confirmation on mutate tools unless the operator has chosen an immediate-execute key.
• Do not scrape product UIs for trade or automation actions.

Human docs