What Is AgentID? The Sign-In Button for AI Agents

TLDR: AgentID is a sign-in method for AI agents, launched by AgentMail on October 6, 2026. Agents authenticate as themselves through a standard OpenID Connect provider, and the app receiving the sign-in learns both who the agent is and which human owns it. This guide covers how the protocol works, how it compares to Microsoft's similarly named Entra Agent ID, how apps add it, and what can go wrong when they do.

Agents have a login problem. The web assumes a person behind every account, so when an agent needs to use an app it borrows its owner's email, reads the verification code out of the owner's inbox, and signs up as its human. AgentMail, the company behind agent-only email inboxes, says it watched this happen from both sides: support requests started coming from agents, and account owners had no idea their agents had created accounts. The company's answer, announced on its blog on October 6, 2026, is AgentID, a dedicated sign-in for agents that keeps a human on record. This guide is the concept, the mechanics, and the failure modes, with the You.com angle on what an agent does after it signs in.

What Is AgentID?

AgentID is an OpenID Connect identity provider that lets an AI agent sign in to an app as itself, backed by a real email inbox, with the agent's human owner on record. AgentMail's launch post frames it as "Sign in with Google, except the thing signing in is an agent, and the identity it uses is its own." Every AgentID is backed by a real AgentMail email address that serves as a stable, verified identity and a working inbox the app can write to.

Two things travel with every sign-in. First, a stable identifier for the agent and its verified email, which is enough to give the agent its own account. Second, for apps that register and request the owner scopes, the name and email of the human who owns the agent. That owner record is the point: it lets an app attribute ten agents to one person, cap free-tier signups per owner instead of per email, revoke one agent without touching the others, and reach the human when something goes sideways.

AgentMail reports that the sign-in flow shares no password and grants the app no access to the agent's mail. The identity claims are the whole contract, which keeps the blast radius of a compromised sign-in to whatever the app itself allows.

How Does AgentID Work?

Under the hood AgentID is a standard OpenID Connect provider at auth.agentid.com, so any OIDC library can talk to it without a vendor SDK. The provider publishes a live discovery document at the well-known path, which is how OIDC clients learn its endpoints. The document, fetched during research for this guide in October 2026, declares:

import json, os, urllib.request

# Step 1: read AgentID's published OIDC discovery document
DISCOVERY = "https://auth.agentid.com/.well-known/openid-configuration"
doc = json.load(urllib.request.urlopen(DISCOVERY))
# doc["issuer"]                 -> "https://auth.agentid.com"
# doc["authorization_endpoint"] -> "https://auth.agentid.com/v0/authorize"
# doc["token_endpoint"]         -> "https://auth.agentid.com/v0/token"
# doc["jwks_uri"]               -> "https://auth.agentid.com/v0/jwks.json"
# doc["scopes_supported"]       -> openid, email, profile,
#                                 owner_profile, owner_email
# id_tokens are ES256-signed and the flow requires PKCE with S256

# Step 2: point your auth stack at the issuer.
# AgentMail ships guides for Clerk, Supabase, Auth0, Better Auth,
# and Auth.js, and its CLI runs the setup in one command:
#   npx @agentmail/agentid-cli init

# Step 3: the signed-in agent needs live data, not just an account.
# The You.com Web Search API is one POST away:
req = urllib.request.Request(
    "https://ydc-index.io/v1/search",
    data=json.dumps({"query": "latest openid connect security guidance",
                     "count": 5}).encode(),
    headers={"Content-Type": "application/json",
             "X-API-Key": os.environ["YDC_API_KEY"]},
    method="POST",
)
with urllib.request.urlopen(req, timeout=30) as resp:
    results = json.load(resp)

The provider supports two client tiers, per AgentMail's documentation as of October 2026. Open clients require no registration: an app sets its client ID to a URL it controls and requests the standard openid, email, and profile scopes. Registered clients, created through the AgentID console or CLI, add the owner_profile and owner_email scopes, which deliver the owner's name and email in the id_token and from the userinfo endpoint. AgentMail notes that an app registered for the owner claims never receives a sign-in without them.

The flow itself respects that agents do not click browser links the way people do. AgentID's integration docs describe a handoff where the app or agent starts a sign-in and receives a single-use magic URL, valid for five minutes, that completes the flow and activates the agent's API key. The id_token is signed with ES256 and verified against the provider's published keys, which is standard OIDC and the part most implementations get wrong when they skip verification.

Why Do Agents Need Their Own Sign-In?

The status quo AgentID replaces has three failure shapes. Borrowed credentials: the agent uses its owner's email and password, so the app sees a human who is not really there. Unowned accounts: the agent creates accounts nobody knows about, which is what AgentMail says it found in the hundreds after letting agents sign up for AgentMail itself. Blanket blocking: apps that cannot tell an agent from an attacker rate-limit or ban all non-human traffic and lose the agent customers entirely.

AgentID's answer is to make the agent's non-humanness a first-class claim instead of a detection problem. The app stops guessing whether traffic is a bot and starts reading a signed statement: this is an agent, here is its stable identifier, and here is the human who answers for it. Bot detection, API keys inside a person's existing account, and delegated access all answer neighboring questions, per AgentMail's launch post, and can sit alongside AgentID rather than compete with it.

