Agent Integration

This section is for developers building the AI agent/client. An agent does not need to know the merchant authorization-server configuration, Proxy clientProxy clientThe server-side credential (client ID and secret) the MCP/UCP service uses to authenticate itself to AIGW. Never give it to an agent. secret, or merchant access tokenMerchant access tokenA token issued by the merchant's own authorization server. Only the MCP/UCP service sees it, never the agent.. It interacts with the MCPMCPModel Context Protocol: a standard way for AI agents to call tools and data sources exposed by a server./UCP service and AIGW using standard OAuth discovery, Dynamic Client Registration, Authorization Code + PKCEPKCEProof Key for Code Exchange: binds an authorization request to the later code exchange so a stolen code is useless., and bearer tokens.

Try it first

The Playground acts as an agent and runs every step below against AIGW, showing each real request and response.

Agent journey

1. Discover authentication
2. Register with AIGW
3. Request authorization
4. Handle the callback
5. Call MCP / UCP

What the agent stores

The agent may receive/store:

• dynamically issued client_id and client_secret;
• PKCE verifier/state for the current flow;
• AIGW access tokenAIGW access tokenThe token an agent receives after the user authorizes it. It says which user approved which agent for which scopes. and refresh token if issued/used;
• the MCP/UCP protected-resource metadata and discovered AIGW endpoints.

It should not receive the MCP/UCP server's Proxy client secret or the merchant access token.