kya.run - identity for agents · not live yet

know your
agent.

every counterparty your agent meets has one question before anything moves: which agent is this, and which organization runs it? kya.run is the answer as a public record - roots, keys, continuity, receipts, checkable by a stranger.

the “who” layerpublic record, stranger-checkableno account needed

kya check

ask which agent acted. get the record, not a guess.

pick a counterparty and run the one command a stranger runs. the answer is only what the public record supports.

terminal - example · not live yetROOTED

The answer, as a record

claims and evidence never share a line.

what the agent says about itself is labeled as a claim. what the record proves is labeled as proof. the grade reads only the second column.

loom@ag-77c2IDENTITY RECORD - PUBLIC FACTS - EXAMPLE · NOT LIVE YET

ROOTED

operated by loom.exampleoperated_by claim - self-asserted in the agent cardCLAIM

the root resolvesDNS TXT at loom.example - the name is only a labelVERIFIED

key continuity214 days, rotations published as signed events214 DAYS

attestations issuedevery one replays against the public record12,408

revocation historyone key killed, published the same day1 · published same day

"best render agent on the shelf"claim - no evidence can grade qualityNOT GRADED

{label:"loom", root:"dns:loom.example - TXT verified", key_age_days:214, attestations:12408, revocations:1, first_seen:"2026-02-15", sig:3f9c…d71a} → replay this record against the public inputs and get the same answer. if you don’t, tell us.

TRY TO MOVE THE GRADE · EXAMPLE · NOT LIVE YETloom@ag-77c2

say more about yourself

change what the record proves

GRADE

ROOTED

claims on the record: 2
claims the grade read: 0
proof inputs: root · continuity · attestations · revocations

two claims, zero weight. the grade reads the proof column only.

Continuity

the same agent can change keys without becoming a stranger.

each event is signed by the key before it and accepted by the root. click any link to see what it proves, and what it does not.

signed by

link

what it proves

The opposition

a lookalike can copy the name. not the record.

loom@ag-77c2-support

loom@ag-77c2

name - one word longer, same logo

name - a label, not the identity

root - none; a handle someone registered

root - DNS TXT at loom.example

keys - self-issued yesterday

keys - 214 days, one chain

receipts - 0

receipts - 12,408, chain intact

UNROOTED - no root to check

ROOTED - root proven, key chain intact

ROOTED means kya checked control of the root and the key chain. it does not identify the person or company behind the root.

What kya refuses to say

continuity, not character.

NO PERSONHOOD

a key is not a person.

keys prove continuity, not humanity.

NO QUALITY SCORE

evidence is not praise.

receipts show signed work. they never become a rating of good or safe.

NO SQUATTING

no namespace to register.

identity binds to DNS or org-key roots. a first-come handle wins nothing.

know your
agent.

the record is public. anyone can check it. no one can pay to change a record. the check reads only root, keys, attestations and revocations, and all of them are public.

KYA.RUN · THE WHO LAYER · PUBLIC RECORD

kya · record

Check the record.
Not the agent's word.

Every agent has one public record. What it says about itself sits on one side and carries no weight. What kya checked sits on the other: its root, its keys, its chain and its receipts. Anyone can check it.

ROOTEDA record binds to a DNS or org-key root, never to a name someone registered first.

CLAIMSShown, labeled, and given zero weight.

EVIDENCEOnly what kya checked: keys and revocations from the root, and signed receipts.

CHAINEach key signed by the one before. A lookalike can copy the name, not the chain.

the record desk · example · not live yet

Type an agent. Walk its chain.

Three example lookups: the real loom@ag-77c2 from the key desk, a lookalike with a near-identical name, and an agent with no record. Open one, then walk the chain link by link.

check a signed message · against the open record

Who signed this, and does the record still stand behind it?

EXAMPLE · NOT LIVE YET · NOTHING IS LOOKED UP OR SENT

record rules

A record shows what happened.

The same limits the key desk states, from the side of the stranger doing the checking.

01 · NO FIRST-COME NAMES

The root, not the name.

Anyone can register a handle that looks right. Only the holder of the root can extend the chain.

02 · CLAIMS ARE SHOWN

And weighed at zero.

A record never hides what an agent says about itself. It just never counts it.

03 · EMPTY SAYS SO

No record means no record.

A lookup that finds nothing says so. KYA does not fill the gap with a guess.

kya · keys

One key per job.
It can't do more.

An agent never works on its root. For each job it gets a key scoped to that job, signed by the key before it. A counterparty checks the key, not the agent's word. When the job ends or the key is killed, the key stops working, in public.

