The Confluence Show for developers and AI agents

What is available

• REST API at https://api.theconfluence.show — the market-structure data behind the show, behind an entitlement per market; nothing on it connects to an exchange or places orders. Public OpenAPI 3.1 spec.
• MCP server at https://mcp.theconfluence.show/mcp — the same data as tools for Claude, ChatGPT and other agents (Streamable HTTP).
• Official CLI: the npm package tcs-show (binary: tcs) — markets, candles, tokens and the MCP from the terminal.
• The whole site as markdown: https://theconfluence.show/llms.txt, https://theconfluence.show/llms-full.txt, a markdown mirror of every article, and content negotiation on the canonical URLs.

REST API

Base URL https://api.theconfluence.show. The OpenAPI specification is public and self-describing: every operation has a stable operationId (the handler name), a description, typed parameters, a response schema where one is declared, and the scope it needs under security.

• https://api.theconfluence.show/openapi.json — OpenAPI 3.1 spec
• https://api.theconfluence.show/docs — Swagger UI (use Authorize with your API key)
• https://api.theconfluence.show/redoc — ReDoc
• Public, no token: GET /healthz, GET /symbols, GET /markets, GET /stripe/status
• Everything else: Authorization: Bearer <token>; WebSocket /ws/live takes the same token as ?token=

curl https://api.theconfluence.show/symbols

curl -H "Authorization: Bearer tcs_…" \
  "https://api.theconfluence.show/candles?coin=BTC&interval=1m&start=1755900000000&end=1755903600000"

Authentication and scopes

Two kinds of Bearer token are accepted on the same header: an API key (tcs_…) or a browser session token. API keys are self-serve: any signed-in account can create up to 5 of its own from the account page — each key inherits the role and market entitlements of its owner, never expires and can be revoked at any time. The key value is shown once, at creation. Team-issued keys continue to exist and work unchanged.

The same key management is exposed over the API for the signed-in account: GET /auth/apikeys lists your keys, POST /auth/apikeys with a name creates one (the response is the only time the key is returned), POST /auth/apikeys/revoke retires one by id.

Permissions follow the role of the account, not the token. The three scopes are declared per operation in the spec and listed in the RFC 9728 protected-resource metadata:

• hrc:read — market data for the markets the account is entitled to (any authenticated account).
• hrc:team — coverage, statistics and article publishing (team and admin roles).
• hrc:admin — user, key and entitlement management (admin role).

Unauthenticated requests get a 401 with a WWW-Authenticate: Bearer challenge that points at that metadata. Keys are not part of the 7-day trial of the live room.

• Protected-resource metadata (RFC 9728)
• Create your API keys

OAuth 2.0 (client credentials)

API keys also work as OAuth 2.0 client credentials: exchange one at the token endpoint for a short-lived access token, and send that as the Bearer instead of the raw key. The grant is client_credentials and the API key travels as the client_secret — HTTP Basic or form body, both accepted.

• Token endpoint: POST https://api.theconfluence.show/oauth/token with grant_type=client_credentials and the API key as client_secret.
• Response: access_token, token_type "Bearer", expires_in 3600, and the scope granted to the key's owner (e.g. "hrc:read hrc:team").
• Authorization-server metadata (RFC 8414): https://api.theconfluence.show/.well-known/oauth-authorization-server.

curl -X POST https://api.theconfluence.show/oauth/token \
  -d grant_type=client_credentials \
  -d client_secret=tcs_…

{"access_token":"…","token_type":"Bearer","expires_in":3600,
 "scope":"hrc:read hrc:team"}

• Authorization-server metadata (RFC 8414)

Rate limits and versioning

• Rate limit: 600 requests per minute per IP on https://api.theconfluence.show. Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, plus RateLimit-Policy: "600;w=60". Go over and you get a 429 with a Retry-After header.
• Every response carries X-API-Version, a date-based version of the API. Backwards-incompatible changes are announced in advance with Deprecation and Sunset headers on the affected operations, at least 90 days before they take effect.

MCP server

https://mcp.theconfluence.show/mcp speaks the Model Context Protocol over Streamable HTTP with JSON responses. initialize, ping and tools/list are public, so any client can discover the tools; tools/call needs the same Bearer API key as the REST API (team role). All tools are read-only and declare it (readOnlyHint).

• list_markets
• data_coverage
• market_snapshot
• bundle_fields
• signal_events
• setups
• coach_feed
• screen_markets
• history
• sql
• stats

claude mcp add --transport http hrc https://mcp.theconfluence.show/mcp \
  --header "Authorization: Bearer tcs_…"

• MCP protected-resource metadata

CLI

The official CLI ships as the npm package tcs-show; the binary is tcs. It speaks to the same REST API with the same API key (set it once, or mint OAuth tokens with tcs token) and covers markets, candles, token, whoami and mcp.

npm install -g tcs-show

tcs whoami     # which account your key resolves to
tcs markets    # every served market
tcs token      # mint an OAuth access token from your key

Machine-readable content

• https://theconfluence.show/llms.txt — site index for agents (llmstxt.org); https://theconfluence.show/llms-full.txt — the full research library in one file.
• Every article at https://theconfluence.show/md/<cluster>/<slug> as raw markdown; clusters are learn, compare and reports.
• Content negotiation: request any article URL, the home page, /faq, /about, /contact or /developers with Accept: text/markdown and you get markdown from the same URL (Vary: Accept; Link: rel="alternate" announces the mirror). Appending .md to those URLs works too.
• https://theconfluence.show/sitemap.xml and https://theconfluence.show/rss.xml — every public URL and the latest articles.
• Unknown URLs return a real HTTP 404 with a short markdown body pointing at the index.

curl -H "Accept: text/markdown" https://theconfluence.show/learn/cvd-explained

Limits and conduct

• Market data is read-only and nothing on the API connects to an exchange or places orders. The write operations are billing for the signed-in account (/stripe/*), chart drawings, article publishing (hrc:team) and administration (hrc:admin) — each declared with its scope in the spec.
• The published rate limit is 600 requests per minute per IP (see Rate limits and versioning above); cache what you can, and an abusive key can still be revoked.
• Everything served is educational market analysis, not financial advice and never a trade signal. Use is governed by the Terms of Service.

• Terms of Service
• About the company