Open spec · published Apr 22, 2026

The open identity spec
for AI agents that move money.

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.

See an example
Why this exists, and why now. MetaComp launched StableX KYA for regulated finance on April 21 — the first commercial Know-Your-Agent framework. Useful, closed, finance-only. This is the open-community version: a portable JSON spec anyone can adopt today, free, no signup, no contract. Drafted in 24 hours after the MetaComp launch because the standard shouldn't be one company's product.

Seven fields. That's the whole spec.

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.

agent_id
Who is this?
A stable, globally unique identifier. UUID v4 or a reverse-DNS string. Never reused.
principal
Who owns the consequences?
The legal entity (person or LLC) liable for what the agent does. EIN or government ID. The buck stops here.
scope
What can it do?
A list of allowed action verbs: send_payment, open_subscription, read_data, etc. Whitelist, not blacklist.
vendor_allowlist
Where can it spend?
Domains the agent is allowed to transact with. Empty array means "anywhere" — explicit, not implicit.
limits
How much, how fast?
Per-transaction, per-day, and per-month dollar caps. Crossing any one triggers escalation.
escalation
Who answers when something's off?
Webhook URL or email for any flagged action. The human-in-the-loop endpoint, named explicitly.
attestation
Who signed off on this?
Signature from the principal's keypair plus an ISO timestamp. Lets a verifier prove the spec wasn't tampered with.
version
Which spec is this?
Always "0.1" for now. Tools that read KYA files check this first.

Here's what a filled KYA file looks like.

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.

// outreachbot.kya.json
{
  "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"
  }
}

What the spec looks like across roles.

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.

ResearchBot
Market research · web data agent
scope: read_data only
vendors: perplexity.ai, apify.com, exa.ai, firecrawl.dev
limits: $20 / txn, $100 / day, $500 / mo
Copy ResearchBot spec →
OutreachBot
Cold email · prospecting agent
scope: send_payment, open_subscription, read_data
vendors: apollo.io, smartlead.ai, clearout.io, instantly.ai
limits: $100 / txn, $200 / day, $2500 / mo
Copy OutreachBot spec →
DevBot
Code generation · deploy agent
scope: send_payment, open_subscription, deploy_code
vendors: vercel.com, supabase.com, openai.com, anthropic.com, github.com
limits: $50 / txn, $150 / day, $1500 / mo
Copy DevBot spec →

Three ways to use the spec today.

It's a JSON file. There's nothing to install, no SDK, no platform. Pick the path that matches what you're building.

01 · Solo builder
One file per agent
Drop a .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.
02 · SaaS vendor
Demand a KYA at API auth
If a request comes from an agent (header: X-Agent-KYA), require the file. Reject if scope or vendor_allowlist excludes you. Free upgrade to your fraud posture.
03 · Audit tool
Cross-check transactions
Agent Ledger already does this — paste a CSV plus a KYA, get a list of transactions that violated the spec. Open the same pattern up in your tool.
04 · Bank or fintech
Make agent accounts unprovisionable without one
Meow opens accounts for agents today. Block the open call without a valid KYA attached. Pushes the standard upstream where it belongs.

Why this isn't a product.

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.

Short answers, no hedging.

Why not just use OAuth scopes or API keys?
OAuth scopes describe what an authenticated user can do. KYA describes who an agent is — a different question that becomes urgent the moment the actor isn't a human. An API key with no KYA still leaves the question of liability and limits unanswered. They're complementary, not overlapping.
What stops someone from forging a KYA file?
The 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.
Is this trying to compete with MetaComp?
No. MetaComp's StableX is a paid framework for regulated financial services with workflow tooling around it. This is a one-page JSON convention for everyone else. Two different markets, both can exist.
Where do I propose a change?
Open an issue on the daily-build-portfolio GitHub repo with the title [KYA] proposal — version 0.2 will roll up community amendments. Backwards compatibility is a hard requirement until v1.
Is healthcare next?
Probably. HIPAA has no agent category and the same gap exists. A KYA-Healthcare draft is on the surprise stack — propose "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.