Connect Your Apps
Point client applications at the FinOps AI Gateway using a virtual key.
Applications connect to the FinOps AI Gateway the same way they would connect to OpenAI — by changing the base URL and using a virtual key issued in Monetize360.
Prerequisites
- A virtual key created and active in Finops Config
- Your tenant's gateway URL (provided by your Monetize360 administrator)
- Models and providers configured and allowed for the key's organization
Authentication
Send the virtual key JWT in the Authorization header:
Authorization: Bearer <virtual-key-jwt>Monetize360 generates and rotates these tokens when you create virtual keys. Applications should obtain the token from your secure configuration store — not hard-code provider API keys.
Alternative headers supported by the gateway:
| Header | Format |
|---|---|
Authorization | Bearer <token> (OpenAI style) |
x-bf-vk | Virtual key token |
x-api-key | Virtual key token (Anthropic style) |
x-goog-api-key | Virtual key token (Google style) |
OpenAI-compatible example
Replace YOUR_GATEWAY_URL and YOUR_VIRTUAL_KEY_JWT with values from your administrator:
curl -X POST "https://YOUR_GATEWAY_URL/v1/chat/completions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_VIRTUAL_KEY_JWT" \
-d '{
"model": "gpt-4o-mini",
"messages": [{"role": "user", "content": "Hello"}]
}'SDK configuration
For OpenAI, Anthropic, or other SDKs, set:
| Setting | Value |
|---|---|
| Base URL | Your tenant gateway URL (e.g. https://gateway.your-tenant.example/v1) |
| API Key | Virtual key JWT |
No SDK-specific FinOps package is required — the gateway speaks standard provider APIs.
Framework-specific guides
| Integration | Guide |
|---|---|
| LangChain | LangChain SDK |
| OpenAI SDK | OpenAI SDK |
| Anthropic SDK | Anthropic SDK |
| Google GenAI | GenAI SDK |
| LiteLLM | LiteLLM SDK |
| Cursor & other IDEs | CLI & IDE Agents |
See What is an integration? for the full list of protocol adapters and endpoint paths.
Test before production
Use the Simulator to verify budgets, routing, and model allowlists with the same virtual key before pointing production traffic at the gateway.
API reference
For full endpoint documentation, open the API tab in the navigation bar.