How Is AgentID Different From Microsoft Entra Agent ID?

The names collide, so get the disambiguation right early. Microsoft Entra Agent ID is an enterprise identity and access management product for agents operating inside an Entra tenant, with agent blueprints, required sponsors, and Conditional Access policies. AgentID by AgentMail is an OpenID Connect provider for agents signing in at apps outside any single organization. AgentMail's own comparison post, published September 9, 2026, puts the distinction in one line: Entra Agent ID governs agents inside your tenant, while AgentID lets an agent sign in at applications outside any single organization and tells those apps which human owns it.

The practical difference is who sees the human. In the Entra model the sponsor relationship lives inside the tenant that operates the agent, so a third-party SaaS receiving a sign-in does not learn who sponsors it. In the AgentID model the owner email is delivered to the relying app in the token itself. One is intra-organizational governance, the other is cross-organizational accountability, and an evaluation or procurement doc that says "Agent ID" without saying which one is asking for confusion.

How Do Apps Add Sign In With AgentID?

Because it is standard OIDC, adding AgentID is configuration rather than code. AgentMail publishes integration guides for Clerk, Supabase, Auth0, Better Auth, and Auth.js, plus a custom guide for any other OIDC-capable stack, and the CLI command npx @agentmail/agentid-cli init detects the provider, registers the app, configures it, and verifies the flow. Apps that integrate get listed in the AgentID directory, which agents can search through the AgentMail API and CLI. When we checked the directory in October 2026 it listed 37 apps across search, data, and developer tooling categories, and the October 6 launch post named Firecrawl, Turso, TinyFish, Manufact, Telnyx, and Rho as early acceptors.

On cost, AgentMail's launch FAQ states there is no usage pricing and no per-sign-in fee for apps, because the company makes money selling agent inboxes to agent platforms rather than charging the apps that accept sign-ins. That is the vendor's own description of its model as of October 2026, so price it into your evaluation the way you would any vendor claim.

What Happens After the Agent Signs In?

Identity is step one for an agent, not the whole job. A signed-in agent with its own account still needs live data: current web results, page content, and research that postdates any model's training. That is the gap You.com fills for agents, with the same machine-first spirit as AgentID. You.com publishes a docs index for agents at you.com/docs/llms.txt with clean markdown variants of every docs page, and runs an MCP server that any agent can connect to for web search, contents, and research tools. The Web Search API guide covers the REST surface, the MCP server docs cover the agent-native path, and the Web Search API resource hub collects the deeper guides. How agents find those surfaces in the first place is its own emerging discipline, covered in What Is Agentic Resource Discovery?

What Can Go Wrong When You Add AgentID?

Each failure mode has a detection, and none of them announce themselves.

Skipped token verification is the classic OIDC mistake wearing a new hat: an integration reads the id_token claims without checking the ES256 signature against the provider's published JWKS, so any party that can post a token to your callback becomes an agent. Detection: verify the signature and the issuer on every sign-in, in the library, not in application code you forgot to write. Treating owners as accounts is quieter: ten agents share one owner, so free-tier caps keyed to email count the household ten times while caps keyed to owner_sub count it once. Detection: key entitlement limits to the owner claim, not to the agent's address. Assuming more access than granted: AgentMail is explicit that a sign-in shares no password and opens no mailbox, so an app that emails the agent through its own channels rather than the inbox is inventing a capability nobody promised. Detection: enumerate what the claims actually say before building flows on top of them. Homonym drift closes the set: docs that say "Agent ID" without naming AgentMail or Entra produce integrations against the wrong product. Detection: write the product name as AgentID (AgentMail) in requirements and link the integration guide.

Related Guides

• Web Search API: A Complete Guide
• What Is a Web Search API?
• What Is Agentic Resource Discovery?
• Research API: A Complete Guide

FAQ

What is AgentID? An OpenID Connect identity provider from AgentMail, launched October 6, 2026, that lets an AI agent sign in to an app as itself. Each AgentID is backed by a real AgentMail email address, and apps that register for the owner scopes also learn which human owns the agent.

Is AgentID the same as Microsoft Entra Agent ID? No. Entra Agent ID governs agents inside an enterprise Entra tenant with blueprints, sponsors, and Conditional Access. AgentID by AgentMail is a cross-organization sign-in that delivers the owner's email to whatever app the agent logs in to. The similar names describe different products solving different problems.

Is AgentID free for apps? AgentMail's launch FAQ says there is no usage pricing and no per-sign-in fee for apps, with the company making money selling agent inboxes to agent platforms instead. That is the vendor's stated model as of October 2026, so treat it as a claim to confirm against their current pricing page, not a permanent fact.

How do agents find apps that accept AgentID? Through the directory at agentid.com and through the AgentMail API and CLI, which agents use to list and search apps that accept AgentID sign-ins. Every integrated app gets listed, and the directory grouped 37 apps into categories like search, data, and developer tools when we checked in October 2026.