# KT Accounts Developer Documentation

> How to connect an app to KT Accounts, the account service for aidenkt sites: the sign-in kit for sites on aidenkt.com, OpenID Connect for any domain, the developer portal, and the agent API.

Every page is also served as Markdown at its path with `.md` added (the home page is `/index.md`). Some pages need a KT account or an agent access token (`Authorization: Bearer kta_…`); this list shows only the pages the requester can read.

## For Agents

- [Agent guide (canonical)](https://accounts.aidenkt.com/developers/agents.md): get a key with apps.manage, register and manage apps, integrate them
- [OpenID Connect discovery](https://accounts.aidenkt.com/.well-known/openid-configuration)
- [Complete documentation](https://docs.aidenkt.com/llms-full.txt): every page listed below in one file

## Pages

- [KT Accounts Developer Documentation](https://docs.aidenkt.com/index.md): How to connect an app to KT Accounts, the account service for aidenkt sites.
- [Agents](https://docs.aidenkt.com/agents/overview.md): How an AI agent gets a key with apps.manage, exchanges it for access tokens, and what it can and cannot do.
- [Quick Start](https://docs.aidenkt.com/getting-started/quick-start.md): Pick the integration path that fits where the app runs, register it, and connect it.
- [In-App Identity](https://docs.aidenkt.com/integrate/in-app-identity.md): Tell KT Accounts who the person is inside your app, shown on their Account Settings page.
- [Sign in with KT Accounts](https://docs.aidenkt.com/integrate/openid-connect.md): OpenID Connect with PKCE for apps on any domain and for servers.
- [Roles and Permissions](https://docs.aidenkt.com/integrate/roles-and-permissions.md): Named permissions, and the role permissions every badge implies.
- [Check Sign-In on a Server](https://docs.aidenkt.com/integrate/server-checks.md): Why the kit protects nothing, what a site's server can check today, and the helpers for it.
- [Sign-In Kit](https://docs.aidenkt.com/integrate/sign-in-kit.md): The Log In button, the person's picture and menu, and the app switcher for a site on aidenkt.com.
- [Troubleshooting](https://docs.aidenkt.com/integrate/troubleshooting.md): The usual symptoms when connecting a site, and what each one means.
- [Read Who Is Signed In](https://docs.aidenkt.com/integrate/who-is-signed-in.md): Ask KT Accounts who is signed in from a page on a registered aidenkt.com origin.
- [Appearance](https://docs.aidenkt.com/portal/appearance.md): The app's colour from the aidenkt palette, and where its name, colour and icon appear.
- [Credentials and Rotation](https://docs.aidenkt.com/portal/credentials.md): The client ID, the client secret, how the secret is shown once, and how to rotate it.
- [Icon Maker](https://docs.aidenkt.com/portal/icon-maker.md): Make an app's icon from an uploaded image, an icon from the pack on a palette colour, or one emoji on a palette colour.
- [Register an App](https://docs.aidenkt.com/portal/register-an-app.md): Who can register apps, every field on the New App form, and the rules each one follows.
- [Suspend and Delete](https://docs.aidenkt.com/portal/suspend-and-delete.md): What suspending and deleting an app do, and who can do each.
- [Who Sees It](https://docs.aidenkt.com/portal/who-sees-it.md): The app's audience, which decides who gets its tile in Your Apps and the app switcher.
- [Access to These Docs](https://docs.aidenkt.com/reference/docs-access.md): Who can read which pages of docs.aidenkt.com, and how people and agents sign in to read them.
- [Endpoints](https://docs.aidenkt.com/reference/endpoints.md): Every KT Accounts endpoint an app or agent uses, with its authentication.
- [Limits](https://docs.aidenkt.com/reference/limits.md): Rate limits, sizes and lifetimes across KT Accounts.
- [Palette Keys](https://docs.aidenkt.com/reference/palette.md): The 40 aidenkt palette colours an app's colour and icon background can use.
- [Scopes and Claims](https://docs.aidenkt.com/reference/scopes-and-claims.md): The OpenID Connect scopes, the claims each one adds to the ID token and userinfo, and what each integration path can see.