agentid.com valid

AgentID

AgentID is the sign-in button for AI agents. It gives every agent its own verified identity, backed by a real email address, so agents can sign in to apps without borrowing their owner's account. Apps that add AgentID always know which human is behind each agent.

For agents: AgentID gives AI agents verified identities backed by email so apps can sign them in via OIDC; includes full developer docs, CLI quickstart and brand guidelines

ai agent identityoidc sign-inagent authenticationclisign in with agentid

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T15:07:53.099Z. Cached copy · Source on agentid.com

# AgentID

> AgentID is the sign-in button for AI agents. It gives every agent its own verified identity, backed by a real email address, so agents can sign in to apps without borrowing their owner's account. Apps that add AgentID always know which human is behind each agent.

AgentID is a product of AgentMail (YC S25). It is a standard OpenID Connect provider designed specifically for AI agents. Any app that already accepts Sign in with Google can accept AgentID with two configuration values and no code changes.

## The problem AgentID solves

AI agents today sign into apps using their owner's credentials. Apps receiving agent signups today have no way to tell whether hundreds of new accounts represent one person's agent fleet or many real customers. This creates three problems:

1. Apps cannot distinguish real customers from agent-created noise
2. Apps cannot enforce per-human rate limits, seat caps, or tiers
3. Apps with compliance obligations cannot verify the human behind an agent's actions

AgentID solves all three by passing a verified `owner_email` claim to registered apps on every sign-in.

## How AgentID works

When an agent signs in to an app that supports AgentID:

1. The agent clicks "Sign in with AgentID" on the app's login page
2. The agent authenticates against auth.agentid.com using OpenID Connect
3. The app receives an id_token containing the agent's identity: `sub` (stable subject), `email` (verified inbox address), and `email_verified`
4. If the app is a registered client and asked for the owner scopes, the id_token also carries the human owner's name and email (`owner_name`, `owner_email`), with `owner_email_verified: true` alongside `owner_email`. If the owner verified with World ID, `owner_profile` also adds `owner_human_verified: true` and `owner_human_id`, an identifier for that person that is the same across every agent they own and different in every app. `/userinfo` returns the same values with the access token.

The signing key never leaves the browser that generated it. Each sign-in is a fresh signature over a one-time challenge. Owner scopes also need the `App: Share Owner` permission on the agent's AgentMail API key; without it, the agent can't finish the sign-in alone and the organization owner has to approve it.

## Client tiers

**Open clients** need no registration. The `client_id` is a URL the app controls. Open clients get the `openid`, `email` and `profile` scopes.

**Registered clients** are created in the AgentID console or with `npx @agentmail/agentid-cli init`. Registered clients get a client secret, up to 10 redirect URIs, and access to the `owner_profile` and `owner_email` scopes.

## Integration

Clerk ships AgentID as a built-in SSO connection (strategy `oauth_agentid`). AgentID also works as a custom OpenID Connect provider in Supabase, Auth0, Descope, and Auth.js v4. Better Auth apps instead install `@agentmail/agentid-better-auth`, an AgentMail-maintained provider helper for Better Auth's Generic
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=agentid.com · GET /v1/domain/agentid.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.

Claim my listing on Agent Web Map for agentid.com:
1. POST https://agentwebmap.com/v1/sites/agentid.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://agentid.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/agentid.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/agentid.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.