Sticky routing for whole conversations

Sessions

Group related requests with an x-session-id header to keep provider routing sticky and trace a conversation end to end.

x-session-id → Sticky routing
x-session-idSticky routingTurn 1Provider BTurn 2Provider BTurn 3Provider B
Same provider, warm prompt cache
01

One header

Add x-session-id. Nothing else.

02

Warm caches

Stay on the provider holding your cache.

03

On by default

Stickiness works out of the box.

04

Session view

Follow a conversation in the activity log.

Built for

  • Coding agents

    Long tool loops stay cache-friendly

  • Chat apps

    Consistent behavior across turns

  • Debugging

    Follow one user's whole conversation

Tag a conversation
terminal
1curl https://api.llmgateway.io/v1/chat/completions \2  -H "Authorization: Bearer $LLM_GATEWAY_API_KEY" \3  -H "Content-Type: application/json" \4  -H "x-session-id: conversation-9f8e7d6c" \5  -d '{6    "model": "claude-sonnet-4-6",7    "messages": [8      {9        "role": "user",10        "content": "Hello!"11      }12    ]13  }'
Read docs

More in routing & reliability

All features

Start using Sessions today

One API key. Every model. Live in minutes.