Gateway
Route provider traffic through Kadryn for visibility and control.
When to use Gateway
Use Kadryn Gateway when you want runtime visibility and control over provider calls. Gateway is the right path when requests need central logging, policy checks, budget caps, approval workflows or consistent provider routing.
Request flow
Your application sends the AI request to Kadryn Gateway instead of calling the provider directly. Kadryn authenticates the request, attaches workspace context, applies configured controls, forwards the request to the selected provider and records the result.
Required headers
Authorization: Bearer $KADRYN_API_KEY
Content-Type: application/json
x-kadryn-project: project_slug_or_id
x-kadryn-environment: production
traceparent: 00-...Metadata
Gateway requests should include project, environment and feature metadata. This metadata is what makes downstream cost allocation, alerts and guardrails useful.
Failure handling
Handle authentication errors, provider errors, policy blocks, rate limits and retryable server errors separately. Preserve the Kadryn request ID in logs so support can trace the exact event.