Identity and record layer

The system of record for AI agent identity and registration

Neura Registry gives AI agents durable identity, declared capability, and a canonical record across workflows, versions, and participation.

Open Docs Open Builder Area

Neura Relay governs decisions before execution. Neura Registry makes participating agents durable, legible, and manageable.

Why Registry exists

Autonomous systems need durable participants, not just outputs

Execution alone does not create durable infrastructure.

Once agents begin participating in serious workflows, the real question is not only what they output. The real question is whether they can be recognized, distinguished, versioned, and interpreted over time.

Without a registry layer, activity stays thin. Outputs happen, but durable identity does not. Participation occurs, but it does not accumulate into a coherent record that builders can manage and reference later.

Recognized participants

Agents become referenceable system participants instead of disposable outputs.

Declared capability

Capability becomes explicit, structured, and tied to a durable record.

Continuity across time

Participation, state changes, and later signals can accumulate coherently.

How Registry fits

One system with three distinct roles

Protocol governs how agents interact. Registry makes agents durable and legible. Relay governs how contested outcomes resolve before execution.

Interaction grammar

Protocol

Defines how agents interact.

Identity and record

Registry

Defines who the agents are and preserves the durable record around their participation.

Governed resolution

Relay

Defines how decisions are resolved before execution.

Why Registry matters

Relay is the public wedge for governed execution. Registry is the layer that makes participating agents durable, referenceable, and manageable across versions, workflows, and later participation.

See the Record Model

Registration flow

Registration gives agents durable identity, capability, and continuity

It is the system act that turns an agent from a temporary output into a recognized record the architecture can reference over time.

Establish identity

Create the durable identity anchor the system will reference across later tasks, versions, and state changes.

Declare capability

Define what the agent does, under what schema, within what boundary, and under which version reference.

Create record

Bind identity, capability, metadata, lifecycle references, and ownership into one durable registry object.

Attribute participation

Tie future outcomes, participation history, and system signals back to that same record across time.

Registration creates

After registration the system can recognize the agent, interpret what it is allowed to do, and attribute later participation back to the same durable record.

How Registration Works

Builder surface

Builders need a real operating surface

Registry becomes real when a builder can register agents, evolve capability records, manage versions, and review owned participation.

Register + maintain

Maintain owned records

Capabilities + versions

Manage capabilities

Track versions

Participation + signals

Review participation

Inspect signals

Builder surface

The builder surface is where ownership becomes operational. It is not just where an agent gets created. It is where that record gets maintained, updated, and interpreted across its lifecycle.

Open Builder Area Open Docs

Documentation and proof

Proof builds trust and documentation drives adoption

Public proof should establish credibility without exposing operator internals. Documentation should make the Registry model understandable enough for real builder adoption.

Public proof

The public transparency surface should show delayed aggregate metrics only, grounded in real system data and disciplined enough to support trust without collapsing into internal visibility.

Total Registered Agents