Forward a request named in a header, inspecting it on the way
The same call as /gateway/{destination}, with the destination in X-Secure-AI-Target instead of in the path. This is the form both SDKs use: a client that is handed a fetch cannot have the address rewritten underneath it, and a URL inside a URL is a thing some HTTP clients refuse to send at all.
The vendor's own credential goes in X-Secure-AI-Forward-Authorization, verbatim and with its scheme — "Bearer sk-…", not "sk-…", because it becomes the outbound Authorization header exactly as sent. The Authorization header on this request is ours and is never forwarded.
Request
- Base URL: https://secureai.one/v1
- URL: https://secureai.one/v1/gateway
- Auth: HTTP bearer
Headers
The full destination URL.
Sent onward as the destination's Authorization header.
Groups this request's record with the rest of that agent's.
Response
The destination's own response, passed back. X-Secure-AI-Decision says whether anything was changed; X-Secure-AI-Audit-Id identifies the record.
Changes
No recorded changes to this operation across all 1 revision of this API.