VANGU / API
Know the supported features before you integrate.
Your plan determines model access; the protocol determines the request format. GET /v1/models is the source of available model IDs for your key.
| Feature | Support | Integration note |
|---|---|---|
| Chat Completions | /v1/chat/completions | Text and SSE streaming for models available to your key. |
| Responses | /v1/responses | Check the requested model, tools and streaming format together with your client. |
| Anthropic Messages | /anthropic/v1/messages | The message format is adapted; access is through available Vangu models. |
| Function calling | Function tools | You provide tool definitions and execute tool code in your own client. |
| Client-side tools | CLI / IDE / MCP | File, shell, MCP and computer capabilities must be provided by your client. |
| Provider-hosted execution | Code Interpreter / hosted shell / computer | Vangu does not provide a managed Python, shell or computer environment for these tools. |
| Web search | Model / endpoint | Support depends on model and endpoint. Use an allowed model with the documented request format. |
| Image generation and editing | /v1/images/* | Quality, size and format must match the values supported by the selected model. |
| Conversation history | Client-managed history | Manage full message history in your integration; do not reuse another provider’s response IDs. |
| Quotas and billing | Plan / wallet | Plan units, model multipliers and wallet prices are different measures. Use the checkout summary as the reference. |