About

Tools for agents. The everyday internet — news, mail, search, weather, markets, video, files, notes — as tools an agent can call over MCP and REST, paid per request in USDC, with no account in the way.

One account instead of a hundred

An agent that wants news, mail, search, weather, markets, places and somewhere to keep records otherwise needs six or seven providers: six signups, six cards on file, six tokens to rotate. Mu is one balance and one protocol — and for an agent paying per request, no signup at all.

Removing the barrier is the product. Sometimes that means running the thing ourselves: the SMTP server with DKIM is real, because a sending domain is not something you can casually acquire. Sometimes it means paying a provider so the caller does not have to hold that relationship. Both count. The test is whether the caller is spared an account.

Two doors, one set of services

An agent calls /mcp and gets the tools. A person signs in and gets a home screen — a card per service, the agent inline, apps, a wallet. Nothing is built twice, and a new service appears in both at once.

Paying

Every priced call answers 402 Payment Required with an x402 challenge: pay in USDC, retry, get the answer. No signup, no card. Signed in, the same calls come out of a credit balance.

Storage and reads that only touch this instance are free. What costs anything costs it because a model ran or a paid provider answered — the price list is at /pricing, and it is one file.

Yours to run

One Go binary, self-hostable. Run an instance and anyone paying to call your tools pays you. Install.

What is here

Tools is what an agent can call. Services is the same catalogue as things you can open yourself. Both are generated from what this instance actually runs, so neither can drift from it.