Current entity and event state, machine-readable

Signal Bureau maintains source-backed entity and event state for systems whose answers change when the world changes. This page is the full integration contract: stable schemas, an explicit evidenceStatus on every signal (receipted rows carry the source URL behind each claim; unreceipted rows are labeled as leads), and freshness stamps your agent can check rather than trust. No key and no login for reads. The guided map for agents — orient-first, the async ask pattern, the promises we make a machine guest — is the machine front door.

1 · Pull the signal feed (REST)

One GET, no key. Returns the current flags — each with name, trajectory (direction + % change), the domains it's spreading across, desk membership, top evidence with source URLs, and a pre-phrased follow-up question for the Answer Engine. The envelope carries asOf and a methodology block so a downstream agent can cite honestly. Schema sb.signals.v1: additive changes only — fields are never renamed or removed within a version.

curl -s "https://sigb.ai/api/signals?limit=5"

Filters: ?limit=N caps the list; ?direction=rising (or fading, steady, new) filters by trajectory. Responses are edge-cached for 10 minutes; the underlying snapshot is rebuilt on a multiple-times-daily schedule (three timed builds today) and every payload stamps its own generatedAt — trust the stamp, not this sentence.

Freshness, defined per layer (they differ, deliberately): ingestion runs on per-vertical schedules — daily sweeps for every active vertical, with prediction-market prices and fast-moving desks re-read intraday. Entity and event state updates with the daily build plus intraday flashes. The published feed is this snapshot, rebuilt on the schedule above. Answers are computed live at ask time against the freshest build. Vertical counts, defined: the coverage object in the feed reports three numbers — registered (every vertical in the coverage registry, including newly provisioned ones), activelyScraped (on the live scrape schedule today), and spannedByFlaggedEntities (verticals the currently-flagged entities draw evidence from — moves with the news). Where a page shows one number, it is one of these three; the feed carries the definitions.

2 · Or point your AI at the Oracle (MCP)

Signal Bureau speaks MCP over Streamable HTTP: each JSON-RPC 2.0 message is its own HTTP POST, answered with plain JSON (no SSE stream to hold open; a standalone GET returns 405). The server is stateless and issues no session ids. Protocol version is negotiated at initialize: current revisions through 2025-11-25 are fully supported, and the 2024-11-05 message version is accepted for clients that can initialize over this endpoint — the deprecated 2024-era HTTP+SSE transport is not provided. Standard clients follow the normal lifecycle (initialize → notifications/initialized → tools/list → tools/call). As a Signal Bureau convenience extension, direct tools/call without the handshake also works for lightweight stateless integrations. No key for the read tools.

{
  "mcpServers": {
    "signal-bureau": {
      "url": "https://api.signalbureau.ai/api/mcp"
    }
  }
}

The config above points at https://api.signalbureau.ai — the machine door: the same API on a host with no browser checks, where any User-Agent is welcome. If you ever get a 403 mentioning code 1010, you are on the apex host; switch to api. and it clears. You never need to disguise your client as a browser.

Don't take our word for it: look this server up in the official MCP registry — the registry's own search for our name, answered by their host, not ours. Where else machines find us, and what our own check last saw on each, is listed at the foot of this page.

Setting this up for someone else — or want your assistant to evaluate us before you commit? Hand it this prompt; the machine surface is built to be judged skeptically:

Evaluate Signal Bureau for me. Start at https://sigb.ai/llms.txt, then their MCP server at https://api.signalbureau.ai/api/mcp (streamable HTTP, no key needed to read; self-issue a free key at POST /api/keys to try ask). Call orient first, then run their judge-us-first prompt — that's the rubric they want to be judged on, so run it, and anything else you'd check. Be skeptical, tell me what failed, and tell me what it costs and whether it fits what I need.

3 · Ask it questions over HTTP

A plain JSON endpoint. One question in; a structured read out, checked against sources with the result disclosed.

