Skip to content
costheta logo

costheta

Returns signed, recomputable random outcomes derived from a cosmic-ray muon detector event recorded after a committed option list.
At a glanceswept Oct 24, 2026

not read yet

Use

For
AI agents and their operators who need auditable decisions backed by physical detector evidence
Runs as
API
Used for
  • Commit a choice before a detector event fixes the result
  • Obtain a signed certificate for a challenged decision
  • Draw public random bits from a detector pulse
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 26, 2026
  • MCP serverdev.costheta/costhetaverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-26
  • Address to connectcostheta.dev/mcp
  • OpenAPI spec21 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Securityby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare costheta with

Pick up to two.

All 10 alternatives to costheta →

All Security tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use costheta for?

Sign in to leave a note
Questions this page answers
  • What is costheta?

    Returns signed, recomputable random outcomes derived from a cosmic-ray muon detector event recorded after a committed option list. It is listed in the Atlas under Security.

  • Who is costheta for?

    AI agents and their operators who need auditable decisions backed by physical detector evidence

  • Do people use costheta?

    Little sign of use.

  • What are alternatives to costheta?

    In Security, by use: HaltState, Phronesis, COSTRINITY, Cloudflare, Lumo by Proton, Brave.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk