2 min lesson
What the gateway normalizes
Pick two rows from the table in "What the gateway normalizes" and explain the choice each one supports.
Step 1 of 3
What the gateway normalizesthe dialect problem
Name the specific seams that diverge across providers. Vague "it abstracts the API" reads as someone who has never onboarded a second provider. The texture below is what reads as having shipped one.
- Surface
- Auth
- How it diverges
- Header vs SDK token, per-org keys, rotating creds
- What the gateway exposes
- One credential resolver keyed by provider + region
- Surface
- Request shape
- How it diverges
- Message roles, tool schemas, sampling param names
- What the gateway exposes
- One canonical request DTO the adapter serializes
- Surface
- Streaming
- How it diverges
- SSE event names, delta framing, [DONE] sentinels
- What the gateway exposes
- One internal token-delta stream, provider-agnostic
- Surface
- Errors
- How it diverges
- 429 means rate-limit here, quota there, overload elsewhere
- What the gateway exposes
- A normalized error taxonomy: retryable, fatal, shed
- Surface
- Token accounting
- How it diverges
- Usage in trailer, in headers or estimated
- What the gateway exposes
- One usage record per request for cost + capacity
| Surface | How it diverges | What the gateway exposes |
|---|---|---|
| Auth | Header vs SDK token, per-org keys, rotating creds | One credential resolver keyed by provider + region |
| Request shape | Message roles, tool schemas, sampling param names | One canonical request DTO the adapter serializes |
| Streaming | SSE event names, delta framing, [DONE] sentinels | One internal token-delta stream, provider-agnostic |
| Errors | 429 means rate-limit here, quota there, overload elsewhere | A normalized error taxonomy: retryable, fatal, shed |
| Token accounting | Usage in trailer, in headers or estimated | One usage record per request for cost + capacity |
The adapter is where the dialect dies; everything above it sees one model.