Question 1

Which AI assistants work with this?

Accepted Answer

Any MCP-compatible client. Claude Desktop and Claude.ai custom connectors both work directly - Claude Desktop needs the small mcp-remote bridge package since it only speaks stdio, while Claude.ai and other clients with native remote-MCP support can connect straight to our server URL.

Question 2

Can an AI assistant spend money without my say-so?

Accepted Answer

No. Every order tool always previews the exact price first. The assistant can only place and pay for an order if it sends that exact price back to us in a second call - if the price has changed or it tries to skip the preview, the order is rejected. You should still read what it's about to send before approving.

Question 3

How does the assistant authenticate?

Accepted Answer

Either with your API key as a bearer token, or by signing in with your account directly (OAuth) if your MCP client supports it - the same way you'd sign in on the website, with a consent screen showing exactly what access you're granting.

Question 4

Does it use a separate balance from the API or website?

Accepted Answer

No. An MCP-connected assistant shares the same prepaid balance and order history as your account's REST API and web checkout - one balance, three ways to spend it.

Question 5

Can I see what my AI assistant has ordered?

Accepted Answer

Yes. Every order it places appears in your dashboard and transaction history exactly like any other order, tagged so you can tell it was placed by an assistant rather than the website or a direct API call.

Question 6

Can I disconnect an AI assistant later?

Accepted Answer

Yes, from your account's balance and access settings - revoking access there immediately stops that assistant from checking your balance or placing further orders.

Give your AI assistant a mailbox

Give your AI assistant a mailbox