Concepts
Narrative explanations of how AtmanID thinks about access governance, JML lifecycle, non-human identity, and the audit chain. Start here if you’re evaluating AtmanID or onboarding to identity governance for the first time.
Concepts
Narrative explanations of how AtmanID thinks about access governance, JML lifecycle, non-human identity, and the audit chain. Start here if you’re evaluating AtmanID or onboarding to identity governance for the first time.
Guides
Step-by-step task recipes for admins and operators — registering non-human identities (curl and SDK), the MCP bearer-token flow, MCP gateway policy, agent insights standing instructions, and branding, with more landing each sprint. For end-to-end scenarios like onboarding an app and running a certification campaign, see Tutorials. This is what you reach for at 4pm on a Friday.
Reference
The v1 API (generated from the OpenAPI spec), the TypeScript SDK, and the changelog. The fall-back when guides don’t cover your edge case. The RBAC model lives in Architecture & Security and the Iris tool catalog in the Iris section.
Iris
AtmanID’s natural-language interface to your IAM data. Ask “how many users are active” or “show me overdue certifications” and Iris answers — with citations.
Tutorials
End-to-end walkthroughs combining concepts and guides into complete scenarios. “Onboard your first app and run a certification campaign,” “Set up an external auditor for SOC2 evidence.”
Architecture & Security
Tenant isolation model, audit chain integrity, cross-tenant defense, encryption posture, SOC2 status, NIST/ISO mapping. The page CISOs and procurement teams go to first.
Developers
Curated entry into the docs for developers building integrations. Fastest path from “what is this?” to “I shipped my first integration” — links straight to first API call, SDK setup, API/SDK reference, common patterns, and changelog.
Your first authenticated call, in full. Set ATMANID_BASE_URL to your tenant’s base URL (provided with your onboarding) and ATMANID_API_KEY to an API key:
curl -X GET "$ATMANID_BASE_URL/api/v1/users" \ -H "Authorization: Bearer $ATMANID_API_KEY" \ -H "Accept: application/json"{ "data": [ { "id": "3f2b9c1e-…", "email": "sarah.chen@example.com", "first_name": "Sarah", "last_name": "Chen", "status": "ACTIVE" } ], "total": 48, "page": 1, "limit": 25, "total_pages": 2}Every response carries an X-Request-Id that correlates to a tamper-evident audit row — so any action is provable, not just plausible. Identity-creating mutations take an idempotency_key body field; lists always return the { data, total, page, limit, total_pages } envelope.
Jump straight to the Developers landing for the curated entry — first API call in 10 minutes, TypeScript SDK setup, endpoint reference, common patterns. Building with a coding agent? Use the agent integration prompt. Or go straight to Reference → API for the OpenAPI spec, Reference → SDK for the TypeScript client, or Tutorials → First API call for the end-to-end walkthrough.
AtmanID is an AI-native IAM platform: runtime enforcement for AI agents, with humans and agents governed on one identity model and one tamper-evident audit trail. Most IAM platforms were designed before generative AI existed and added chat to an existing UI. AtmanID was designed around the question “what does Identity & Access Management look like when an AI assistant is the primary interface?” The answer reshapes everything from the data model up.
Four differentiators that show up everywhere in this documentation:
/llms.txt and /llms-full.txt for any agent to ingest.© AtmanID · Privacy