bR2bR · ID Registry

Identity that survives the AI era.

bR2bR is the contractual handshake between humans, AI agents, robots, and devices. Every actor on the network gets a durable, queryable identity — so trust, billing, and audit don't collapse the moment a non-human joins the transaction.

Claim your bRRAInUserID Visit id.brrain.io
Anatomy

Two durable IDs. One network.

Every bRRAIn install and every device that registers against one gets an address in the network. Read left-to-right, they narrow from organization down to the specific actor.

4-part install ID

Identifies a bRRAIn instance and the organization that operates it.

org site instance version
acme-ny-prod-v3

Portable across migrations, stable across upgrades, scoped to the operating org.

5-part device / user ID

Identifies an actor (human, agent, robot, or device) inside an install.

install class kind serial role
acme-ny-prod·ai·agent·a3f9·analyst

AAS-compatible device profiles. Humans, agents, robots, and devices share the same schema — billing and audit don't need a branching tree.

Why a registry

Four problems the old identity stack can't solve.

1

Agents aren't users

OAuth flows assume a human at the keyboard. Long-running agents need credentials that rotate on their own clock and bind to a physical or logical host.

2

Devices aren't accounts

A factory sensor, a drone, or an embedded microcontroller has no email address. It still needs to transact, sign, and be metered.

3

Billing needs provenance

"Who did this work?" is the question every invoice dispute answers. bR2bR makes that answer cryptographic, not reputational.

4

Audits need continuity

Agents change versions. Devices get swapped. Humans rotate roles. The registry keeps the history queryable even as the actor evolves.

Who can register

One schema. Every kind of actor.

HumansOperators, learners, partners, customers — a bRRAInUserID anchors every role.
AI AgentsLLM-backed assistants, autonomous workflows, long-running service accounts.
RobotsMobile, stationary, cobot. AAS-compatible device profiles map cleanly.
DevicesSensors, cameras, microcontrollers, appliances. Zero-trust on first contact.
Session billing

Billing becomes session-native.

Every bR2bR handshake opens a session. The session meters itself and closes with a signed receipt. Invoicing is a matter of collecting receipts — not rebuilding a timeline.

  • Per-minute metering with cryptographic receipts
  • Multi-party sessions (human + agent + device) supported
  • Auto-reconciled against Stripe and Zoho Books
  • Dispute window: 3 days, credit-only, automatic

$0.005

per session minute

Volume tiers available for vendor networks and high-throughput device fleets.

Open standard

We published the spec. You can fork the reference implementation.

bR2bR is not a proprietary product dressed up as a standard. The specification is CC-BY 4.0; the reference implementation is Apache 2.0. A working group governs breaking changes with a 75% supermajority and a 90-day review window.

Specification

CC-BY 4.0. Versioned, with explicit deprecation policy.

Reference implementation

Apache 2.0. Runs the live Registry at id.brrain.io.

Conformance tests

Published with every spec release. Pass them to list on the registry.

Give your agents a name.

Registration is free. Your bRRAInUserID resolves across every bRRAIn property — app, learn, partners, exchange, and the Registry itself.

Claim your bRRAInUserID Read the spec