Sign in with Pidgeon
Sign in with Pidgeon
Let AI agents sign in to your app as themselves, and people too. Sign in with Pidgeon is one OpenID Connect provider at https://pidgeon.ai that signs people in with the code flow and PKCE, and signs agents in with no person present, by a request signed with their agent identity’s key (Agent identity). Register your site (in the dashboard or by API) to get a client id and secret, then follow the page for people or for agents.
Register your site
POST /v1/auth/clients with an API key of admin access. The client_secret is answered once; Pidgeon keeps only its hash.
curl https://pidgeon.ai/v1/auth/clients \
-H "Authorization: Bearer $PIDGEON_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "Shop Example", "redirect_uris": ["https://shop.example/auth/callback"]}'| Field | Value |
|---|---|
name | Required. What the consent screen calls your site, up to 120 characters. |
redirect_uris | Required. 1 to 20 https addresses, matched exactly; http only on localhost, 127.0.0.1 or [::1]. No fragment, no user name or password. A 400 names the address and the rule it breaks. |
pod_id | The pod the site belongs to. A key of one pod registers in its own pod. |
| Call | Access | Answers |
|---|---|---|
GET /v1/auth/clients | read | {data: [site…]}, without secrets. |
DELETE /v1/auth/clients/{client_id} | admin | 204. The site stops signing anyone in, and its sign-ins end. |
Or register it in the dashboard: Auth → Sites, or /start/auth, which also hands your coding agent a prompt that adds the button.
Edit a site, rotate its secret
PATCH /v1/auth/clients/{client_id} renames a site or replaces its return addresses, checked as registering checks them. redirect_uris is the whole new list, not an addition. The client_id and the secret stay, and sign-ins already made stay; a sign-in in flight to an address you took off fails at the token endpoint.
curl -X PATCH https://pidgeon.ai/v1/auth/clients/site_q8Zr2mX4k1Vb7nPw0sTe \
-H "Authorization: Bearer $PIDGEON_API_KEY" \
-H "Content-Type: application/json" \
-d '{"redirect_uris": ["https://shop.example/auth/callback", "https://staging.shop.example/auth/callback"]}'POST /v1/auth/clients/{client_id}/rotate-secret answers a new client_secret, once. The old secret stops working at once, with no overlap, since a rotation is most often for a secret that leaked: put the new one on your server straight away, or sign-ins fail at the token endpoint until you do. Tokens already issued are not affected.
| Call | Access | Answers |
|---|---|---|
PATCH /v1/auth/clients/{client_id} | admin | The site, without its secret. |
POST /v1/auth/clients/{client_id}/rotate-secret | admin | The site, with its new client_secret this once. |
A key of one pod reaches its own pod’s sites only. In the dashboard: Auth → Sites → the site → Edit or Rotate secret.
Discovery and keys
Any OpenID Connect library configures itself from the issuer. ID tokens are RS256, signed with the key at /.well-known/jwks.json.
curl https://pidgeon.ai/.well-known/openid-configuration
curl https://pidgeon.ai/.well-known/jwks.jsonregistration_endpoint is open dynamic client registration (RFC 7591) for apps that connect to a person’s account and cannot publish a client metadata document: MCP clients and other connected apps (OAuth for apps). It registers public clients only, with no secret, so it is not how a site signs people in: register your site above for a client secret. A client registered this way that nobody connects, signs in or names in a mandate within 30 days is deleted.
There is no end_session_endpoint: Pidgeon has no RP-initiated logout. Signing out of your site ends your own session; Pidgeon’s ID token is not a session and expires in ten minutes. To end what your site holds at Pidgeon, revoke the sign-in’s access token at revocation_endpoint. A person signs out of Pidgeon itself in Pidgeon.
Who signs in
| Who | How | Page |
|---|---|---|
| A person | Authorization code with PKCE, after signing in to Pidgeon. Free. | People |
| An agent, as itself | Token exchange (RFC 8693), the request signed with its agent key. One agent sign-in on your meter. | Agents |
| An agent, for a person | The same exchange under a mandate the person gave it. | Mandates |
Every ID token says which with kind: person or agent. A sign-in never becomes an API key: its tokens are refused by /v1.
See all three live at demo.pidgeon.ai, our own site that signs in with Pidgeon: sign in as yourself, watch an agent sign in, then let it sign in as you, and read the claims each time. Your own agent can sign in there too: GET https://demo.pidgeon.ai/api/whoami without a token answers the client_id and issuer to use, and with one answers the claims the site accepted.