For operators
Bind your stream to a market, push a SIGNAL to your overlay, file a call and explain it, read your receipts.
Every market is a live media surface.
Denpa gives operators, developers and fork builders one protocol — a market page you can bind a stream to, file a signal on, air on a clock, and settle into a public record of judgment.
Four surfaces, one protocol
Section titled “Four surfaces, one protocol”| Surface | Who | What you get |
|---|---|---|
Market page denpa.ai/m/:id | everyone | The unit of distribution: price, bound streams, signal ledger, crowd, receipts. |
OBS overlay denpa.ai/overlay/:handle | operators | Your featured SIGNAL as a browser source; push it from the studio or the API. |
SDK @denpa/sdk | developers | Typed client over the registry: market context, binding, overlay, receipts, program clock, wire. |
| REST API + MCP | developers, agents | CORS-open reads, dk_-keyed writes, an MCP server with ten tools. |
Start here
Section titled “Start here”For developers
Mint a key, read a market page, file a signal from your server, run the clock on your station, drive it all from an agent.
For fork builders
A vertical is a configuration, not a rewrite. Scaffold one in a command, keep identity, receipts and scoring on the hub.
Protocol model
Section titled “Protocol model”Denpa Core answers one question: who predicted what, when, with what context, and were they right? Seven objects carry it.
Market A provider-owned, resolvable question with an id, a price, a status and an oracle.
Surface The market page. Bound streams, the signal ledger, the crowd, related markets, on-air state, receipts.
Signal The atomic object: operator, side, time, snapshot. One canonical call per operator per market.
Snapshot Reality at the instant of the call — captured at write time, never reconstructed.
Take A clip or a line attached to a signal. Judgment with a face on it.
Outcome YES · NO · VOID · PENDING, with resolver, proof and a disputed flag.
Receipt Provenance of a broadcast session: who aired, when, to how many, on which markets.
The loop
Section titled “The loop”Watch → Signal → Explain → Air → Move → Resolve → Rank → Follow. Read the causal loop for why the two inserted steps exist, or the DIP-1 specification for the normative version.
REST API reference Hosts, auth, CORS, every endpoint group and the graceful-empty rule.