Errors

Most tier 6–10 and edge-engine failures do not return HTTP 500. edge_payload(), risk_payload(), and every handler in tiers/routes.py catch their own exceptions and return 200 with an "error" field in the body instead. This is deliberate: a bug in one signal module should render as a broken panel, not take down the rest of the dashboard. Check the response body for an error key even on a 200.

Local dashboard API (`ghostcopy/server.py`)

Status	When	Body
`200`	Success — or a caught internal failure in the edge/risk/tier engines	JSON, may contain an `"error"` key even at `200` (see above)
`401`	`tunnel_token` is configured in `state/config.json` and the request is missing/wrong `Authorization: Bearer`	`{"error":"unauthorized"}`
`400`	Malformed `POST /act` body, or a malformed `/proof/<hash>` path	Plain text or `{"ok":false}` depending on route
`404`	Unknown call hash on `/proof/<hash>.json`, or any unmatched route	`{"error":"unknown call hash"}` on ledger routes; plain-text `nope` elsewhere — don’t assume every 404 is JSON
`503`	An optional layer (execution, forex) isn’t installed/configured	Plain-text reason

Enterprise Wallet API (`/api/enterprise/wallets/top`)

Status	Meaning
`401`	Missing, invalid, or revoked `X-API-Key`
`429`	Daily quota exhausted. The response is refused, never truncated — an empty page and a quiet market must not look the same. Body includes `resets_at` (Unix timestamp of the next UTC midnight) so you can back off correctly instead of retrying in a loop.
`200`	Success. An empty `wallets` array here is a real finding (“nothing survived the deflation”), not an error.

{ "error": "daily quota exhausted", "quota": 100, "used": 100, "remaining": 0, "resets_at": 1756044800 }

Execution relay service (`apps/api/execution/server.ts`)

Status	Meaning
`200`	Relayed, or a successful preflight
`400`	Malformed request body, or the contract’s own revert reason surfaced as text — these messages are never secret, so they’re passed through directly
`409`	Preflight failed — trade would revert on-chain. Body includes a structured `problems` array.
`404`	Unknown route

MCP server

Rate-limit and auth failures throw a typed AuthError with a descriptive message (e.g. “daily quota of 100 calls exceeded for tier free”) rather than a bare HTTP status, since MCP tools return through the Model Context Protocol, not raw HTTP, when run over stdio. See MCP Server for tier limits.

Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.

Using the API

Streaming

Intelligence service

Public HTTP endpoints

Self-hosted endpoints

MCP tools

Local dashboard API (`ghostcopy/server.py`)

Enterprise Wallet API (`/api/enterprise/wallets/top`)

Execution relay service (`apps/api/execution/server.ts`)

MCP server

​Local dashboard API (ghostcopy/server.py)

​Enterprise Wallet API (/api/enterprise/wallets/top)

​Execution relay service (apps/api/execution/server.ts)

​MCP server

Local dashboard API (`ghostcopy/server.py`)

Enterprise Wallet API (`/api/enterprise/wallets/top`)

Execution relay service (`apps/api/execution/server.ts`)

MCP server