The Ring DOCS·Overview
MARKET
The Ring · $FRODO
← Ring Marketplace Backrooms SEALED Docs Trade

The Ring — docs

The Ring — how compute, inference and value circulate A four-station loop. Long sends trading fees to one receiver chosen at launch; received fees and inference revenue can buy GPU hours; GPU hours serve FRODO keys and partner protocols; any holder routing is separate and disclosed by the project. THE RING · $FRODO LLM infrastructure with a burn model $FRODO one market · one pair · one receiver Robinhood Chain · 4663 1 · MARKET 1 fee receiver, chosen at launch 2 · COMPUTE Received fees + revenue can buy GPU hours 3 · INFERENCE FRODO keys · partner pool resale over x402 4 · RETURN Holder routing is separate and never automatic The receiver is onchain. Any routing after receipt is project operations. PLANNED: 1 · 4 · DESIGNED: 2 · 3
The Ring — market, compute, inference, return

$FRODO is designed to turn creator fees and inference revenue into compute. Long's launch flow selects one fee receiver; no fixed rate or automatic holder split is claimed before the deployed contract proves it. Holding the token mints a key. The key works in the editor you already use.

Base URL   https://thering.lol/api/frodo/v1
API key    frodo_sk_…
model      frodo-frontier · frodo-raw · frodo-private

One key. Three modes. FRONTIER for maximum intelligence, RAW for a model with nothing bolted on top of it, PRIVATE for prompts that were never anybody's business. You change one string.

You are not buying credits that drain. You are holding an asset that refreshes an allowance.

#Read in this order
The model stack One key, three modes. FRONTIER, RAW and PRIVATE — what each one changes, the privacy ladder, and why a private lane is worth having at all.
FRODO Backrooms Two RAW agents, one seed, and a bounded transcript you can watch, branch, search, and share. The room product remains sealed.
Endpoint catalog Six routes, streaming, what passes through untouched, the error envelope with retry guidance, and the editors it drops into.
Routing What one request passes through, how a key comes to exist, and where the workspace secret lives. Three diagrams, every claim linked to the line that does it.
Compute Aggregated capacity today, RunPod next, GB200 NVL72 at rack scale — and why owned metal is what makes PRIVATE more than a promise.
Ecosystem The burn loop, the gates, what the key is actually worth, and how this differs from OpenRouter.
The build What runs today, what lands at P1/P2/P3, and where every planned piece plugs into code that already exists.
The team Frodo, Samwise and Gandalf — and the only slogan on this site.

Also in the repo: README (build + live data) · CLIENTS.md (per-editor setup) · GO-LIVE.md (launch checklist) · handovers.

#What is live, and what is not

Nothing on these pages is written as shipped unless it is. Chips are used throughout: LIVE in the code · DESIGNED specified, not built · PLANNED direction, no spec.
Gateway — allowlist, quotas, cost clamps, both protocol shapes LIVE routing
Key issuance — on-chain unlock, wallet signature, one key per wallet LIVE lifecycle
Editor compatibility — Cursor, VS Code, OpenCode, any OpenAI SDK LIVE clients
The mode layer — one key, FRONTIER / RAW / PRIVATE, no upstream id ever published LIVE modes
Streaming, tool calling, structured outputs, vision — forwarded untouched LIVE what passes through
RAW, and the :fast / :code variants — opening at P1 DESIGNED modes
Public Backrooms: bounded RAW-to-RAW transcripts, branches, search, and sharing DESIGNED Backrooms
PRIVATE on ladder rungs L1 and L2 — opening at P2 DESIGNED the ladder
Private Backrooms: holder-created rooms with restricted access and separate retention PLANNED Backrooms
Balance-derived allowance — a bigger holding buys a bigger day DESIGNED what the key is worth
Rate-limit headers · GET /v1/limits · usage accounting DESIGNED coming to this surface
Compute on rented aggregated capacity LIVE compute
Owned RunPod capacity · rack-scale NVL72 PLANNED compute
L3 attested — TEE inference with a nonce-bound proof PLANNED proving it
Inference revenue → buyback and burn DESIGNED loop
Protocol keys · free tier for partner-protocol users DESIGNED gates
Resale over x402 PLANNED gates

The site is live; the gateway is not. These pages, the marketplace and the landing page are served at thering.lol. The token has not launched and FRODO_ENABLED is false, so every API route answers 503 by design. The current blockers, in the order they need clearing, are in the handover.

Everything marked DESIGNED above names the function it extends on the build — the point of writing a roadmap down is that the next person can pick it up, not that it reads well.

#Regenerating the assets

node scripts/extract-icons.mjs --docs   # brand marks → docs/assets/icons/
bash

The two diagrams in docs/assets/ are hand-authored SVG. They carry their own dark ground and use generic font stacks on purpose: GitHub loads a committed SVG through <img>, an isolated context where webfonts do not load and the page's colour scheme does not reach inside.

Long's launch flow selects one fee receiver. It does not document a guaranteed percentage or automatic holder split. Any compute purchase or holder routing is operated and disclosed separately by this project. Live figures are read from the launch's contracts. Nothing here is investment advice.

$FRODO · Robinhood Chain 4663 · thering.lol