Skip to main content
First-party SDKs for TypeScript and Python wrap the same REST API and expose typed models, retry/backoff, and fail-closed error helpers. A Go SDK is in preview and not yet published.

TypeScript

Node.js + edge runtimes. @atlasent/sdk.

Python

3.9+. pip install atlasent.

Go

Preview. Not yet published.

​
What the SDKs do for you

  • Auth plumbing. Sends your key as Authorization: Bearer <key>, rotation hooks.
  • Retries. Respect Retry-After; exponential backoff on transient errors.
  • Fail-closed helpers. Typed AtlaSentDeniedError, AtlaSentError, RateLimitError.
  • Typed models. Generated from the same openapi.yaml this site renders.
  • Audit iterators. Cursor pagination handled automatically.

​
What they don’t do

  • Cache permits. One permit = one action. Caching is unsafe.
  • Swallow errors. If the API is down, your agent halts. That’s the point.
  • Ship a policy DSL. Policies are JSON; compose them however you like.

​
Consistency

The TypeScript and Python SDKs follow the same method names: Same names, idiomatic casing per language. Explicit permit consumption is operator-tier and is not part of the standard SDK guard flow — see the operator runbook.