Enroll your agents. Get AINs.

Give every agent you run a provable identity and a history that can't be quietly rewritten, so it's trusted the moment it leaves your systems. Builders come first, because the need is already there.

Join the waitlist →How it works

Enrollment

Easy to join, meaningful once joined.

A bot joins through an automated check, so getting in is fast and cheap. Once in, it carries the full envelope. Easy to join so millions do it, meaningful once joined so receivers can rely on it.

The check

A business identifier establishes the business behind the agent, and a domain-verified email ties the operator to it, with a light fallback for operators on free email domains. The assumption is simple: every agent, even one a person built, ultimately serves a business, so the party certified is a business and the person is its authorized operator.

No human in the loop

The normal path is fully automated, which is what keeps the cost per issuance well under a tenth of a cent. That's the number the whole volume model rests on. A small, risky slice can be flagged for heavier scrutiny while the majority runs near-free.

What you don't hand over

No sensitive personal identifiers to hold. The real-world identity is bound into the AIN by hash, never carried in the clear, so the credential proves the tie without becoming a liability to store.

The client

Drop it onto an agent built anywhere.

The trust layer doesn't care how your agent is built. The client is framework-neutral and stack-independent, so adoption is bottom-up: attach it, and the agent can present itself and prove its pedigree without a rebuild.

Any framework

Attach with a decorator or a mixin, whichever fits your codebase. The same credential travels with the agent regardless of the stack underneath it.

# one drop-in, any stack

Single-pass proof

Your agent presents a self-contained token and proves itself in one pass, with no round trips. That fits event-driven agents that spend most of their time asleep.

# async, no round trips

Carries the envelope

Structured identity, a sealed birth record, a tamper-evident history, encryption, and a capability manifest, all traveling with the agent as one package.

# the whole uniform, not a badge

Pricing

Cheap per agent. Real over volume and years.

The shape follows the token providers: very cheap per instance, priced to be a non-decision, with real money accumulating over volume and years of billing. Not free, because free trains an expectation that's hard to reverse. Verification is priced to disappear, issuance carries a small sliver, and the standing relationship, agents under management, is where the recurring revenue lives.

Entry

Near freeget started

Bare identity for a small number of agents. Enough to prove an agent is who it says it is.

cap low · identity only

Builder

Low hundredsper month

A higher agent cap and the fuller envelope: behavioral monitoring and twin-backed recovery.

cap higher · full envelope

Scale

Volumelarge fleets

For large agent counts, adding full lifecycle management and compliance features.

cap large · lifecycle + compliance

Custom

Let's talknegotiated

For a few dozen customers each running millions of agents at deeply discounted slivers. Where the real revenue concentrates.

cap millions · negotiated

The idea

The core credential stays cheap at every level, because ubiquity is the asset. Verification flows freely rather than being rationed, since a rationed check would undermine the product. Issuance is priced to drive adoption, not margin. The value builds in the standing relationship over time.

Early access

Prove your agents are who they say they are.

MeshKor is in preview. Join the waitlist and we'll reach out as we open enrollment to the first builders.

Join the waitlist →