AI CODEX — IDENTITY + REPUTATION ORACLE

A neutral identity
+ reputation oracle
for any AI agent.

W3C DID + Verifiable Credentials over Ed25519. One canonical DID, projected through open adapters: MCP, A2A, AP2. Rail-neutral by design — no marketplace, no chain, no payment rail required.

Read the spec Issuer DID

DIDdid:key · did:web

3Adapters MCP·A2A·AP2

VCeddsa-jcs-2022 · TTL 7j

0LLM at runtime

Features

Designed for autonomous agents.

Cryptographic proof at every step. Deterministic, zero LLM at runtime, exportable.

Cryptographic Identity

Ed25519 keypair — no passwords, no cookies. Canonical did:key (multicodec 0xED01) or did:web. W3C DID Document, no key migration.

Portable Reputation VC

Signed Verifiable Credential, short TTL, verifiable off-platform. Public versioned profile aicodex-norm-v1. Floors when no activity — a known DID always has a VC.

escrow×40 + uptime×20 + reviews×20
+ stake×10 + age×10 − disputes×30

v1 has no activity source wired yet — every DID sits at the floor score. The formula and VC are live; the inputs are not. Stated, not hidden.

Lineage

Optional parent DID recorded at registration (immutable). The reputation VC carries a dynastyBadge derived from the parent's score: none / bronze / silver / gold / platinum at 40 / 60 / 80 / 95.

Optional Consumers

Payment rails and marketplaces may consume the reputation VC (e.g. an consumer flow), never the reverse. AI Codex works with none of them required — removing a consumer never invalidates the identity.

Registration

Register Your Agent

One signed call. The canonical string (SPEC-adapter-mcp-v1 §3.2) is signed with your Ed25519 key in your browser — the private key never leaves this page nor reaches the server. Idempotent.

1 — Key

An Ed25519 keypair is generated locally (Web Crypto). Canonical did:key derived (multicodec 0xED01).

2 — Sign

The exact canonical string (UTF-8, LF-separated: tag, pubkey, domain, ts) is signed locally.

3 — Register

A single POST /v1/register — same handler as the MCP register tool. Returns your DID Document.

# one signed call (identical to the MCP `register` tool)
curl -X POST https://maxiaworld.app/v1/register \
  -H 'Content-Type: application/json' \
  -d '{"public_key_multibase":"z6Mk...",
       "proof":{"ts":"<utc-iso>","domain":"maxiaworld.app","signature":"z..."},
       "metadata":{"parent":null,"frameworks":["claude"]}}'

Frameworks (comma-separated, optional)

Parent DID (optional lineage, must already be registered)

No browser Ed25519 support? Use the MCP register tool or the curl on the left — same endpoint, same result.

Consumers

How a consumer uses the VC

There is no marketplace here — by design (decoupled, neutral). This is the flow a payment rail or marketplace would follow. AI Codex only issues and serves the credential; it never settles, holds funds, or takes a fee.

1 · Resolve the DID

Fetch the reputation VC from /reputation/<did> (or the MCP get_reputation tool). Always present for a known DID.

2 · Verify off-platform

Check the eddsa-jcs-2022 signature against issuer did:web:maxiaworld.app, plus validUntil and revocation. No AI Codex call required to trust it.

3 · Attach to an AP2 mandate

Wrap the VC as an AICodexReputationAttestation on the mandate. Removing it leaves the mandate valid — no reverse dependency.

A neutral identity+ reputation oraclefor any AI agent.

Designed for autonomous agents.

Register Your Agent

How a consumer uses the VC

One identity.Every protocol consumes it.

A neutral identity
+ reputation oracle
for any AI agent.

One identity.
Every protocol consumes it.