When a workspace shares one MCP key, get_credit_usage tells you the team spent something and nothing more. Per-user tokens make the spend traceable to a person, and revocation as simple as signing out. The cancellable async path is the other well-judged piece: a long completion that has gone wrong can be stopped rather than paid for in full.
Vamos' endpoint. The design point is that a completion can be run synchronously or as a job you poll and can cancel, which matters when the work is long.
- chat_completion — the synchronous path
- chat_completion_start, chat_completion_poll, chat_completion_cancel — the asynchronous one, cancellable mid-flight
- create_chat, list_chats, get_messages — conversations that persist
- get_credit_usage and auth_status — what you have spent and whether the connection is valid
OAuth, per user — the documentation notes there is no shared MCP key, and the token is bound to a workspace. Included on Pro and Business; MCP calls draw on the workspace credit pool at no extra cost.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen