Frequently asked questions

Those keep your memory inside their own product. Prio's sits on your machine and works with all of them, so what you told one, the next one already knows. You have several agents now, and you'll have different ones next year. This is the part that stays.

No. You install one app, once. From there your agent works out what's available and what applies. You set it up by talking to your agent, not by filling in a wizard.

The other way round. It gets on with things, and you can say no at any time. The sensitive ones always come to you: a credential, money, and anything that gets shared.

You say yes once, and you can take it back whenever you like.

Yes, and that's deliberate. Two sets of keys, two memories, with nothing crossing between them unless you decide it does.

You pick something (a house search, a trip, a project) and their agent can work from it alongside yours. The two can compare and disagree. Neither of you sees the other's memory, only what was shared.

On your machine, in files you can read, export or delete. Not in an account we hold.

Your memory stays where it is and still works. It doesn't need us to exist.

Claude, ChatGPT, Gemini, Codex and others, through the tool connections they already support. If a new one arrives next year, it works with that too.

Documents and local files. More over time.

The waitlist is. We'll be clear about pricing well before anyone is asked to pay.

Prio is in development and we're onboarding a small group first. Leave your email and we'll be in touch when there's a spot.

Things it needs to finish what you asked: a report, a dataset, a paid API call. Small, one-off purchases that would otherwise stop it dead. Not shopping.

Only up to the limit you set, and only on the kinds of things you allowed. Anything above that waits for you. You can pause or revoke at any point.

Usually cents. You pay for what fits: a few cents for a one-off, a subscription when something gets used every week.

Yes. When something gets used regularly, a subscription is the sensible answer. You approve it once, it counts against the same budget, and you cancel it in the same place you see everything else.

Every payment leaves a receipt showing what was bought, when, for how much, and what it was for. You can see the whole history and export it.

In a wallet on your machine, under a limit you control. Not in an account we hold, and the agent never has direct access to the keys.

No. You set a limit and top it up. Everything else happens underneath.

Yes. Separate budgets, separate limits, separate histories, with nothing crossing between them.

An open standard for machines paying for things. It uses the web's "payment required" response, which existed for decades and was never used, so software can pay for one thing without creating an account first. AWS and OpenAI are building on it too.

Cards assume a person filling in a form, and a merchant relationship that lasts. Neither fits an agent that needs one report, once, at three in the morning.

Your remaining balance is yours and your receipt history is exportable. Nothing is locked in an account we hold.

Agent payments are in development. Leave your email and we'll be in touch when there's a spot.