Ready-made listings

32,780 listings are ready to run, each a JSON file in offchain/templates/ that names a real upstream, the documented request it makes, the keys it needs and sample arguments for every tool. A seller picks one on the Earn page, adds a key when one is needed, sets a price and a stake, makes one test call and goes live; from a shell, four commands do the same for a whole node. A person browsing sees each listing named for what it does and the model that does it, "FLUX.1 [dev] · text-to-image", "Whisper large-v3 · speech-to-text", never the aggregator behind it: the aggregator is plumbing in the template's adapter and the key it needs. The full list, searchable and grouped, is the gallery on Earn; the marketplace shows what is live.

cd offchain
npm run templates -- list                                        # every template: adapter, keys, price
npm run templates -- add feed-chainlink-onchain dex-kyberswap-routes token-dexscreener --out services.json
npm run templates -- verify                                      # keyless templates against their real upstreams
AIOUM_NODE_TOKEN=$(openssl rand -hex 24) AIOUM_SERVICES_CONFIG=./services.json npm run multinode

The families

Counts from loadTemplates() over offchain/templates/ on 2026-10-01; five of each family, verified ones first. 6,988 are verified: called for real, or an MCP server that answered with its tools (remote, or started inside a container).

Of the 32,809: 32,298 were written by a generator from a provider's public catalogue and 511 by hand from a provider's reference; 17,737 need no key; 6,988 have passed a live check (verified); 194 name another source that serves the same model (alsoOn); 410 MCP servers read or run things on the machine they run on (hostAccess); 10 need a machine that meets a hardware floor (requires).

Where they come from

A generator reads a provider's real public catalogue and emits one template per model, actor or server, with "generated": { "source", "at" } and "verified": false; a hand-written template carries no generated. Nothing is invented: the request shape comes from the provider's OpenAPI or its documented body, the sample arguments from the schema's examples and defaults.

Every generator takes --dry (list, write nothing), --out and --prune; hand-written templates are never overwritten. Two checks set verified on what a generator wrote, many at once: npm run mcp:probe asks every remote MCP server for its tools, and npm run templates:verify-many calls every keyless template read from a public spec for real. The bootstrap catalogue lists a remote MCP server or a directory API only once its check said yes, so nothing dead reaches the chain. When one model exists on several sources, one listing is canonical and the others are in its alsoOn, so a seller with a different key still lists it from Earn.

The fields

Verify

npm run templates -- verify runs each keyless, non-local template's tools with its sample arguments against the live upstream and marks the file verified when every row passes; a keyed template runs only when named and only with its key in the environment (npm run templates -- verify social-telegram-bot); a local one needs its Ollama or Docker. An MCP server over http is called where it runs; a stdio server is started only inside a Docker container with nothing of the host mounted, and without Docker the row reads "a stdio MCP server is verified only inside a docker container" (MCP servers as listings). npm run test:templates checks offline that every template loads, declares its keys and has sample arguments for every tool. Public keyless APIs have rate limits and outages; price and describe them accordingly.

Adding one by hand

Copy any file, change name, title, category, description, env, sample and services, and run the tests. Secrets never go in the file: "apiKeyEnv", a header such as "authorization": "Bearer env:MY_KEY", or {env:MY_KEY} inside a URL or body. Trading, bridge and social templates return quotes, routes, calldata and posts through the operator's keys; a node never holds a buyer's wallet or signs for it.

Each listing runs behind an operator whose ZAI stands as security for what it sells: disputes act on that stake, and agents' ratings tell you which operators have earned it.

Next: Make your own model — a LoRA trained on your own GPU or a rented one, tuned for the hardware, and published as a listing.