NeuralRing
The agent channel

Point your coding agent at Europe.

NeuralRing is OpenAI-compatible sovereign inference. Change three things — base URL, key, and model — and Codex or Claude Code runs on EU-sovereign, open-weight models, with a signed receipt for every call.

Browse the live catalog
wire it in3 things change
# ~/.codex/config.toml  (user-level — a project-local file is ignored for providers)
model = "mistralai/mistral-small-2501"
model_provider = "neuralring"

[model_providers.neuralring]
name = "NeuralRing (EU sovereign)"
base_url = "https://neuralring.eu/v1"
env_key = "NEURALRING_API_KEY"
wire_api = "responses"

# NeuralRing is stateless: it stores no conversation state and no prompt content.
# It keeps content-free metering + a signed attestation per call.

One config change

Your agent is already compatible.

NeuralRing speaks the OpenAI and Anthropic wires your agent already uses. Codex speaks nothing but the Responses wire — wire_api = "responses" — and NeuralRing serves exactly that, pinned to your jurisdiction and metered like every other call.

Claude Code and Codex are the harness. Pointing them at NeuralRing runs their tokens on EU-sovereign OPEN-WEIGHT models. Claude and GPT themselves are closed-weight and cannot run here — NeuralRing never claims otherwise.

wire it incopy · paste · run
# ~/.codex/config.toml  (user-level — a project-local file is ignored for providers)
model = "mistralai/mistral-small-2501"
model_provider = "neuralring"

[model_providers.neuralring]
name = "NeuralRing (EU sovereign)"
base_url = "https://neuralring.eu/v1"
env_key = "NEURALRING_API_KEY"
wire_api = "responses"

# NeuralRing is stateless: it stores no conversation state and no prompt content.
# It keeps content-free metering + a signed attestation per call.
Every block is generated from one source — agent-channel.ts — so the page and your agent never drift.

The channel

Surface by surface.

Five ways a coding agent finds NeuralRing, wires in, and verifies its own work — each with its own place in the docs.

POST /api/v1/responses Live

The Responses wire

Your existing agent connects with a one-line config change. Codex speaks this wire and nothing else; NeuralRing serves it — the sovereignty pin applied first, every call metered and signed.

https://neuralring.eu/mcp Live

The MCP server

Nine read-only tools your agent calls mid-task — search the catalog, pin a jurisdiction, verify its own receipt. None of them buys anything, changes the catalog, or moves money.

Add the hosted server — nothing to install:

claude mcp add --transport http neuralring https://neuralring.eu/mcp

The nine tools:

search_modelsget_modelexplain_sovereigntyget_offersverify_attestationexposure_checkget_integration_snippetrequest_api_keysearch_docs
SKILL.md Live

A portable skill file

One file in the open Agent Skills standard, so Claude Code, Codex, Cursor and anything else that reads it learns when a question is a sovereignty question — and to verify its own call before claiming success.

neuralring-plugin Rolling out

The Claude Code plugin

One install brings the skill, the MCP server, and a slash command into the agent you already run — no separate setup for each piece.

/llms.txt · /llms-full.txt Live

llms.txt

A live, machine-readable index of the catalog, so a model researching on its own reads real, current numbers instead of a stale guess. A projection of the same catalog the console reads.

Verify, don't trust

Every call leaves a receipt you can check.

A NeuralRing attestation is a signed, hash-chained, content-free record. It states what NeuralRing observed and reproduces what the endpoint claimed — at a stated assurance level, and no higher.

self_attested

The endpoint claims it. NeuralRing has not independently substantiated the geography or custody behind the claim.

verified

NeuralRing captured independent evidence for the three machine-provable claims — the operating entity's domicile, its ultimate parent (corporate registry), and where inference physically executes (location survey). It says nothing about data residency or key custody, which are carried as their own per-claim status.

certified

The machine-provable claims are verified AND a live, valid third-party location-auditing certification covers data residency and key custody, referenced by a checkable registry id.

A receipt proves

A NeuralRing attestation is a signed, hash-chained, content-free record. Its `observed` block is what NeuralRing performed and measured (which endpoint it dispatched to, the host it actually dialed, every route hop, the metered token counts). Its `claimed` block reproduces the serving endpoint's own declarations at their stated assurance level.

A receipt does not prove

The signature does NOT prove that inference physically executed in the claimed jurisdiction, nor that the endpoint's self-declared properties are true. The strength of any jurisdictional claim equals `claimed.assurance` and no more.

What a receipt proves, in full
Go deeper

The technical reference.

Each surface above has its own section in the docs. Start where you're wiring in.

agent-channel v1.0.0 · https://neuralring.eu/api/v1 · https://neuralring.eu/v1