ZeroID

Open Source Autonomous Agent Identity Management Infrastructure

Open Source ZeroID GitHub Repository: ZeroID

Current Language Coverage

Language
Status
Notes

Python

Available

Strong developer experience for admin APIs and token operations

TypeScript

Available

Good browser and Node ergonomics with built-in token exchange support

Current Resource Shape

The SDK already exposes a meaningful ZeroID surface, but feature coverage is not identical across languages yet.

Python

Current client resources:

  • client.identities

  • client.agents

  • client.oauth_clients

  • client.credential_policies

  • client.api_keys

  • client.tokens

  • client.signals

TypeScript

Current client resources:

  • client.identities

  • client.agents

  • client.oauthClients

  • client.credentialPolicies

  • client.apiKeys

  • client.tokens

  • client.signals

  • client.credentials

Important Behavioral Notes

Tenant Context

Admin routes use tenant headers. The SDK handles this for you by carrying:

  • account_id / project_id in Python

  • accountId / projectId in TypeScript

For local development, SDK clients can auto-generate tenant IDs if you do not provide them. That is convenient for quickstarts, but production systems should use stable tenant values.

Public Token Endpoints

The token APIs do not send tenant headers as admin routes do. The server derives tenant context from credential material, such as:

  • API key metadata

  • client credentials

  • WIMSE URI

  • subject token

API Key Bootstrap

If you initialize the client with a ZeroID API key:

  • The SDK can exchange it for a short-lived access token

  • The token can be cached and refreshed automatically

  • Higher-level flows, like token exchange, become easier to implement

  • Read Python if you want the fastest first integration path.

  • Read TypeScript if you are integrating from Node or a TypeScript service.

SDK vs REST Guidance

Use the SDK when:

  • You want a better developer experience

  • You are integrating from the application code

  • You want token caching, tenant header handling, and typed models

Use REST directly when:

  • You need a language without an SDK yet

  • You are working from infrastructure or platform tooling

  • You need a feature that is server-supported but not yet surfaced in your preferred SDK

What's Next?

Last updated