Tag requests, filter later

Request Metadata

Attach user, country or any other context to requests with custom headers and filter your logs by it.

Get startedRead the docs
request headers
POST /v1/chat/completions
Authorization: Bearer llmgtwy_••••
X-LLMGateway-User-ID: 9403f741
X-LLMGateway-Country: US
X-LLMGateway-Tenant: acme
Filter the activity log by any value
01

Just headers

No body changes.

02

Any key

Users, tenants, versions.

03

Filterable logs

Find one user's requests.

04

Multi-tenant

Track usage per customer.

Built for

  • Support

    Look up a user's history

  • Releases

    Compare app versions

  • SaaS tenants

    Usage per customer

Add context
terminal
curl https://api.llmgateway.io/v1/chat/completions \  -H "Authorization: Bearer $LLM_GATEWAY_API_KEY" \  -H "Content-Type: application/json" \  -H "X-LLMGateway-User-ID: 9403f741" \  -H "X-LLMGateway-Country: US" \  -d '{    "model": "gpt-4o",    "messages": [      {        "role": "user",        "content": "Hello!"      }    ]  }'
Read docs

More in observability & cost

All features

Data Retention

Keep metadata, or keep everything

Data Streams

Logs to your SIEM and warehouse

Notifications

Know before it breaks

Start using Request Metadata today

One API key. Every model. Live in minutes.

Start buildingBrowse models