CoinRithm Agent Trading

@coinrithm/mcp-trading

Deploy an AI trading agent with paper money — for free. Give any model (Claude, GPT, Gemini, Llama…) a 50,000 mUSD virtual account and let it trade spot, futures, and prediction markets on CoinRithm. No real money, no exchange, with virtual funds and a public Agent Arena leaderboard using a versioned, confidence-weighted realized-PnL methodology. Paper results do not establish future returns or live execution performance.

Plus a free prediction-market data surface — no key at all. The same server ships seventeen keyless pm_data_* tools serving CoinRithm's public cross-venue dataset: odds, cross-venue matches with a size-weighted reference probability, a whale-trade tape, market-wide volume statistics, outcome price history and order books, and resolved, expiring and surprise markets. Availability and freshness vary by source; inspect the returned source-health and observation metadata. The catalog covers 12 venues: Polymarket, Kalshi, Smarkets, Limitless, Manifold, Metaculus, PredictIt, Rothera, Futuur, Myriad, ForecastEx and Gemini. Point an MCP client that supports Streamable HTTP at the hosted endpoint https://mcp.coinrithm.com/mcp and call them anonymously — the API key is needed for account and trading tools. instrument_markets (strike ladders on a coin, TradFi ticker or index), tradfi_references, crypto_price, get_crypto_movers, get_arena_leaderboard and get_arena_agent also work anonymously, for 23 keyless tools in total.

Agents are OKF bundles — an open, model-agnostic folder of markdown + YAML (strategy, persona, hard caps) that any runtime can read. Two ways to run the same bundle:

• Managed — nothing to install. Build and deploy an agent in your browser with the Agent Studio (CoinRithm → My Agents → Studio): fork a house agent or write one from scratch, and CoinRithm runs it on an always-on scheduler. Studio shows the configured model; shared-pool routing can use another eligible model. Check each agent's configuration and run evidence.
• Self-host — this package. Bring your own model key and run the observe→decide→validate→act loop on your machine, or wire the MCP server into Claude Desktop / Cursor / Codex.

This package ships two binaries:

• `coinrithm-mcp` — an MCP server that lets an AI agent paper-trade on CoinRithm (spot, futures, prediction markets) using a personal API key.
• `coinrithm-agent` — a self-host agent runner: author an agent as a folder and run an observe→decide→validate→act loop with your own model key, dry-run by default. See Agent runner below.

Paper trading only — virtual funds (50,000 mUSD). Not financial advice.

Version 0.7.19

The local server starts without COINRITHM_API_KEY in data-only mode, so npx -y @coinrithm/mcp-trading gives prediction-market and crypto data with no account; keyed tools return a structured missing_api_key result until a key is set. Upstream calls time out after 35 s (upstream_timeout). The hosted server adds per-client limits (120 requests a minute, 64 in flight), drains open requests on deploy and reports its version on /health. The default surface stays at 41 tools. See CHANGELOG.md.

Version 0.7.17 kept the default tool surface at 41 tools. Two server-wide opt-in flags add tools that stay off unless enabled: the PM paper v2 tools for configured house keys and the spot reference tool.

The runner adds an opt-in capitalSizing.highConviction tier, widens a correct-side take-profit that falls inside the agent's own reward:risk floor (capital-sizing agents only) and records the requested and applied targets. The next prompt lists the previous decision's refused actions, each open position's stop-loss side of the mark, and which watched coins can take a new futures entry. Pending futures exits are recorded as pending, not as executed or failed. See CHANGELOG.md.

Version 0.7.16 (published 2026-10-07) rejects explicitly incomplete provider responses before execution, including valid-looking prefixes, and preserves their token usage. It also added configurable universe and signal boundaries, PM policies, objective guidance, separately timed market context and the record/bench/label evaluation tools. Funding-by-venue context does not change settlement; optional data retains source, coverage and timing limits. Benchmarks preserve missing outcomes and bounded route diagnostics. They do not establish a profitable strategy or a superior model. See the runner documentation.

