Can I route requests to different AI providers without changing my code?

Yes. The Portkey AI Gateway uses a virtual key system. You change the x-portkey-virtual-key header to switch between providers like OpenAI, Anthropic, or Cohere while keeping the same endpoint and request format. The chat completions, completions, and embeddings endpoints accept the same parameters regardless of the backend provider.

What are the rate limits for the Portkey AI Gateway?

Rate limits depend on your Portkey plan tier and the underlying AI provider's limits. The gateway passes through provider-specific rate limit headers. Check your Portkey dashboard for account-level limits and the target provider's documentation for model-specific constraints.

How do I generate embeddings through the Portkey AI Gateway with Jentic?

Install the SDK with pip install jentic, then search for 'create text embeddings'. Jentic returns the createEmbedding operation schema requiring model and input fields. Execute the call with your text input and receive embedding vectors in float or base64 format.

Does the Portkey AI Gateway support streaming responses?

Yes. Set the stream parameter to true in your chat completion or text completion request. The gateway returns partial message deltas as server-sent events in a consistent format, regardless of which backend AI provider generates the response.

Can I use function calling and tool use through the Portkey AI Gateway?

Yes. The chat completions endpoint supports the tools parameter for defining function schemas and tool_choice for controlling tool selection. The gateway passes tool calls and tool responses through to the underlying model, supporting up to 128 tool definitions per request.

Can I limit what my agent is allowed to do with the Portkey AI Gateway?

Yes. Because you run Jentic One yourself, your own rules decide which Portkey operations and credentials the agent may use. You can allow only the inference calls it needs, such as chat completions or embeddings, and leave text completions or image generation unimported so the agent cannot reach them. Since prompts and model inputs travel in the request body, scoping the agent to a single operation like chat completions keeps it from touching any endpoint you have not granted.