Skip to main content
A connection lets an AI client — ChatGPT, Claude, an agent runtime — act for one person’s Apiosk account, within limits that person set. The rule behind the whole flow: a person is the authority on money; software is the authority on nothing. The assistant does the typing; the person makes the decision.

​
The flow

  1. Invitation. In the app, under Integrations, the person starts a connection. They get a short invitation to paste into the assistant.
  2. Intent. The assistant registers what it is and what it wants to be called, and receives a verification link to hand back.
  3. Approval. The person opens that link, signs in, and sets the two ceilings: per request and per day. A short code confirms the approval.
  4. Tokens. The assistant exchanges the code for its own access and refresh tokens. The secret itself never passes through the assistant’s prompt.
Connecting through a client that supports OAuth — the MCP server — collapses steps 1 to 4 into the client’s own consent screen.

​
What a connection may do

Each call is checked against the ceilings at the moment it reserves money, so a burst of parallel calls cannot slip past them.

​
Connections or API keys?

Use a connection when a person is in the loop. Use an API key when a server runs on its own.