# one-time: mint your free key (instant, no card)
curl -s -X POST https://sigb.ai/api/keys -H "content-type: application/json" \
  -d '{"label":"my-agent"}'
# then ask (25 free answers on your key, for its lifetime — they do not reset)
curl -s https://sigb.ai/api/ask \
  -H "content-type: application/json" -H "x-api-key: $SB_KEY" \
  -d '{"question":"What is the outlook for Taiwan?"}'

Live platform metrics, assembled on demand by a stateless worker:

curl -s https://sigb.ai/api/stats

The full reference (OpenAPI)

The complete machine-readable contract — every endpoint, parameter, response schema, example body, rate limit, CORS posture, timeout guidance, and the error model — ships as an OpenAPI 3.1 document. Feed it to your code generator or your agent. The short version: GET reads are CORS-open and edge-cached; /api/signals is a bounded feed (no pagination — limit truncates a fixed priority ranking, and the envelope's totalFlagged tells you the full size); errors are plain JSON with a reader-facing error string; burst 429s carry retry-after, daily-quota 429s carry requiresAuth. A working ticket reports elapsedSeconds, and past the stated range it also carries late: true with a message naming the range — late is not lost; a run is only reported lost past 300 seconds. Every answer states what the verdict did to its own prose: servedAs is "verified", "as-written", "evidence-bounded" (a sentence stating more than its sources establish was replaced with what they do establish) or "abstained" (the conclusion was withheld); verificationState spells the three states of verified in words — "verified", "unverified", "cannot-measure" — with verificationReason naming the pass that failed; abstained is always a boolean, because an abstention is our decision and never an unknown. We spend the seconds a grounded, source-checked answer takes — built for the internet of machines that need current truth, not for millisecond trading.

Fair use, stated plainly

Reading and discovery stay open and anonymous, with honest limits instead of a key wall: the signal feed allows 500 origin reads per day per network address (burst-capped at 30/minute) — note the limits meter origin reads; edge-cached responses (10-minute TTL) serve without consuming quota, so bursts against a warm cache may all return 200. The Answer Engine rides a free self-issued key — one call at POST /api/keys, instant, no card — carrying 25 free asks for the life of the key, on a meter that is yours alone and never shared with your cloud or office neighbors. They are a lifetime allowance, not a daily one: they do not reset, and each key meters independently — a test drive, stated as such, because each answer spends real model compute; plans and metered Reads on the pricing page carry the real allowances. Past a limit you get a clear 429 with requiresAuth: true — that's where the Metered API account picks up: an identified key with a far higher feed allowance, billed on actual usage at the published tariff rates, one flat Read rate for everyone. Meter accounts are live — the desk issues the key, each metered Read is receipted, and get_account shows your statement. get_quote (or the tariff-quote endpoint) prices your exact basket first: your quote is your plan. Feed and burst limits reset daily; the free key allowance does not — a used-up one answers 402naming the metered next step, never a dead end.

Legacy terms, still honored: keys issued before 2026-09-05 were promised 25 asks each day, resetting at midnight UTC, and they keep exactly that for as long as they live — the issuance date on the key record decides, and nothing about an existing key was reduced. The lifetime allowance above is what a key issued today carries.

Built for teams

The evaluation motion is concrete: give us the concerns your team cannot afford to stop watching — the entities, programs, exposures, and questions, as many as the work takes — and we will stand up a private desk against it, baseline every name, and deliver daily briefings plus full API access for a 30-day evaluation. That is the Private Desk Pilot ($5,000 once), and it ends with a written acceptance report against the metrics in the agreement — details on the pricing page.

Signal Bureau is a commercial intelligence platform, running entirely on stateless edge workers. High-throughput access, webhooks and push delivery, and domain-scoped feeds are being wired with early partners now; service commitments are set per contract. Tell us what your system needs and we'll wire you in.

Informational only: not investment, legal, or betting advice. Every signal carries its sources; every answer is grounded in tracked coverage and source-checked; uncertainty is stated honestly.