> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atlasent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Choose a safe AtlaSent quickstart and learn the authorization, Permit, verification, execution, and evidence boundaries.

**Fastest path (about 5 minutes):** [create a free account](https://console.atlasent.io/auth/sign-up?utm_source=docs\&utm_medium=quickstart), then follow the **[Developer / API quickstart](/quickstart/developer-api)**: one request to a demo action that returns `allow`, then the `hold` and `deny` variants.

Other paths: **[Choose your AtlaSent quickstart](/quickstart/choose-your-path)**.

<CardGroup cols={3}>
  <Card title="Developer / API" icon="code" href="/quickstart/developer-api">
    Evaluate a sandbox action, handle a bounded Permit, verify it, and inspect the evidence that actually exists.
  </Card>

  <Card title="Enterprise operator" icon="building" href="/quickstart/enterprise-operator">
    Take one protected action from organization setup through rehearsal and readiness review.
  </Card>

  <Card title="AI agent / MCP" icon="robot" href="/quickstart/agent-mcp">
    Put AtlaSent between an agent tool request and a consequential effect without treating tool access as authority.
  </Card>
</CardGroup>

## The lifecycle you are learning

**Verified identity → organizational authority → authorization → Permit → verification → execution → evidence**

Each stage establishes something different. An `allow` does not prove execution. A verified Permit does not prove the downstream effect occurred.

## Existing developer sequence

The detailed developer references remain available:

1. [API key](/quickstart/api-key)
2. [First evaluation](/quickstart/first-evaluation)
3. [Verify a Permit](/quickstart/verify-permit)
4. [Inspect/export available audit evidence](/quickstart/audit-export)

<Warning>
  Portable signed evidence bundles and offline third-party bundle verification must not be described as generally available unless the current [Trust Portal](/trust/index) and compliance claims matrix say they are. Follow those sources for current maturity.
</Warning>

<Note>
  The Developer / API quickstart uses a demo action that executes nothing. Console keys are live keys, so its requests send `context.environment: "production"`; that names the key's environment and activates nothing. The other paths have their own safety guidance: follow the page you choose. Protecting a real production action is a separate, controlled step.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.