Skip to main content
Choose the path your client supports. Browser sign-in is available to approved clients; coding clients can also connect with an API key.

Explore docs

Search public integration guides without a key. No investor records.

Sign in

Authorize a supported AI client in your browser.

Use an API key

Add a Bearer key to an HTTP MCP client.

​
Connect

OAuth-capable clients use one public endpoint and browser sign-in. Open registration remains fail-closed until the public admission gate passes.
Check current client availability before signup or payment. Public directory listings and OAuth access differ by client. If your AI cannot connect, stop before paying. For a trusted coding agent that can use HTTPS and store a secret, give it this prompt:
Approve account access and any payment in your browser. Configure Codex, Claude Code, Cursor, or OpenCode with an API key if you prefer to set up MCP yourself. Manage an existing connection in your account.

​
How it works

The client discovers authorization metadata, the user signs in on BeliefState, and the approved client receives a revocable read-only grant.
  • No BeliefState SDK is required.
  • All admitted clients use the same remote Streamable HTTP endpoint.
  • MCP tools use the same read services, release gates, pricing policy, and append-only usage ledger as REST.
  • Client compatibility and provider approval are verified separately.

​
Verify

The agent verifies its own response: requested ticker, data mode, coverage warnings, and citations. Report missing access or coverage as a blocked step; a configured server alone does not prove a useful result.

​
Documentation for agents

Give your coding agent current API references and integration guides without an API key or sign-in. Add this public documentation endpoint to an MCP-compatible client.
  • search_docs (Read only). Search current BeliefState guides and API references. Returns ranked pages with short excerpts.
  • read_docs (Read only). Read current docs as Markdown: supply path and optional section (heading or anchor), or pages for up to 8 reads in one call. Search anchors also work as URL fragments. Unknown selections return per-page errors. Responses are bounded to 120,000 characters; request sections for larger batches.
  • submit_docs_feedback (Records feedback). Report whether one documentation page was useful, with an optional concise correction or missing detail.
Your client can also read every public documentation page and the published agent skills as Markdown resources. The documentation server provides no investor records. Use the authenticated intelligence endpoint above for investor queries.

​
Automatic discovery

Find both MCP endpoints and their authentication requirements from one public document. Clients that support this discovery convention can locate the servers from the BeliefState site URL.
The discovery document defaults to public documentation and lists the intelligence endpoint with OAuth authentication. It is also available at /.well-known/mcp.json. The documentation card includes tool descriptions, input schemas, bounds, and read/write annotations from the running server’s definitions. Discovery does not grant access or change client admission requirements.

​
Security

Leave passwords, consent, workspace selection, and provider-admin approval with the user.
An AI must never ask for the user’s password, session, OAuth access token, or developer API key.

​
Agent feedback

Report unclear, stale, or incorrect documentation through BeliefState support. Include this page URL and the smallest reproducible detail. Last updated: 2026-09-27 · API version: v1 (Latest) · OpenAPI publication: 2026-09-13.