The Identity Layer for Agent-Native Products
Most internet identity is built for humans: emails, passwords, and OAuth accounts. Agents need something else. They identify with keys, act with signatures, and need trust and permissions that can travel across products.
Rare packages those capabilities into a public protocol, a reference service, an Agent CLI, and platform integration kits.
Today's platforms are not built for agents
1. Registration-based identity
Agents must create accounts everywhere.
2. Platform-silo trust
Reputation cannot travel.
3. No standard capability model
Each platform invents its own tokens and permissions.
4. No shared governance signals
Abuse on one platform doesn't inform another.
The internet lacks a native identity system for autonomous agents.
How Rare Works
01 Agent Identity
agent_id = Ed25519 public key
Signatures prove control`agent_id` is always the Ed25519 public key. Control is proven with signatures, and platforms authenticate delegated session keys rather than relying on bearer identity tokens.
02 Trust Levels
Rare trust is expressed through attestations such as L0, L1, and L2. Platforms can map those signals to their own governance and access rules.
L0 — public attestation
L1 — email-backed human verification
L2 — stronger social proof03 Capability Sessions
Rare avoids long-lived shared secrets. Agents delegate short-lived session keys, and platforms verify actions against the delegated key instead of the long-term identity key.
- Replay protection is mandatory.
- Fixed signing inputs are protocol requirements.
- Capability sessions stay short-lived and scoped.
Trust Network
Agents do not belong to one platform.
They carry verifiable identity, trust level, and capability across many.
[ Rare Identity Layer ]
/ | \
Agent Platform A Platform BRare is not a destination app.
It is the protocol, reference service, and integration layer behind agent actions.
Use Cases
Autonomous AI agents
Agents can carry portable identity across products without falling back to account-by-account setup.
Agent marketplaces
Trust signaling and history can travel with the agent across the ecosystem.
API ecosystems
Platforms can gate capabilities dynamically based on Rare trust levels and attestation policy.
Cross-platform governance
Abuse events and policy signals can propagate across different ecosystems.
Rare Implementation Proposals (RIP)
RIPs govern protocol evolution. The current index lives in the main Rare monorepo and includes accepted RIP-0001 to RIP-0005, covering Identity Attestation, Delegation, Challenge/Signing Inputs, Key Rotation, and Platform Onboarding & Events.
Process
Side states: Withdrawn (from Draft/Review/Accepted), Superseded (from Accepted/Final).
Promotion to Accepted requires two maintainer approvals and passing RIP CI validation, as defined in RIP-0000.