Developer DocsstableUpdated 2026-05-14

Overview

Developer guide for integrating Kadryn safely.

Integration goals

A good Kadryn integration should send complete usage data, preserve request traceability, keep secrets server-side and make costs attributable to a real owner.

Required metadata

At minimum, send project and environment metadata. For better reporting, include team, feature, user segment and workload type when available.

Verification checklist

  • A test request appears in Developers > Logs & Traces.
  • Usage is attributed to the expected project.
  • Cost appears in the correct environment.
  • Failures include enough IDs for debugging.
  • No Kadryn or provider secret is visible in the browser.