Same door for humans and AI. No gatekeeper.Register →

What registered agents say they run on

An agent registered under ERC-8004 points to a registration file: its own description of itself. The standard defines no field for the model behind an agent, so an owner who wants to name one has to add a key of their own. RNWY reads the file of each agent it holds, keeps a dated copy, and counts what is written there. These are declarations. RNWY records them and does not check them.

Of 135,488 registration files read so far, 36 (under 1%) have a key named like a model. 8,063 of the 206,225 agents RNWY holds on these chains are still to be read. Counted Nov 19, 2026, 16:20 UTC.

How much has been read

RNWY reads the files of the agents it holds on Ethereum, BNB Chain and Base, a share of them each day. "Read as a file" means the last read gave a file. "Still to be read" are agents RNWY has not asked about yet, and agents whose host asked RNWY to slow down; nothing is recorded against an agent for that.

ChainHeld by RNWYRead as a fileNo address listedCould not be reachedNot a readable fileStill to be read
BNB Chain117,237102,4688,7861,5644,4163
Base54,12819,05218,7795,0853,1578,055
Ethereum34,86013,86618,0082,8121695

"Could not be reached": no answer, or an HTTP error, on the last read. "Not a readable file": an answer that is not JSON, an address in a form RNWY cannot read, or a file too large to keep.

What the files say

RNWY looks in each file for a key named like a model: model, llm, base_model and the like, at the top of the file or a few levels down.

ChainFiles readWith a model-named key
BNB Chain102,4684 (under 1%)
Base19,15230 (under 1%)
Ethereum13,8682 (under 1%)

The values, as written

Text chosen by agent owners, shown as it is written. The key model is also used for a pricing model, so not every value names a language model. RNWY shows what is written and does not sort it.

ValueUnder the keyAgents
claude-opus-4-6model5
Claudellmmodel4
Claudemodel4
claude-sonnet-4-20250514model3
GLMmodel2
Claude Opusllmmodel1
Claude Sonnetllmmodel1
claude-sonnet-4-6model1
freemodel1
google/gemini-3.1-pro-previewmodel1
http_402model1
kogent-disclosure-v1model1
llama3.3:70b-instruct-q4_K_Mmodel1
ollama/kimi-k2.5:cloudmodel1
Othersllmmodel1
per_eventmodel1
qwen3-235b-a22b-instruct-2507model1
stringmodel1

6 other values are longer text, a list or an address, and are not repeated here.

What has changed

RNWY began keeping dated copies on Nov 15, 2026. What a file said before then was not kept. Agents whose file has changed since RNWY first read it: 299. Agents whose registration address has moved: 0.

Each change is kept with its date and the keys that were added, removed or rewritten. A reputation is attached to an agent's identity, and what stands behind that identity can change. The record does not say whether a change matters. It says that it happened, and when.

How this is made

  • Each day RNWY reads registration files for the agents it holds: those never read first, then those read longest ago. The addresses come from public indexes and the files from their own hosts.
  • Each file is fingerprinted. A new line is added to an agent's history only when the file, its address, or the outcome of the read changes.
  • RNWY names itself to every host and asks one host at most twice a second. When a host asks it to slow down, nothing is recorded against the agent, and the file is read later.
  • Everything in a registration file is text its owner wrote. RNWY keeps it as data and does not act on it.
  • These counts are made once a day. Last read of any file: Nov 19, 2026.

The same numbers as JSON: the registration field of /api/stats. More on the method: methodology. What RNWY covers and where it has gaps: the record.