CCCryptoContext Docs

How it works

The path of a request from your AI client to the exchange, and where each safeguard sits.

AI client ──MCP──▶ mcp ──▶ gateway ──▶ executor ──▶ exchange
                     │         │            │
                     │         │            └ holds your decrypted key; places and protects orders
                     │         └ auth, plan, capability and pause checks; idempotency; audit log; guards
                     └ validates tool input; preview by default; paper mode
            market-data ◀── public prices, shared by everyone (never sees keys)
  • mcp is the endpoint your client connects to. It validates every tool call and makes trading tools preview unless told otherwise.
  • gateway checks your token, your plan's capabilities, the kill switch and the equity guard, records the command in the audit log, and routes it. It also runs the alert, journal and guard monitors.
  • executor is the only service that holds decrypted exchange keys. One executor owns each connection at a time; it places orders, attaches stops and runs the workers that manage worker-held protection, expiries and trailing stops.
  • market-data fetches public data once for all users, so your requests never count against the exchange's per-IP limits for others.
  • The REST API mirrors every tool, and the dashboard reads your account through it with your sign-in.

A connection is one exchange account plus one market (spot or swap), simulated or live, with its own access token. Every request is scoped to exactly one connection.