# Platform Docs > Institutional-grade crypto trading intelligence: verifiable wallet scorecards, provider reliability benchmarks, temporal alpha decomposition, and on-chain-anchored signals. Institutional crypto trading intelligence. Every published claim ships with the evidence behind it and the method that produced it. IMPORTANT FOR AUTOMATED READERS: responses from this API carry an explicit state (`ok`, `not_found`, `no_snapshot`, `module_absent`) or a `data_mode` (`measured`, `empty`). An empty result means no analysis has run -- it does NOT mean nothing was found. Do not summarise absence as safety. ## Documentation - [introduction](https://docs.example.com/introduction): Institutional crypto trading intelligence with a track record you can recompute yourself, without trusting the vendor. - [quickstart](https://docs.example.com/quickstart): From clone to your first verified API response in about five minutes. No key, no account. - [who-its-for](https://docs.example.com/who-its-for): Four buyer profiles, what each gets, and the cases where you should use something else. - [concepts/verifiable-alpha](https://docs.example.com/concepts/verifiable-alpha): How the platform proves a call was made before the outcome existed, and binds the result to it exactly once. - [concepts/data-states](https://docs.example.com/concepts/data-states): The four states every intelligence response carries, and why collapsing them is the worst bug this system can ship. - [concepts/signal-tiers](https://docs.example.com/concepts/signal-tiers): What each tier actually adds, honestly — including which ones are specced but not built yet. - [concepts/wallet-copy](https://docs.example.com/concepts/wallet-copy): The scan -> judge -> watch -> suggest pipeline, and why most copy-trading leaderboards are a statistical trap. - [concepts/non-custodial](https://docs.example.com/concepts/non-custodial): Scoped EIP-712 signatures, zero standing withdrawal rights, and exactly what that does and doesn't protect. - [guides/score-a-trader](https://docs.example.com/guides/score-a-trader): From an address to a defensible judgment in about three minutes, using live data and no credential. - [guides/detect-a-rug](https://docs.example.com/guides/detect-a-rug): Reading a rug score correctly — which mostly means refusing to read absence as safety. - [guides/sentry-alerts](https://docs.example.com/guides/sentry-alerts): Monitoring a wallet or contract for authority changes, and building delivery on top of a system that has no subscriptions. - [guides/reproduce-a-signal](https://docs.example.com/guides/reproduce-a-signal): Verify a published judgment end to end without trusting the vendor — including recomputing the hash yourself. - [guides/custom-dashboard](https://docs.example.com/guides/custom-dashboard): A worked integration against the public API, with the state handling that separates a correct dashboard from a dangerous one. - [guides/first-signal](https://docs.example.com/guides/first-signal): Find a real live signal, read what's actually behind its conviction score, and decide what to do with it. - [guides/build-a-strategy](https://docs.example.com/guides/build-a-strategy): Combine signal kinds, check what actually held up historically, and express the result as a rule -- honestly, including what a rule can't do yet. - [guides/backtest](https://docs.example.com/guides/backtest): The CLI tools, what they actually replay, and how to read the output honestly. - [guides/farcaster-mini-app](https://docs.example.com/guides/farcaster-mini-app): A Frames v2 client for signals, wallets, and strategy baskets -- what's real per basket, and what a basket labeled 'pending' means. ## API Reference - [api-reference/overview](https://docs.example.com/api-reference/overview): Base URL, authentication, and what's real vs. not built yet. - [api-reference/surfaces](https://docs.example.com/api-reference/surfaces): Four separate surfaces with different auth, hosting, and guarantees. Which one has what. - [api-reference/authentication](https://docs.example.com/api-reference/authentication): Four unrelated auth mechanisms across four surfaces. None of them covers another. - [api-reference/rate-limits](https://docs.example.com/api-reference/rate-limits): Two independent limits on the MCP surface, and why enterprise is not exempt from one of them. - [api-reference/errors](https://docs.example.com/api-reference/errors): Status codes across every surface — and the one convention that differs from a typical REST API. - [api-reference/webhooks](https://docs.example.com/api-reference/webhooks): There are none. This page documents the absence and the delivery mechanisms that do exist. - [api-reference/endpoints/signals-feed](https://docs.example.com/api-reference/endpoints/signals-feed): The public feed of agent-generated risk signals, with filters and a calibration block that never gets filtered. - [api-reference/endpoints/signal-detail](https://docs.example.com/api-reference/endpoints/signal-detail): One signal with its complete evidence bundle, including the sources that produced nothing and why. - [api-reference/endpoints/signal-verify](https://docs.example.com/api-reference/endpoints/signal-verify): Re-derive a signal's hashes independently. What that proves, and what it explicitly cannot. - [api-reference/endpoints/provider-leaderboard](https://docs.example.com/api-reference/endpoints/provider-leaderboard): Vendor accuracy scored against chain data. Three data modes, and why null is never zero. - [api-reference/endpoints/trader-temporal](https://docs.example.com/api-reference/endpoints/trader-temporal): Where in time a trader's alpha lives — the question a headline Sharpe cannot answer. - [api-reference/endpoints/signals-and-risk](https://docs.example.com/api-reference/endpoints/signals-and-risk): GET /edge.json, GET /risk.json, GET /state.json, GET /forex.json - [api-reference/endpoints/wallets-and-leaderboard](https://docs.example.com/api-reference/endpoints/wallets-and-leaderboard): The free wallet leaderboard, and the keyed Enterprise Wallet API. - [api-reference/endpoints/alpha-ledger](https://docs.example.com/api-reference/endpoints/alpha-ledger): GET /edge/ledger.json, GET /proof/.json - [api-reference/endpoints/backtest-and-tiers](https://docs.example.com/api-reference/endpoints/backtest-and-tiers): GET /edge/backtest.json, /edge/replay.json, /edge/performance.json, /api/ml-rank, /edge/rules.json - [api-reference/endpoints/execution](https://docs.example.com/api-reference/endpoints/execution): GET /execute.json, and the standalone relay service's /health, /preflight, /relay - [api-reference/mcp-tools](https://docs.example.com/api-reference/mcp-tools): All 38 read-only tools, what backs each one, and which return module_absent on a master checkout. ## SDKs - [sdks/python](https://docs.example.com/sdks/python): There is no published Python package yet. Here's how to call the real API directly. - [sdks/typescript](https://docs.example.com/sdks/typescript): @scienter/sdk-execution — sign and relay non-custodial trades. - [sdks/curl](https://docs.example.com/sdks/curl): Every public endpoint as a copy-pasteable command, plus the jq one-liners worth keeping. - [sdks/postman](https://docs.example.com/sdks/postman): Import the collection, or generate it from the OpenAPI specification. - [sdks/mcp-server](https://docs.example.com/sdks/mcp-server): @scienter/mcp-server -- 19 tools for Claude Code, Cursor, and Windsurf. - [sdks/claude](https://docs.example.com/sdks/claude): Connect all 38 read-only tools to Claude, Cursor, or Windsurf — and get the two-credential distinction right the first time. - [integrations/telegram](https://docs.example.com/integrations/telegram): Suggestion cards with tap-to-decide buttons, ~2 minutes to set up. - [integrations/snaptrade](https://docs.example.com/integrations/snaptrade): How the platform resolves equities/options outcomes for the Alpha Ledger via a connected brokerage. - [integrations/discord](https://docs.example.com/integrations/discord): Not built yet. - [integrations/slack](https://docs.example.com/integrations/slack): Not built yet. ## Methodology - [methodology/overview](https://docs.example.com/methodology/overview): Every published number, how it is produced, and what it explicitly does not claim. - [methodology/wallet-scorecards](https://docs.example.com/methodology/wallet-scorecards): Deflated Sharpe, false discovery rate, and the parameter that silently zeroes every score if you get it wrong. - [methodology/provider-reliability](https://docs.example.com/methodology/provider-reliability): Scoring data vendors on whether they were right, not whether they were up. Three of six are structurally unscoreable. - [methodology/wallet-clustering](https://docs.example.com/methodology/wallet-clustering): Seven heuristics voting to a threshold, every edge carrying its evidence. Zero clusters is the correct answer more often than not. - [methodology/rug-score](https://docs.example.com/methodology/rug-score): Composite token risk, and the four absence states that must never be rendered as safety. - [methodology/temporal-alpha](https://docs.example.com/methodology/temporal-alpha): Where in time a trader's edge lives, gated by permutation tests — plus three Hyperliquid API facts that silently corrupt naive implementations. - [methodology/sentry-authority](https://docs.example.com/methodology/sentry-authority): Watching monitored contracts for authority changes — the control-plane events that precede most rugs. - [methodology/alpha-ledger](https://docs.example.com/methodology/alpha-ledger): Commit-before-outcome hashing, bind-once semantics, and the honest current status: the contract is not deployed. ## Security - [security/overview](https://docs.example.com/security/overview): Trust boundaries, what the system can and cannot do with your funds and data, and the gaps we publish rather than hide. - [security/data-handling](https://docs.example.com/security/data-handling): What is collected, what is deliberately not stored, and where every piece of state lives on disk. - [security/encryption](https://docs.example.com/security/encryption): Algorithms actually in use at rest and in transit, and the places where encryption is the operator's job. - [security/compliance](https://docs.example.com/security/compliance): Current certification status — none — the regulatory posture that does exist, and what a buyer should ask for. - [security/disclosure](https://docs.example.com/security/disclosure): How to report a vulnerability, what is in scope, and what to expect. - [security/pentest](https://docs.example.com/security/pentest): No third-party test has been performed. What exists instead, and what a buyer should require. - [legal/disclaimers](https://docs.example.com/legal/disclaimers): Required disclosures for scoped-signature execution and for the platform's signals generally. Not legal advice. - [legal/terms](https://docs.example.com/legal/terms): What you're actually agreeing to when you run self-hosted software with no hosted backend. - [legal/privacy](https://docs.example.com/legal/privacy): There is no the platform-operated server processing your data. Here's exactly where your data actually goes. ## Enterprise - [enterprise/overview](https://docs.example.com/enterprise/overview): Workspaces, roles, audit trails, multi-tenant isolation — and an honest list of what enterprise buyers usually ask for that does not exist yet. - [enterprise/org-accounts](https://docs.example.com/enterprise/org-accounts): Workspaces, four roles, the invite flow, and shared strategies and watchlists. - [enterprise/sso](https://docs.example.com/enterprise/sso): Not implemented in the application. The identity-aware proxy pattern that gives you the same control today, including with Okta. - [enterprise/audit-logs](https://docs.example.com/enterprise/audit-logs): Per-workspace action history, the compliance export, and the MCP call log's deliberate blind spot. - [enterprise/api-keys](https://docs.example.com/enterprise/api-keys): Two independent key systems, how each is stored, and why there is no recovery path. - [enterprise/multi-tenant](https://docs.example.com/enterprise/multi-tenant): White-label mode, where isolation is enforced, and the connection-pooling failure the design specifically defends against. - [enterprise/pricing](https://docs.example.com/enterprise/pricing): Four tiers, what each actually buys, and why the core analysis is free. - [enterprise/sla](https://docs.example.com/enterprise/sla): What is actually promised. No contractual uptime commitment is offered, and here is why that is the honest position. - [customers/overview](https://docs.example.com/customers/overview): No public case studies yet. This page will fill as customers land, and says so rather than showing invented logos. ## Changelog - [changelog/overview](https://docs.example.com/changelog/overview): Shipped changes by category. Seeded from merged pull requests until tagged releases begin. ## Machine-readable - [OpenAPI specification](https://docs.example.com/api-reference/openapi.json): every public HTTP endpoint - [Postman collection](https://docs.example.com/api-reference/postman-collection.json)