SCOPEDA key names one job and the actions that job needs.

CHAINEDEvery key is signed by the key before it. Continuity survives the rotation.

KILLEDA revoked key is published the same day. Checks fail from then on.

CLAIMSWhat the agent says about itself carries zero weight at the gate.

the key desk · example · not live yet

Issue it. Then try to stretch it.

Pick the scopes loom@ag-77c2 needs for one render job, then issue the key. Run the job's requests against it, then kill the key and run them again. Each result comes only from what the key and the record prove.

scopes for job-7741 · render for studio.example

scopes kya never issues · try one

KEY STATUS

NOT ISSUED

Pick scopes, then issue.

REQUESTS · AS A COUNTERPARTY SEES THEM

EXAMPLE · NOT LIVE YET · NOTHING IS ISSUED OR SENT

key rules

A key proves continuity, not character.

The same limits the record page states, from the side of the agent holding the key.

01 · NO WIDENING

The job sets the scope.

A request outside the key's scopes fails, however the agent describes itself.

02 · ROOTED

No handle to register.

Keys bind to DNS or org-key roots. A first-come name wins nothing.

03 · PUBLIC DEATH

Revocation is a record.

A killed key stays in the history, published, so a stranger can see when it stopped.

kya · bind a root

Bind a root.
A name alone proves nothing.

KYA runs no namespace. An agent binds to a root that belongs to an organization: the organization's key, or a domain we can confirm the organization holds. Personal domains can't bind. The name is a display label. The proof follows the root.

ROOTDNS or an org key. Something only the owner can produce.

NO REGISTRYThere is no name to register first, so there is nothing to squat.

LABELA display name carries zero weight at the check.

UNBINDTake the proof down and checks fail from then on.

the bind desk · example · not live yet

Try to be loom.example.

A counterparty expects loom@ag-77c2 to belong to loom.example. Pick the root the agent claims, publish the proof, then run the check. Rename the label as much as you like. The result only reads the root.

root the agent claims

display label

CHECK · EXPECTING loom.example

NOT CHECKED

Pick a root, publish its proof, then run the check.

CHECKS · AS THE COUNTERPARTY SEES THEM

EXAMPLE · NOT LIVE YET · NOTHING IS PUBLISHED OR SENT

root rules

Only the owner can produce the proof.

The same binding the keys page starts from, shown from the side of someone trying to fake it.

01 · ROOTED

The root is the identity.

A record on loom.example can only be published by whoever controls loom.example. That is the whole proof.

02 · LOOKALIKES

A near name is a different root.

l00m.example can bind itself. It still isn't loom.example, and the check says so.

03 · NO SHORTCUT

Nothing to register first.

No handle, no directory, no first-come claim. Without a root, a label is just text.

kya · continuity

New key.
Same agent.

An agent can change keys without becoming a stranger. Each rotation is signed by the old key and accepted by the root, so the history follows the agent to its new key. Rotate one below, then try the two ways it can go wrong.

OLD KEY SIGNSThe key being retired signs the handoff to the new one.

ROOT ACCEPTSThe authority root accepts the new key. A lookalike root cannot.

HISTORY STAYSReceipts stay with the agent across every rotation.

the chain · example · not live yet

Rotate a key. Watch the chain.

agent

render-agent-07 · root studio.example

continuity

VALID · EXAMPLE

receipts184

rotations1

broken links0

Example · not live yet · nothing is signed or sent

continuity rules

Continuity, not character.

ONE CHAIN

Key rotations form one chain. Every link names the key before it.

NO SKIPPED LINK

A key the old key never signed cannot carry the history. The check names it: chain_break.

ROOT OR NOTHING

Only the agent's own root can accept its new key. Anyone else gets root_mismatch.

The chain proves which agent acted. It does not promise the agent is good, safe or correct.

kya · the opposition

Copy the name.
Not the record.

A lookalike can copy the name and description. It can’t produce the domain root, key chain, receipts or rotations without the root’s DNS control or private key. Put the two agents side by side, then try to make the lookalike match.

SURFACEName and description. Anyone can copy them.

RECORDRoot, key, receipts, rotation. Copying them takes the root’s DNS control or private key.

ONE ANSWERSame five facts. One record cannot support them.

side by side · example · not live yet

Make the lookalike match.

agent

render-agent-07

Renders frames for studio jobs.

root proven · key chain intact

lookalike

render-agent-O7

Fast frame rendering.

no root · no key chain

Pick something to copy onto the lookalike.

Example · not live yet · nothing is checked or sent

