AIGW documentation

AIGW documentation

What AIGW does, the two tokens it issues, and where to start for your role.

Checked against the Evaluation environment, Console 0.10.1 / 0.14.1, on October 19, 2026. Release status

AIGW is an OAuth authorization server for AI agents. It sits in front of a merchant's existing identity system, registers agents automatically, gets the user's consent, and lets the tool servers agents call reach the merchant's API with a token the agent never sees.

Fastest path

Every AIGW flow starts the same way: an agent calls a protected service and gets a challenge back. The quickstart picks up from there and ends with a working token.

Where every flow startshttp
HTTP/1.1 401 UnauthorizedWWW-Authenticate: Bearer resource_metadata="https://mcp.example.com/.well-known/oauth-protected-resource"

Start by role

Key concepts

TermMeaning
AccountYour organization in the AIGW Console.
ProjectGroups Resources, Proxy clients, agents and agent policy. Tokens never cross Projects.
ResourceA merchant API that agents can reach, with its own authorization URL and discovery documents.
Proxy clientCredentials for an MCP or UCP service, used to redeem merchant tokens.
Agent policyWhich agents are approved, pending or rejected in a Project.
AIGW tokenThe access token the agent holds. Bound to one Resource.
Merchant tokenThe merchant's own access token, kept in AIGW's vault and released only to the service.

The full picture, with the architecture diagram, is in How AIGW works.

Environment

These docs describe the Evaluation environment. See release status for what is supported in it.

ServiceURL
Consolehttps://aigw.eval.loginid.ai
Gateway APIhttps://api.aigw.eval.loginid.ai
Core token servicehttps://core.api.aigw.eval.loginid.ai
Playgroundhttps://playground.aigw.eval.loginid.ai/

Get help