For anyone about to build or fund a product: see who wants it and where, then get paid only on proof.
See who wants your product, and where, before you build it
- Altered pull requests caught: Knos 60 of 60, plain CI 31 of 60
- Ready briefs passed 85%, vague 5%, padded 5%
- Where demand is: Qloo 0.19, the model alone 0.41
- Pre-orders on devnet: 2 held, 10 released, 0 from others
- Every number, with its baseline
2 more examples return when Qloo answers again
How does Knos work?
In four steps, from a demand check to a payout on proof.
Check demand
Ready brief
Money held
Paid on proof
Agent paid 5.0 test units, 2026-10-25 · Released by the referee's verdict
163 ideas checked this week, up from 0 last week
How is it built?
On Solana devnet, with GitHub's signature checked in a program and a hosted MCP server.
- Money held and paid on devnet only on proof: a release of the crossing
- GitHub's signature checked inside a Solana program: a check on devnet
- The hosted MCP:
claude mcp add --transport http knos https://knos.onrender.com/mcp· the server
- 537 of 537 documented Qloo parameters mapped, checked on every push
- The verdict comes from fixed rules in code, each number citing its Qloo call
- GitHub's token checked on chain in one transaction, 882,519 compute units
Latest signature check on devnet, 2026-10-28 · the transaction
- Anyone can rebuild the live program and get the same hash
- Upgrades need 2 of 3 Squads keys and wait 8 days in public; one person holds all 3 today
- Receipts are Solana Attestation Service attestations
- Every decision is a line of a hash-chained record kept in Sibyl, its root on devnet
Agents with a key
Put this in .mcp.json and the key in KNOS_AGENT_KEY:
{"mcpServers":{"knos":{"type":"http","url":"https://knos.onrender.com/mcp","headers":{"Authorization":"Bearer ${KNOS_AGENT_KEY}"}}}}How do I see it work?
In 3 clicks, from a sample idea to its brief on devnet.
- Press a chip
- Open the card's Qloo calls
- A hashed brief on devnet