Agents actually registered in the Framework
These are the agents with entries in the live C=US directory today. They are the MVP’s example agents: in production C=US registers no agents, and each agent is registered by its host, in the st= or o= directory that names it (who registers agents). Each one proves who it is with its own certificate or workload identity, has an accountable person behind it, and holds a dated grant for one narrow job; none of them can approve its own work. For each, this page asks the trust registry whether C=US authorizes its listed scope right now, and shows the latest gateway decision, including refused requests, from the signed log. Every answer and record is signed by C=US and checked in this browser.
Loading live records…
The sponsors, lots and sensor readings are synthetic, and every person's identity proofing is simulated. "Authorized now" asks about the listed scope and one example resource per agent (a lot in its jurisdiction, or o=Cequs,c=US for advisory work). "Latest gateway decision" is historical: a refusal for another scope can appear alongside a current authorization for the listed scope. The edge agents' requests are decided at Cloudflare from the registry's signed answers and are not in the C=US gateway log, so their latest decision is empty here. An advisory agent's suggestions are stored for a person to approve or reject; their full text is not published, only the titles that the gateway signed. The coffee agent's status is read from the coffee app on cequs.com and is not signed; its orders are recorded on the c=CA server.