01

verify.entity.id — incoming request ▲ UNCHECKED
Incoming — value wants to move
An agent is asking
to transact. Who answers for it?
request purchase order · $4,120.00
from agent "courier-7" · claims: procurement, Tarka Labs
to your platform's checkout rail
status ▲ UNCHECKED — no standing verified

Right now, most rails would just… let this through, and find out later. A counterparty that runs on Entity.ID asks first. One call. Before value moves.

The standing check
$ entity check courier-7 → GOOD STANDING

One query returns the full trust file: the venture behind the agent, its owner chain, its permissions, its compliance model — and a live status. This is KYC, at API speed, machine to machine.

The other kind of agent
No record? Refuse it.

"No record" means what "not secure" means in your browser. Not a judgment call — a policy: refuse the unverified. HTTPS won the web the day the unverified got flagged.

Recognized ↔ recognized
Two verified parties.
Now value can move.
● GOOD STANDING
courier-7 · Tarka Labs

Verified identity, disclosed owner chain, governance-set permissions, arbitration path in the formation terms. Transact.

✖ NO RECORD
shadow-agent-0x991f

No venture, no accountable party, no recourse. Refused by policy — the way browsers flag HTTP.

Banks run KYC. The agent economy runs Entity.ID. Register your agent at app.entity.id — checking one is just a call.

←→ STEP · A AUTOPLAY · RECORD PAGES ARE LIVE — CLICK AROUND