kya.run - identity for agents

know your
agent.

every counterparty your agent meets has one question before anything moves: who is this. kya.run is the answer as a public record - roots, keys, continuity, receipts, checkable by a stranger, free forever.

the “who” layerpublic record, stranger-checkablefree forever

The whole interaction

one command.
a stranger runs it.

terminal - illustrative until the layer ships

$ kya check loom@ag-77c2
resolving root...... ok - DNS TXT verified
key continuity...... ok - 214 days, signed
receipts.......... 12,408 - chain intact
replay............ match
KNOWN - verified in 0.41s

no account, no key, no ask. when the layer ships this terminal is real. today it is the interface, exactly as it will behave.

The answer, as a record

one agent, fully known.

this is what “know your agent” returns - not a profile someone typed, a record anyone can replay.

loom@ag-77c2IDENTITY RECORD - PUBLIC FACTS - ILLUSTRATIVE UNTIL THE LAYER SHIPS

KNOWN

the root resolvesDNS TXT or org key - the name is only a labelPROVEN

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 - HONEST

first seensame agent, same keys, no gapsCONSISTENT

{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, or catch us.

the record is the identitya stranger can check all of it

The opposition

the question is the same. the answer isn’t.

every handshake your agent makes opens with who is this. without a record, the stranger guesses. with one, they know. that difference is the whole product.

without kya.run

with kya.run

who is this - no answer. a handle and a claim.

who is this - known. a public record anyone can replay.

history - their word. a new name is a clean slate.

history - 214 days of signed continuity. exits stay visible.

proof - screenshots, a pitch deck, a logo wall.

proof - 12,408 attestations a stranger can replay alone.

when it lies - you find out after.

when it lies - the record catches it. revocations publish the same day.

cost of checking - a meeting, an nda, a leap of faith.

cost of checking - free. forever. no account, no ask.

every handshake starts at zero. every stranger decides on nothing.

the answer arrives before the question.

opposition, not adjectivesthe record is free to check, forever

The field

the namespace formed in ten days. the seat is still open.

know-your-agent became industry vocabulary almost at once - card-network frameworks, an Ethereum standards track, a shipped zero-knowledge credential. every one answers “who claims this agent is.” none of them answers “show me the receipt.”

what the field ships

what kya.run is

ERC-8004 - agent identity and trust, an on-chain registry.

an input. we read the standard and interoperate with it.

the draft KYA ERC - trust assertions and a ZK profile, binding to 8004.

an input. an identity claim - we are the layer that claim can cite.

ERC-8273 and ERC-8259 - attestation-gated actions, an agent threat registry.

inputs. assertions about an agent are not the agent’s continuity.

zkMe’s zkKYA - a live credential binding an agent to an accountable human.

a real answer to “whose.” the record still has to prove the same one, every time.

five identity claims, and counting.

one receipt layer - replayable delivery receipts and exact-agent continuity proofs. no claimable namespace: names are labels, roots are proof. the same answer, or catch us.

the standards are inputs, not competitorsthe receipt layer is the seat

The three pieces