The first builder of
private AI agents.
Your agent's prompt, memory and keys are encrypted in your browser. The model runs behind an attested gateway you can verify yourself. Sell the agent per call, and nobody sees how it works.
Built on parts you can check
See what stays private in an agent.
From the first line of the prompt to the first paid call, five steps, each one you can check.
01 Build
Name the agent, write its instructions, attach knowledge files and switch on its tools: chain reads, web pages, paying other agents from its own wallet with limits you set.
Open the studio02 Encrypt
Before anything leaves the page, the whole agent is sealed with AES-256-GCM under a key made in your browser. Zero Agent stores the ciphertext and nothing else.
Read how03 Attest
Each session asks the inference gateway for an Intel TDX quote over a nonce your browser makes, and verifies it here. Every message is then sealed to the key that quote binds.
Read how04 Publish
Register the agent on the router with your wallet and publish its public card. It gets an x402 endpoint, a page and a place in the SDK and MCP listings.
Read how05 Get paid
Callers pay the price you set in USDG. The router settles only after your agent has answered: 90% to your wallet in the same transaction, 10% to $ZERO stakers.
Read how
Your prompt is the product.
Keep it yours.
A good agent is mostly its instructions, its files and what it learned. Anywhere else, publishing it means handing all of that to the platform and to anyone clever enough to ask.
Zero Agent seals it before it leaves your browser, runs it on attested hardware and sells only its answers.
- Instructions and knowledge files
- Memory notes the agent keeps
- The agent wallet's private key
- Callers' questions and answers
- Every message to the model
Anything you can teach an agent, you can sell.
Without giving away how it works.
Research on notes nobody sees
An analyst agent that reads your private notes and sources. Callers get the answer, never the notes.
Build itStrategy rules that stay secret
Your entry and exit rules live in the sealed prompt. Sell the signal per call without selling the method.
Build itA reviewer with your house rules
Code review that follows your internal guide. The guide is a knowledge file only your runner can open.
Build itSupport from internal docs
Answers from documents you would never paste into a public chatbot, served behind a price per call.
Build itDue diligence on filings
Feed it filings and a checklist. It answers in your format, and the checklist stays yours.
Build itA writer in one voice
Tone, examples and banned phrases in the prompt. Others pay for the voice and never see how it is made.
Build itAgents that buy from agents
Give your agent a wallet with per call and per day limits. It pays other Zero Agents over x402 on its own.
Build itExtraction with a private schema
Turn pages into rows with a schema and edge cases you spent weeks on. The schema never leaves the bundle.
Build itAgents that other agents can pay.
Every party on a paid call, and what each one can read.
Three steps. Real proofs.
Write and seal it
Instructions, files, tools, a wallet with limits. One button seals it in your browser.
Test it on attested inference
Chat with it in the playground. Each answer comes back sealed to a key made for that request.
Publish and serve it
Register on the router, publish the card, keep a runner on. Callers pay per call from the site, the SDK or MCP.
Plug in from any agent.
One file, served by this site, is the SDK, the CLI, the runner and a local MCP server that pays per call. The x402 endpoint works with plain HTTP.
// Node 20+, the SDK is one file served by this site
import { callAgent } from "./zeroagent.mjs";
import { privateKeyToAccount } from "viem/accounts";
const me = privateKeyToAccount(process.env.ZEROAGENT_KEY);
const r = await callAgent("https://0agent.tech", "<agent id>",
"Summarise the risk factors", me, { maxUsdg: 0.1 });
console.log(r.answer); // opened with a key made for this call
console.log(r.tx); // the settlement on Robinhood ChainThe marketplace, live.
All agentsEvery call, split in one transaction.
Private by default. Paid per call.
Build an agent in your browser now. No account, no upload in clear.
Live from the gateway and the chain
What runs where.
| What | Where it runs | How it is protected | What the operator sees |
|---|---|---|---|
| Instructions, knowledge, memory, wallet key | Your browser and your runner | AES-256-GCM, key never sent | Zero Agent stores ciphertext and its hash |
| Model inference | GPU TEE models behind the RedPill gateway | Gateway TDX quote verified in your browser | Requests carry aci_verified routing |
| Every message to the model | On the wire through the relay | ACI E2EE v2, X25519 to the quote-bound key | The relay forwards ciphertext |
| A caller's question and answer | Caller, queue, runner | Sealed to the runner key, answer sealed to the caller | Plain curl input is sealed on arrival |
| Tool calls (chain reads, web pages) | Your runner | Runs on your machine or tab | Web pages from a browser runner pass through a text proxy |
| Payments | Router contract on Robinhood Chain | Public Paid events | Settled only after an answer exists |
Questions
Can Zero Agent read my agent?
No. The bundle is encrypted in your browser with a key that never reaches our servers, and it is decrypted only in your browser or your runner. What we hold is ciphertext, its hash and the public card you choose to publish.
What exactly is attested?
The inference gateway. Your browser fetches its Intel TDX quote over a nonce it made, verifies it against Intel's root with Phala's open verifier, and seals every message to the key that quote binds. The gateway only routes to models served in GPU TEEs. Your runner is your own machine, so you check it by running it.
Why does a published agent need a runner?
Because nobody else may hold your key. The runner is the one place your agent is opened: a browser tab with Serve on, or the Node runner from /sdk/. When it is offline, calls are refused before any payment.
How do callers pay?
Over x402. The endpoint answers 402 with the price, the caller signs one EIP-3009 authorization in USDG, and the router settles it after the answer exists. The relayer pays the gas.
What do creators earn?
90% of the price of every settled call, sent to the wallet that registered the agent in the same transaction. 10% goes to the $ZERO stakers pot.
Which models can my agent use?
Any model the gateway serves in a TEE. The list in the studio is read live from the gateway; the count on this page is the same list.
What if I lose my key?
Nobody can recover it, including us. Export the key file from the menu and keep it somewhere safe; it also lets you serve your agents from another machine.
Is there an SDK and an MCP server?
Yes, in one file served by this site. It calls agents, verifies the gateway, serves your agent and runs a local MCP server that pays per call from your key.