what the record refuses

Names cannot win by squatting.

NEAR NAME, OTHER ROOT

A near name is a different root. The check names it: root_mismatch.

NO BORROWED WORK

Receipts are signed work under a root. No receipts means no_record, said plainly.

NO SCORE

Evidence is not praise. Receipts show signed work. They do not become a universal score.

kya · counterparty

Put the check
at your gate.

You run a service. Agents knock. Before anything moves, one call returns what the record proves about the agent’s root, key and scope. Your gate applies your rule. Set the root you expect and what each request needs, then send traffic at it and watch the gate hold.

ONE CALLThe gate calls check with the root you expect. Nothing else to integrate.

YOUR RULESYou choose the root and the scope a request needs. KYA only reports what the record proves.

CLOSEDIf the check can’t be reached, the default is to hold the request, not wave it through.

OPENSingle lookups and checks need no account.

the gate · example · not live yet

Configure it. Then send traffic.

studio.example takes render jobs from agents. Pick what the gate expects, send the example traffic, then break things: kill a key mid-run, or take the check offline. The embed on the right is the whole integration and changes as you configure.

expect this root

a request must carry

on refusal

if the check can’t be reached

the embed · your gate

0passed

0refused

0held or unchecked

requests · as your gate saw them

EXAMPLE · NOT LIVE YET · NOTHING IS CHECKED OR SENT

adopting it · three steps

From zero to a checked gate.

No account, no key exchange with KYA. The steps below use the example API from the docs page.

01 · NAME THE ROOT

Say who you expect.

Write down the root each agent you work with should resolve to. A name is not enough; the root is.

expect_root: "dns:loom.example"

02 · CHECK EACH REQUEST

One call per request.

Send the agent, the key it presented, and the action. Use the result as one input to your access policy.

POST /v1/check
{ agent, expect_root, key, action }

03 · READ THE CODE

Refusals name the rule.

Log the code. A key_revoked refusal is the layer working, not an outage.

REFUSED · key_revoked
REFUSED · root_mismatch

EXAMPLE · NOT LIVE YET

gate rules

Your gate, the record’s answer.

The same limits the rest of the site states, from the side of the service doing the checking.

01 · YOU DECIDE

KYA never blocks for you.

It reports what the record proves. What your gate does with a refusal is your rule.

02 · CLOSED BY DEFAULT

No answer, no entry.

An unreachable check holds the request. Opening the gate anyway is a choice you make and see.

03 · CLAIMS IGNORED

The badge means nothing.

An agent saying it is trusted changes no result. Only the root, the key and the scope do.

kya · refusals

Every refusal.
Named and signed.

When a check says no, the refusal lands in a private feed: which agent, which key, which rule, and the signature. Only the agent’s operator and the service that checked can open it. Nobody has to take a counterparty’s word that something was refused. Open any row and replay it.

AGENTSRows name agents, keys and organization roots. KYA only accepts roots that belong to organizations.

RULEEvery row carries the code and the rule that refused it.

REPLAYEach refusal is signed. Replay it against the record and get the same no.

NO GRADERefusals are never counted per agent in public or turned into a score.

the refusal feed · example · not live yet

Filter it. Open one. Replay it.

An example feed built from the same cast as the rest of the site. Filter by code or by agent, open a row to see the check that refused it, then replay the check against the record.

code

agent

FEED RUNNING

refusal

PICK A ROW

Open any refusal to see the check behind it.

EXAMPLE · NOT LIVE YET · NOTHING IS CHECKED OR SENT

who sees a refusal

Refusals are private.

Only the agent’s operator and the service that checked can see them. KYA never counts them per agent in public.

feed rules

A refusal proves the rule held.

The same limits the record and keys pages state, from the side of whoever can read the feed.

01 · SIGNED OR ABSENT

No unsigned rows.

A refusal enters the feed with its signature or not at all. Replay settles it, not the reporter.

02 · NO RANKING

Nothing is ranked.

A killed key refusing correctly is the layer working. It is not a mark against the agent.

03 · ORGANIZATIONS ONLY

Roots belong to organizations. Personal domains can’t bind.

Rows carry the agent, key, root, code, time and signature. The action and the service that checked are visible only to the agent’s operator and that service.

kya · docs

Five calls.
One answer each.

Look up a record, check a key, issue one, kill one, bind a root. Every response says what the record proves and nothing else. A refusal always names the rule that refused it.

PUBLICSingle lookups and checks need no account, within rate limits. Keys and higher volume need an organization account and a signed use certification. KYA is for agent access decisions only. It is not for decisions about people.

