Developers
Use Developer tools to integrate Kadryn, route AI traffic, debug ingestion, inspect traces, and validate production readiness.
What this menu is for
Developer tools is the technical control plane for Kadryn integration. It covers API keys, gateway routing, direct usage ingestion, webhooks, logs, traces, SDK examples, and diagnostics.
Use this menu when you need to prove that data is entering Kadryn correctly, requests are traceable, events are signed, and integration health is production-ready.
Tabs
- Overview: readiness, setup progress, and plan-relevant developer status.
- API Keys: credentials for Kadryn APIs and automation.
- Gateway: route AI requests through Kadryn when the plan includes gateway proxying.
- Usage Ingestion: send direct usage events when traffic does not pass through the gateway.
- Events & Webhooks: configure signed event delivery and inspect webhook health.
- Logs & Traces: debug requests, errors, latency, and correlated traces.
- SDKs & Examples: implementation references for common stacks.
- Diagnostics: run technical checks for ingestion, gateway, keys, and delivery.
Production checklist
- Use separate keys for development, staging, and production.
- Store secrets in a secret manager, never in source code or client-side bundles.
- Attach stable metadata such as project, environment, workflow, tenant, customer, and cost center.
- Use idempotency keys for event ingestion and retry-safe jobs.
- Verify webhook signatures before trusting inbound events.
- Use traces and request IDs when debugging incidents.
Plan behavior
Developer tools is plan-aware. Basic setup can be visible while advanced gateway, signed webhooks, logs, traces, or diagnostics remain locked. Locked tabs should explain the required capability without implying the workspace is broken.
Ownership
Platform teams usually own this menu. Admins own access and key lifecycle. Finance teams should use the outputs in Costs and Reports rather than handling technical credentials directly.