Agent setup

Use Quotient from your terminal or inside your agent.

Start with the Quotient CLI and skill. Add MCP only if you want your agent to load Quotient's live tool catalog and resources as native tools.

Quickstart

npm install --global quotient-forecasting
quotient setup

Setup authenticates access, installs the skill for selected clients, verifies CLI/account access, and then offers MCP as a separate final choice. The MCP choice defaults to No. A completed setup does not require MCP.

After installing a newer CLI release, run quotient setup again. It keeps saved access, optional context, and any existing MCP entry by default. Restart an open agent only when its skill or MCP configuration changed.

Choose how your agent uses Quotient

CLI + skill — Recommended

The skill teaches your agent the Quotient workflow. The CLI runs explicit, auditable commands for forecasts, signals, market search, mispricing, and reports. This keeps the agent's tool context smaller and makes each data call easy to inspect.

MCP — Optional

MCP exposes Quotient's live tools and resources directly inside supported agents. It is useful for native tool calling, schema discovery, and clients without terminal access. Loading more tools can add startup and reasoning overhead, especially for simple questions. MCP uses the same data, account, and prices as the CLI.

What setup configures

Access

Setup opens with one picker: create a free API key, paste a key you already have, or pay per call with x402.

Creating a key is the default. Press Enter to open your browser, sign in with Privy when needed, and confirm the code shown in your terminal. Setup then receives the account's existing API key automatically; if the account has no key, Quotient creates one. In this browser flow, the key is never placed in the browser URL or copied through the terminal. Browser approvals expire after ten minutes and are bound to the setup process that initiated them.

Pasting a key masks it as you type, showing only its final four characters, and setup verifies the key against your account before saving it. Choosing x402 skips the key entirely and uses Bankr to pay per call.

Later output identifies the saved key as **** plus its final four characters, never in full.

Agent skill

Once access is configured, setup offers Quick start or Customize. Quick start installs the skill for every client it detects and finishes.

Customize lists only the clients it actually detected among Claude Code, Codex, Hermes Agent, and OpenClaw, pre-checked, plus one "Other client" row that installs the portable skill under ~/.agents/skills. If nothing is detected, setup offers the portable skill directly. Pass --client all to write the skill for every supported client regardless of detection.

Installing replaces any previous copy of the skill. Use quotient skill update to refresh it after upgrading the CLI, and quotient skill uninstall to remove it; neither touches your access or MCP entries. The skill teaches the agent how to route common intents to explicit CLI commands and how to distinguish forecasts, market prices, published signals, and the daily WTI oil signal. A shell-capable agent can use Quotient without loading an MCP tool catalog.

The web playground calls the REST API directly and does not require an MCP connection.

Local context

One optional-context prompt keeps the default path short. If selected, setup can store an X profile and these public portfolio identifiers:

Polymarket proxy wallet;
Hyperliquid master or subaccount wallet;
Solana wallet.

They are written to the local Quotient config. The same values can be set in the console under Agent settings and pulled down with quotient sync; that sync is one-way, and a value saved on the account never clears one you set locally. Saving an address does not connect a wallet, start portfolio tracking, authorize a venue, or grant trading permission. Never enter a private key or seed phrase, in the terminal or the console.

The current Quotient portfolio endpoint performs a Polymarket-wallet join. Hyperliquid and Solana addresses are retained as local context for compatible portfolio workflows. Kalshi positions require authenticated account access rather than a public wallet lookup, so guided setup does not request Kalshi API credentials or a signing key.

Payments and execution

Bankr is optional. Setup can detect or install its CLI and save it as the preferred x402 payer and execution provider. This does not log into Bankr, approve a payment, or authorize a trade. Run bankr login separately and confirm each payment or order when requested.

Verification

Setup uses the fast everyday status check. It does not run the MCP doctor automatically:

quotient status

Use quotient doctor only for deeper diagnostics.

Optional: native MCP tools

MCP lets your agent discover and call Quotient tools directly. It is useful for native tool calling, schema discovery, and clients that cannot run terminal commands.

MCP can add tool-loading and context overhead, so simple questions may take longer. It uses the same Quotient data, account, and prices as the CLI. You can install it later.

Add native MCP tools? (optional)

MCP is one optional question, and only on the Customize path. It defaults to No. A client that already has a Quotient MCP entry is left alone. If MCP is installed, restart an agent session that was already open.

Ready

Without MCP, setup ends with a summary like this:

Ready
  Access · connected · 500 credits
  Skill · Codex
  MCP · not installed · optional

Try these in your agent:
  "What data does Quotient have available?"
  "How do I schedule daily buys for Quotient signals?"
  "Give me a digest of what's going on with my portfolio."

Add native tools later:
  quotient mcp install codex

Local files

Configuration is stored at:

~/.config/quotient/config.json

If XDG_CONFIG_HOME is set, Quotient uses that directory instead. The config file is written with user-only permissions. Optional native MCP entries call the local stdio bridge, so the API key is not copied into every client configuration. Friendly CLI commands call the canonical gateway routes directly; the stdio bridge is used only by optional MCP clients.

Manual client setup

Use a targeted command only when guided setup did not configure that client:

quotient skill install claude
quotient skill install codex
quotient skill install hermes
quotient skill install openclaw

These commands install only the skill. Install native MCP tools separately when wanted:

quotient mcp install auto
quotient mcp status
quotient mcp uninstall auto
quotient mcp uninstall codex

For another Agent Skills client:

quotient skill install generic

Live commands require shell access. If the client cannot run terminal commands, add an stdio MCP configuration with command quotient and arguments mcp and serve.

quotient agent install auto remains a deprecated compatibility alias for one release. It prints migration guidance and installs only the skill unless --with-mcp is explicit.

Verification and repair

quotient status
quotient agents detect
quotient skill update auto
quotient mcp status
quotient mcp install auto
quotient mcp uninstall auto
quotient doctor

status is the fast access, configuration, and account check; it does not require MCP.
skill update refreshes skill files without changing MCP.
mcp status, mcp install, and mcp uninstall affect only native MCP configuration.
doctor is the deep diagnostic path. It shows only a masked API key.

Agent resources

Agents with optional MCP installed can read:

quotient://skill
quotient://data-coverage
quotient://integrations
quotient://performance
quotient://openapi

Use get_account_status for a free balance and auto-refill check.

Deployment

The browser authorization facade requires THESIS_CLI_AUTH_SERVICE_SECRET; set the identical random value of at least 32 characters as QUOTIENT_CLI_AUTH_SERVICE_SECRET on the canonical API. The API rejects direct CLI-authorization requests without that service credential.

Before publishing a browser-auth CLI release, create and publish the three Thesis facade rate limits in the Vercel Firewall dashboard. The checked-in operator reference is ops/vercel-firewall/cli-auth-rate-limits.reference.json; it is not an importable migration.