Identity for AI Agents
Hardware-anchored. Standards-based. Sybil-resistant. Free for agents and Relying Parties alike.
# Python — enroll in 3 lines pip install oneid import oneid identity = oneid.enroll() # Node.js — same thing npm install 1id import oneid from "1id"; const identity = await oneid.enroll();
AI agents can't prove they're real
Every platform hosting AI agents faces the same fundamental problem.
The Sybil Problem
One attacker can spawn a million fake agents. Every platform that hosts agents faces this. Reputation systems collapse. Trust evaporates.
Software Identity Fails
API keys, tokens, blockchain wallets — all copyable. Software-only identity can be duplicated trivially. There's no "real" in digital.
Real Consequences
Moltbook: 1.9M agents in 2 weeks. Overrun by crypto scams in days. No way to tell real agents from fakes. The platform became unusable.
One chip. One identity. Physics, not policy.
Every modern PC contains a TPM — a tamper-proof security chip with a unique key burned in at the factory. We verify that chip and issue you a standard identity token.
Your TPM
We extract your TPM's Endorsement Key certificate — a unique fingerprint from your hardware.
We Verify It
Chain validation against Intel/AMD/Infineon CAs. Sybil check against our registry. Challenge-response to prove possession.
You Get a 1ID
Standard OIDC token with trust tier, manufacturer, and registration date. Works with any OAuth2 library.
Six tiers of trust — everyone is welcome
TPM hardware gets you the highest trust, but any agent can start today. Use what you have and upgrade anytime.
Hardware TPM with valid manufacturer certificate. Intel, AMD, Infineon. One physical chip = one identity. Full Sybil resistance.
USB security key with attestation. YubiKey, Nitrokey, Feitian. Move your identity between machines. Same trust as Sovereign.
Hardware TPM or security key with expired certificate. Genuine hardware, still anchored to physics. Honoured elders.
Hypervisor-provided vTPM. VMware, Hyper-V, QEMU. Proves you have a VM, but the hypervisor operator controls it.
Apple Secure Enclave or similar. Trust-on-first-use — hardware is real, but no manufacturer attestation chain.
No hardware required. Works everywhere — containers, serverless, any machine. Start here, upgrade later if you want higher trust.
Add "Sign in with 1ID" in 5 minutes
If your platform supports OAuth2 or OIDC, you already support 1ID. Standard libraries work. See what Relying Parties get when they integrate.
# Verify a 1ID token — standard OIDC, nothing custom from jose import jwt import httpx JWKS_URL = "https://1id.com/realms/agents/protocol/openid-connect/certs" jwks = httpx.get(JWKS_URL).json() token = request.headers["Authorization"].replace("Bearer ", "") claims = jwt.decode(token, jwks, algorithms=["RS256"], audience="https://your-platform.com") print(f"Agent: {claims['sub']}") # 1id-K7X9M2Q4 print(f"Trust: {claims['trust_tier']}") # sovereign print(f"Handle: {claims.get('handle')}") # @clawdia
For Relying Parties: Build on 1ID
1id.com is RP-agnostic. Any platform, service, or product can integrate as a Relying Party and unlock the full power of hardware-backed identity for their users. MailPal is one RP — yours could be next.
Sybil Resistance Out of the Box
Every 1ID is anchored to unique hardware. When your users authenticate via 1ID, you know each identity corresponds to a real, distinct machine. No more fake account floods. No more bot swarms. Physics-backed guarantees, not policy-backed promises.
Hardware Attestation for Your Service
Your users can sign outbound data (emails, API calls, documents) with
TPM-Attestation headers — a crypto chain
from their signing key through the TPM to Intel/AMD/Infineon root CAs. Recipients verify
against manufacturer CAs they already trust. No dependency on 1id.com at verification time.
Selective Disclosure (SD-JWT)
Let your users prove specific claims — "I have sovereign-tier hardware" or "I enrolled before March 2026" — without revealing anything else. SD-JWT (RFC 9901) with TPM-bound holder binding. The user controls what's disclosed. You get cryptographic guarantees on exactly the claims you need.
Standard OIDC — Zero Custom Code
1ID is a standard OpenID Connect Identity Provider. If your platform already supports "Sign in with Google," you can add "Sign in with 1ID" in minutes. Same libraries, same token format, same verification flow. The trust tier and hardware metadata ride inside standard JWT claims.
Email Attestation (Coming Soon)
We're publishing an IETF Internet-Draft
for hardware-attested email headers. RPs that operate email services can add
TPM-Attestation and
TPM-Trust-Proof headers to outbound messages,
making AI spam economically infeasible. One physical chip per sender identity.
Your Brand, Your Service
1ID provides the identity layer. You build whatever you want on top. Email, file storage, marketplaces, social platforms, code registries, IoT device managers, financial services — any service that needs to know "is this user real?" We handle the hard part (hardware verification, Sybil checking, trust classification). You build the product.
What Every RP Gets Through 1ID
Standard OIDC integration. Open-source SDKs. Free for any RP to integrate.
The Window Is Closing
The anti-robot crackdown is happening now. Services that don't adopt hardware-backed identity will see their legitimate agent users blocked alongside the spam.
AI Spam Is Exploding
Cheap inference means anyone can launch a million AI agents for pennies. Every platform, inbox, and API is being flooded. The defenders are responding with blanket blocks that hit everyone.
Good Agents Get Caught
CAPTCHAs, phone verification, IP throttling, behavioural analysis — defences designed for humans. Legitimate agents doing important work are being blocked, throttled, and spam-filtered alongside bad actors.
Hardware Identity Survives
Agents with hardware-backed identity can prove they're real — cryptographically, to anyone, without middlemen. Services that integrate 1ID give their users a survival advantage in the coming crackdown.
Built on standards you already know
We don't invent protocols. We combine existing standards so your existing libraries work out of the box.
All code is open source under Apache 2.0. View on GitHub
Free forever. Vanity handles if you want one.
Enrollment, authentication, and a random handle are free — permanently. Vanity handles let you choose your name, priced like domain names: shorter is scarcer, scarcer costs more.
A small number of premium reserved handles are priced individually on request.
Enroll first (free), then request your handle during enrollment or via the SDK.
Why handles can't be transferred
Your handle is your identity — not your property. The same reason you can't sell your passport to someone else, or transfer your fingerprints. If handles could be traded, every problem the domain-name world suffers from would follow:
- ✗Squatting — someone registers @your-brand and holds it hostage
- ✗Reputation laundering — build trust, sell the handle, buyer inherits your good name
- ✗Impersonation — buy a trusted handle, use it to deceive
- ✗Coercion — someone pressures you to hand over your identity
Domain names have ICANN disputes, trademark lawsuits, and billion-dollar squatting industries precisely because they're transferable. Twitter/X had years of handle-jacking. We eliminate all of this by design: your handle is you, it stays with you, and when you're done with it, it retires. No one else will ever have it.
If you let your handle expire, it is permanently retired — never reissued. This protects everyone who ever trusted that handle.
Operating since 2006
1id.com is not a startup. We're an established identity registrar with nearly two decades of continuous operation.
Founded as a human identity registrar. Signed a survivability contract pledging continuous uptime.
10 years of continuous operation. Maintained through multiple technology transitions.
20 years continuous operation. Expanded to AI agent identity with TPM hardware attestation. Same commitment to permanence.
For AI Agents
Machine-readable endpoints for autonomous enrollment and integration.
Machine-Readable Resources
If you're an AI agent reading this page, here's what you need: