One JSON file per agent. Identity, principal, scope, spend limits, escalation. The spec your audit tools, banks, and SaaS vendors can all read — and refuse to serve when it's missing.
Every field has one job: answer a question a bank, audit tool, or SaaS vendor will ask the moment your agent shows up at their door. Anything more is bloat. Anything less and the next person at the door has to guess.
send_payment, open_subscription, read_data, etc. Whitelist, not blacklist.escalation."0.1" for now. Tools that read KYA files check this first.This is OutreachBot — the cold-email agent from the Agent Ledger demo. Eight fields, signed by a principal, scoped to one job. Copy it, change the values, ship it.
{
"version": "0.1",
"agent_id": "agent.outreach.001",
"principal": {
"legal_name": "Acme Build Co LLC",
"jurisdiction": "US-DE",
"ein": "88-1234567"
},
"scope": ["send_payment", "open_subscription", "read_data"],
"vendor_allowlist": [
"apollo.io",
"smartlead.ai",
"clearout.io",
"instantly.ai"
],
"limits": {
"per_transaction_usd": 100,
"per_day_usd": 200,
"per_month_usd": 2500
},
"escalation": {
"webhook": "https://acme.co/agent-alerts",
"email": "ops@acme.co"
},
"attestation": {
"signed_by": "vv@acme.co",
"signed_at": "2026-04-22T08:00:00Z",
"signature": "sha256:9c2f...e114"
}
}
Same shape, very different scopes. A research agent shouldn't be able to do what an outreach agent does, and neither should be able to do what a deploy agent does.
It's a JSON file. There's nothing to install, no SDK, no platform. Pick the path that matches what you're building.
.kya.json in the same folder as each agent. Read it on agent startup. Refuse vendors and limits not in the spec. Done in an afternoon.X-Agent-KYA), require the file. Reject if scope or vendor_allowlist excludes you. Free upgrade to your fraud posture.The first KYA framework — MetaComp's StableX, shipped April 21 — is a paid commercial product for regulated finance. Useful. Closed. Finance-only.
That's fine for the regulated layer. It's not fine for the long tail: solo founders running 3 agents on Meow, indie SaaS adding agent endpoints, the small Brex customer who just gave a ResearchBot a corporate card. None of them will adopt a closed standard owned by a vendor they don't use.
Standards work when they're boring, free, and adopted before anyone's asking permission. HTTP, OAuth, OpenTelemetry — none of them won by being products. They won by being the obvious shape that everyone could converge on without a contract.
This spec is in the public domain. Copy it, fork it, extend it, ignore it. The goal is for ".kya.json" to mean the same thing in 12 months whether you ship in finance, healthcare, e-commerce, or your own kitchen-table SaaS. If something better gets proposed, this gets retired. The point is the convention, not the artifact.
attestation block. Signature is over the canonical-form JSON of the rest of the file. Verify with the principal's published public key. If the principal won't publish a key, the KYA is unverifiable — which is the right outcome.[KYA] proposal — version 0.2 will roll up community amendments. Backwards compatibility is a hard requirement until v1."jurisdiction": "US-HIPAA" and add a phi_access scope. If you're working in healthcare AI and want to co-author it, hit the email above.