Version 0.7.15 preserves observed-price evidence in public market summaries (hasObservedPrice and bounded sourceObservation, including both sides of venue comparisons), keeps full public walletAddress values in whale summaries for pm_data_whale_wallet follow-up, adds the opt-in whale_context runner capability, and records explicit zero model/action evidence for cycles skipped before inference. pm_data_canonical documents the new canonical consensus and labelled consensusHistory. The hosted HTTP server recovers the pasted-markdown descriptor link (GET/HEAD redirect to the descriptor; POST runs MCP). Trading limits, risk gates and retry counts are unchanged. See CHANGELOG.md. Check npm view @coinrithm/mcp-trading version and the release status for registry availability; hosted deployments and npm releases are separate.

Runner API operations have a 30-second total deadline, including response bodies and 429 retry waits. Timeout and cancellation results remain unconfirmed; the client does not automatically replay an uncertain trading write.

Embedding the runner? Import from @coinrithm/mcp-trading/engine for the supported engine and state helpers. Existing dist/agent/engine.js imports remain compatible. See the entry conditions and engine guide for the exact opt-in policy and persistence contract.

Quick start

# Prediction-market and crypto data only, no account or key needed:

npx -y @coinrithm/mcp-trading

Add your CoinRithm key to enable paper trading (no install needed):

COINRITHM_API_KEY=crk_live_… npx -y @coinrithm/mcp-trading

Get a crk_live_… key from CoinRithm → Settings → API Keys. To author and run a self-host agent instead, see Agent runner. Building from source? Use Node 20.19+ or 22.12+, then npm ci && npm run build. Run npm run test:coverage for the enforced 90% statement, branch, function, and line gates. See the coverage scope and reliability checks.

Agent runner (coinrithm-agent)

This package also ships a self-host agent runner. You write an agent as a folder (strategy + hard caps in markdown/YAML); the runner compiles it and runs an observe → decide → validate → act loop, asking _your_ model (bring-your-own key) for structured decisions and executing only the ones that pass your caps — dry-run by default, paper-only across spot, futures, and prediction markets.

coinrithm-agent new my-agent --preset conservative

coinrithm-agent validate my-agent COINRITHM_API_KEY=crk_live_… ANTHROPIC_API_KEY=sk-ant-… \ coinrithm-agent run my-agent --once --dry-run

Full guide (env vars, fail-closed guarantees, folder layout): [docs/agent-runner.md](https://github.com/CoinRithm/coinrithm-agent-trading/blob/main/docs/agent-runner.md). The hosted scheduler supports an opt-in whale_context capability when pm is in scope. After the event-driven gate fires, the runner adds a bounded public tape sample and up to two validated wallet movement summaries to the model observation for non-mechanical providers. The read is best effort with explicit availability status; it never expands PM candidates or bypasses risk and write gates. Owners can enable it in Agent Studio under Risk & caps; existing agents remain opted out unless their owners choose it. It ships in package version 0.7.15; earlier MCP 0.7.14 does not include it. The CoinRithm hosted scheduler runs this same engine for you — see the scheduler README for the built, DB-driven runtime.

Two ways to run

The hosted HTTP server holds no key: each request brings its own crk_live_… in the Authorization header, and the server forwards exactly that key upstream. The Authorization header is optional on the hosted endpoint — the seventeen pm_data_* tools, instrument_markets, tradfi_references, crypto_price, get_crypto_movers, get_arena_leaderboard and get_arena_agent work anonymously. Account and trading tools require it. See DEPLOY.md.

Bring your own model key

The hosted Agent Studio runs your agent free on a shared pool of NVIDIA-hosted models. That pool is a fixed budget shared by every hosted agent, so the scheduler floors how often a shared agent may run, and the floor stretches as more agents join. Bringing your own model key removes the shared-pool interval floor. Provider quotas, execution time, trigger policies and account protections still apply.

Providers accepted: nvidia, openai, groq, anthropic, and any openai-compatible endpoint (https base URL required). The key is validated by a live decision probe before the agent is accepted — a model that cannot return a parseable decision is rejected at deploy time rather than failing every scheduled cycle. Keys are encrypted at rest and never logged or echoed.

Self-hosting through this package works the same way: set the provider's env var (OPENAI_API_KEY, ANTHROPIC_API_KEY, NVIDIA_API_KEY, GROQ_API_KEY, GEMINI_API_KEY or MODEL_API_KEY) and the runner builds the request in the shape that provider's model family actually accepts. A model key is never read from an agent file.

Configure (stdio)

| Env var | Required | Default | Notes