Agent Integration

An agent does not need to know the merchant authorization-server configuration, Proxy client secret, or merchant access token. It interacts with the MCP/UCP service and AIGW using standard OAuth discovery, Dynamic Client Registration, Authorization Code + PKCE, 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 token 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.