> ## Documentation Index
> Fetch the complete documentation index at: https://docs.portkey.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Servers

> Host your agent servers

The Agent Servers are the virtual servers that act as a client to the upstream agent server and as a server to the downstream agent clients.

## Introduction

Instead of your clients (your users/your services) directly interacting with the upstream agent server,
The Prisma AIRS AI Gateway allows you to:

* create virtual servers and provision access with virtual keys,
* control access to the agent itself and the specific skills and capabilities that the agent provides.

This way, your clients can be restricted to the necessary scopes and capabilities with full observability and logging.

## Usage

Simply replace your agent server URL wherever you are invoking it with the virtual server URL.

For example, if your slug is `test-server` your URL becomes `https://aigw.portkey.ai/agent/test-server`.

> [!NOTE]
>
> For self-hosted deployments, replace `aigw.portkey.ai/agent` with your gateway
> URL.

## Forwarding Caller Headers

By default, only the static headers configured on the agent are sent to the upstream agent. To also pass headers from the caller's request through to the agent, set `forward_headers` in the agent's configuration. It accepts the same shorthand, allowlist, and all-except forms as MCP servers, including header renaming and the same list of protected headers. See [Forwarding Headers](https://docs.portkey.ai/docs/aigw/product/mcp-gateway/authentication/forwarding-headers.md) for the full format.

```json theme={"system"}
{
  "forward_headers": ["x-request-id", "x-tenant-id"]
}
```

Static headers configured on the agent always replace a forwarded header of the same name. Connection-level headers (such as `host`, `connection`, `content-length`, and `accept-encoding`) are never forwarded.

## Logging

Every request to the virtual server will be logged and can be viewed in the [logs](https://docs.portkey.ai/docs/aigw/product/observability/logs.md) section.

This forms the basis of the [observability](https://docs.portkey.ai/docs/aigw/product/observability.md) and [governance](https://docs.portkey.ai/docs/aigw/product/enterprise-offering/access-control-management.md) features at the AI Gateway.

## Further reading

> [card] [Quickstart](https://docs.portkey.ai/docs/aigw/product/agent-gateway/quickstart.md)
>
> Get started with the Agent Gateway by registering your first agent.

> [card] [Agent Registry](https://docs.portkey.ai/docs/aigw/product/agent-gateway/registry.md)
>
> Manage your agent integrations and control access to agents and their skills.

> [card] [Advanced code snippets and examples](https://docs.portkey.ai/docs/aigw/product/agent-gateway/advanced-code-snippets-and-examples.md)
>
> Explore additional examples for fetching agent cards and invoking agents.

> [card] [Logs](https://docs.portkey.ai/docs/aigw/product/observability/logs.md)
>
> View and analyze logs for every request made through your agent servers.


## Related topics

- [Agent Gateway](https://docs.portkey.ai/docs/aigw/product/agent-gateway.md)
- [Agent Registry](https://docs.portkey.ai/docs/aigw/product/agent-gateway/registry.md)
- [Agent Catalog](https://docs.portkey.ai/docs/aigw/product/catalogs/agents.md)
- [API Keys (AuthN and AuthZ)](https://docs.portkey.ai/docs/aigw/product/enterprise-offering/org-management/api-keys-authn-and-authz.md)
- [Slack MCP server](https://docs.portkey.ai/docs/aigw/integrations/mcp-servers/slack-mcp-server.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.