All Agntix APIs are served from a single base URL behind the API gateway:
api.agntix.ai — internal service URLs are not exposed.
Method 1 — API Keys (recommended)
API keys are scoped to an organization and may be limited to specific features (read-only, voice-only, etc.) at creation time.Create
Open Settings → API Keys in the dashboard and click Create key. Pick a name, the scopes you want, then copy the value. The key is shown once. You can also create keys programmatically:Use
Pass the key in thex-api-key header on every request:
Rotate
Keys do not expire, but you can rotate at any time:- Create a new key with the same scopes.
- Roll your service over to the new key.
- Delete the old key from the dashboard — the deletion is effective immediately.
Method 2 — Bearer JWT (Clerk session)
If you’re building a first-party dashboard and the user is already signed in with Clerk, send their session JWT instead of an API key:Getting a JWT in the browser
If you’re using the official Clerk SDK:Permissions & errors
See the full list on the error codes page.
Security best practices
Rotate keys quarterly
Use the dashboard’s bulk rotation tool, or wire CI/CD to do it on a schedule.
Scope down
Issue a separate key per service with only the features it actually needs.
Use Bearer JWTs in the browser
Browser code never holds a long-lived API key.
Monitor usage
The dashboard’s API Keys page shows last-used timestamp per key — purge stale ones.