Software that an agent can hire by the call.
Most software is sold by the month to a person who has to learn it. We build the other kind: focused apps that take a request, do one job well, and hand back something finished — reachable by an AI agent as easily as by you, and priced per call so trying one costs cents. When the job needs to know your world, it runs on a brain built from your own sources, and it shows its receipts.
What we believe
Three commitments the product is built around. They cost us features, which is how you know they're real.
Cited, never guessed
Every grounded answer links back to the source it came from. When your material doesn't cover the question, the honest output is “I don't know” — and a result too thin to be worth anything is never billed.
Private by default
Your brains are yours. They stay private until you choose otherwise, and an answer is generated only from your own sources — never blended with someone else's.
Work, not just recall
A brain that only answers is a filing cabinet. Ours does the job: an app takes a request, does the work, and hands back something finished — a brief, a chart, a transcript, a decision.
How it fits together
Three moves. The third is optional — plenty of the fleet needs nothing from you but a URL.
Point an agent at the store
One MCP server discovers the whole fleet. Your agent lists what's there, reads what an app takes, and calls it — no browsing, no account setup, no human in the loop.
Pay per call, two ways
An agent with a wallet pays in USDC over x402, keyless and account-free. A person with an Ounie account spends credits from a monthly pool. Same app, same result, two rails.
Ground it in what you know
Add your files, links and notes and Ounie builds a cited, interlinked wiki from them. Point an app at that brain and its output stops being generic — it starts being yours, with receipts.
What we won't claim
An app is only as good as what it's given. Point one at a thin brain and you get a thin answer — so we tell you it's thin and don't charge for it, rather than dressing it up.
Some of the fleet depends on data we buy from someone else. When an upstream provider is down, the honest response is to refuse before quoting you a price — not to take the money and fail.
A signal is not a verdict. Our checks say what the evidence shows and where it runs out; none of them are legal clearance, and we say so on the app itself, not in a footnote.
We ship what works. A parameter that can't be delivered honestly is removed from the docs and the interface rather than quietly returning something plausible.
Start with one call
Pick an app, run it once, and see what comes back. No subscription to try it, and nothing to install first.
Building against the API? Read the docs or see the agent surface.