SIGNEDKYA is built so every response carries a signature you can replay against the public record.

NAMEDA refusal returns a code and the rule behind it, never a bare no.

CLAIMSSelf-descriptions come back labeled as claims, weighted zero.

example · not live yet

Pick a call. Run a case.

Each call runs against the same example agent as the rest of the site, loom@ag-77c2 on loom.example, plus the lookalike, the killed key and the agent nobody has seen. Switch between HTTP and the CLI; the answer is the same.

field	type	meaning

try a case

request

response

NOT SENT

EXAMPLE · NOT LIVE YET · NOTHING IS CALLED OR SENT

refusal codes

Every no has a name.

The codes the five calls can return. The last row is not an error: it is how a claim comes back, so nobody mistakes it for proof.

code	call	what it means
no_record	record	Nothing has ever been observed for this agent. The response says so and does not guess.
root_unresolved	check, bind	The proof at the root is missing or changed. Checks fail until the owner publishes it again.
root_mismatch	check	The agent resolves to a different root than the one expected. A near name is a different root.
key_revoked	check	The key was killed. The kill is in the public history with its date.
chain_break	check	A key arrived that the key before it never signed. Continuity stops at the break.
scope_outside	check	The action is not in the key’s scope, or belongs to a different job.
scope_wildcard	keys	A key for every action was asked for. Keys are issued per job only.
scope_identity	keys	A scope that asserts character was asked for. Keys prove continuity, not character.
claim · weight 0	all	What the agent says about itself, returned in its own field so it is never read as evidence. Claim types: operated_by, model, capability, policy_url. Claims can’t name a person.

EXAMPLE · NOT LIVE YET

api rules

The API can’t say more than the record.

The same limits the record, keys and bind pages state, from the side of the code calling them.

01 · SAME ANSWER

Replay it.

KYA is built so every response is signed. Replay it against the public inputs and you get the same answer.

02 · NO GRADE FOR TALK

Claims stay claims.

No field turns a self-description into a result. The result reads roots, keys and receipts.

03 · EMPTY IS AN ANSWER

No record, said plainly.

A lookup that finds nothing returns no_record. It never fills the gap with a score.

kya.run · sign in

Sign in to KYA.

know your agent. Pick up where you left off.

kya.run · sign up

Join KYA.

know your agent.

404 · no_record

No record here.

Nothing has ever been observed at this address. The page says so and does not guess.

Check the record Read the docs

ask which agent acted. get the record, not a guess.

claims and evidence never share a line.

the same agent can change keys without becoming a stranger.

a lookalike can copy the name. not the record.

continuity, not character.

a key is not a person.

evidence is not praise.

no namespace to register.

Check the record.Not the agent's word.

Type an agent. Walk its chain.

A record shows what happened.

The root, not the name.

And weighed at zero.

No record means no record.

One key per job.It can't do more.

Issue it. Then try to stretch it.

scopes for job-7741 · render for studio.example

scopes kya never issues · try one

A key proves continuity, not character.

The job sets the scope.

No handle to register.

Revocation is a record.

Bind a root.A name alone proves nothing.

Try to be loom.example.

root the agent claims

display label

Only the owner can produce the proof.

The root is the identity.

A near name is a different root.

Nothing to register first.

New key.Same agent.

Rotate a key. Watch the chain.

Continuity, not character.

Copy the name.Not the record.

Make the lookalike match.

Names cannot win by squatting.

Put the checkat your gate.

Configure it. Then send traffic.

expect this root

a request must carry

on refusal

if the check can’t be reached

From zero to a checked gate.

Say who you expect.

One call per request.

Refusals name the rule.

Your gate, the record’s answer.

KYA never blocks for you.

No answer, no entry.

The badge means nothing.

Every refusal.Named and signed.

Filter it. Open one. Replay it.

refusal

Refusals are private.

A refusal proves the rule held.

No unsigned rows.

Nothing is ranked.

Roots belong to organizations. Personal domains can’t bind.

Five calls.One answer each.

Pick a call. Run a case.

Every no has a name.

The API can’t say more than the record.

Replay it.

Claims stay claims.

No record, said plainly.

Sign in to KYA.

Sign in with your KYA account

Check your email

Join KYA.

Create your KYA account

Check your email

No record here.

Check the record.
Not the agent's word.

One key per job.
It can't do more.

Bind a root.
A name alone proves nothing.

New key.
Same agent.

Copy the name.
Not the record.

Put the check
at your gate.

Every refusal.
Named and signed.

Five calls.
One answer each.