zitadel.com valid
Zitadel preview
The server's API as one OpenAPI document: [openapi.json](/docs/openapi.json).
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T23:20:47.783Z. Cached copy · Source on zitadel.com
# Zitadel preview
> The server's API as one OpenAPI document: [openapi.json](/docs/openapi.json).
- [Overview](/docs/index.md): Start here for the current Zitadel preview docs, shipped boundaries, and navigation.
- Get started
- [Quickstart](/docs/get-started/quickstart.md): Add the Zitadel preview to a local app with the CLI and npm-binary runtime.
- [Add Zitadel to an existing app](/docs/get-started/existing-app.md): Run setup in an app you already have, what it writes for each framework, and when it stops instead.
- [Agent setup](/docs/get-started/agents.md): Install the Zitadel Agent Skills, drive the CLI with JSON envelopes, and prove auth in a browser.
- Guides
- [Run Zitadel locally](/docs/guides/local-runtime.md): Start, stop, and reset the local Zitadel the CLI manages, and sign in to its console.
- [Edit the login flow and schema](/docs/guides/plan-apply.md): Change your user schema and login flows in .zitadel/, preview the change with plan, and publish it with apply.
- [Add social sign-in](/docs/guides/social-sign-in.md): Let users sign in with Google or any OpenID Connect provider, set up with the zitadel CLI.
- [Customize the login design](/docs/guides/customize-design.md): Style the login from your app's stylesheet, or eject a starter design, add your branding, and publish it as a revision.
- [Customize the login text](/docs/guides/customize-copy.md): Change the login's wording, translate it, and label the steps you add to a flow.
- [Troubleshooting](/docs/guides/troubleshooting.md): Common CLI errors and first checks.
- Concepts
- [Concepts](/docs/concepts.md): The minimum vocabulary for the Zitadel preview, and how the pieces fit together.
- [Project, team, and user](/docs/concepts/project-team-user.md): Core resource vocabulary for the preview.
- [Configuration as code](/docs/concepts/repo-config.md): How your project's auth configuration lives in repo files, syncs with plan and apply, and becomes revisions.
- [Flows and schemas](/docs/concepts/flows-and-schemas.md): The relationship between login flows, user schemas, and generated UI.
- [Sessions and auth attempts](/docs/concepts/sessions-auth-attempts.md): Durable sessions and ephemeral authentication attempts.
- [Databases](/docs/concepts/databases.md): Choose SQLite, PostgreSQL, or Spanner for the Zitadel server.
- SDKs
- [SDKs](/docs/sdks.md): Framework packages and shared client surfaces for the Zitadel preview.
- [SDK proxy](/docs/sdks/proxy.md): Why framework SDKs proxy Zitadel requests through the app origin.
- **Server frameworks**
- [Next.js SDK](/docs/sdks/next.md): Middleware and helpers for Next.js applications.
- [Nuxt SDK](/docs/sdks/nuxt.md): Nitro middleware and composables for Nuxt applications.
- [SvelteKit SDK](/docs/sdks/sveltekit.md): A server hook and helpers for SvelteKit applications.
- [SolidStart SDK](/docs/sdks/solid-start.md): Request middleware and helpers for SolidStart applications.
- [Qwik Router S
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| liblab.com | liblab | documentation APIs and SDKs Developer tools | — | 52 | ✓ | ||
| supertokens.com | SuperTokens | documentation Cybersecurity Authentication and identity +1 | — | 51 | ✓ | ✓ | |
| civitai.com | Civitai Developer | interface Developer tools AI and machine learning +2 | — | 63 | ✓ | ✓ | |
| jazz.tools | Jazz (react) | documentation Developer tools | US | 45 | ✓ | ✓ | |
| streamlit.io | Streamlit documentation website | documentation Developer tools | DE | 55 | ✓ | ✓ | |
| composio.dev | Composio | documentation AI and machine learning AI agents and MCP +1 | — | 64 | ✓ | ✓ | |
| 1password.dev | 1Password Developer Documentation | interface Developer tools APIs and SDKs +1 | — | 62 | ✓ | ✓ | |
| tale.dev | Tale documentation | documentation AI and machine learning AI agents and MCP +1 | — | 50 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=zitadel.com · GET /v1/domain/zitadel.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage zitadel.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for zitadel.com:
1. POST https://agentwebmap.com/v1/sites/zitadel.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://zitadel.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/zitadel.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/zitadel.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.