Skip to main content
Use the hosted MCP endpoint in ChatGPT, Claude or another compatible client:
It uses Streamable HTTP and account OAuth. Create an account first if needed. When the client requests a protected action, complete sign-in and approve the connection and its spending limits in the app. Connection approval sets limits; it does not approve a future data purchase.

​
Tools the assistant sees

The interactive card has a separate approval action that the person uses to approve the displayed total price ceiling. The assistant must not approve for the person. After approval the Gateway runs the task and saves the results; the assistant should read that state instead of starting another purchase.

​
When information is missing

The card or assistant asks a clarifying question for needs_input, or presents candidates for needs_selection. Answer with the missing fact or choose the intended entity. The saved task continues with the offered action; there is no need to start a new purchase merely to clarify. Browsing the directory does not promise that every published endpoint is runnable. Check the returned availability and let apiosk_discover verify whether the exact question has a priced plan.

​
Spending and recovery

A connection has a per-request and daily limit. The person can change or revoke it in the app under Integrations. A workspace-bound connection spends that workspace’s budget; otherwise it uses the person’s balance. Use apiosk_status and the saved task reference for a follow-up or interrupted response. Status reads do not buy data. For setup commands, see MCP clients. Server integrations without a person in the loop use an organisation API key.