Forward a POST request to the provider
A pass-through: the request is forwarded to the provider named by {provider} with {path} appended, and the provider's response comes back. Bodies are the provider's own.
Request
- Base URL: https://api.vigil.tools
- URL: https://api.vigil.tools/{user_id}/{provider}/{path}
- Auth: none declared. Required headers: X-Vigil-Key
Path parameters
Your Vigil user id.
The provider segment.
The provider's own path, which may contain slashes (e.g. v1/messages).
Headers
Your Vigil API key. Required. Create a key in the dashboard, under Settings → API keys or on the setup page; it is shown once. On providers where the Authorization header is free, you can send it as Authorization: Bearer <key> instead. A request with no key, or a key Vigil does not recognise, is refused with 401; if Vigil cannot check the key in time, with a retryable 503.
A label for the agent or app making the call. Calls are grouped by this label on the dashboard, and each label has its own optimisation settings. A call with no label, or an empty one, is untagged: it follows your account default, and the dashboard groups untagged calls by prompt. A label longer than 1,024 bytes is stored as agent-label-too-long: followed by a 16-character fingerprint, and shown as "Label too long (…)". Its calls, alerts and settings stay together, but history trimming and model routing set to On run in Shadow for it.
off — run no optimisation on this request. Only the value off has an effect (it is read as a comma-separated list, so a repeated header still works). It can only switch optimisation off, never on. The call is still logged.
A comma-separated list of optimisations to switch off for this request, e.g. prompt_cache. Up to 32 names, read from the first 256 characters; unknown names are ignored. Like X-Vigil-Optimise, it can only switch things off.
Response
The provider's response, passed through, with Vigil's response headers added.
Changes
No recorded changes to this operation across all 1 revision of this API.