Starts the call through an AI tool
API Proxy
Requests started working after I switched to a relay URL. Check who can see the prompts, files, and key along that path.
Requests started working after I switched to a relay URL. Check who can see the prompts, files, and key along that path.
Starts the call through an AI tool
Forwards requests and results
Runs the model and generates the result
The request travels to the model provider through the relay, and the result comes back through the same relay.
Both the request and response pass through the relay: The prompt, context, file fragments, and any credential sent with the request may reach the relay first. The Provider's response also passes through the relay before reaching the tool.
Public information only makes a service easier to verify: A published operator, official documentation, and service terms make boundaries, billing, and privacy policies easier to inspect, but do not make a platform inherently trustworthy. If a third party handles the request, still verify retention, key handling, and the upstream service.
Unknown services carry greater risk: Some unofficial relays may assemble access through account pools or reverse proxies. If a service records requests, changes responses, or injects content, the AI tool usually cannot audit how that relay handles your data. Do not send keys, source code, or sensitive business data to an unknown relay.
Send the request through the API proxy Base URL and read the key from an environment variable. Do not print the real key; check the proxy address, route, and authorization before a safe test request.