Skip to main content
Amazon Bedrock AgentCore is a managed platform for deploying and operating AI agents on AWS. For x402 and CDP, the relevant pieces are AgentCore Payments (agent-side microtransaction orchestration), AgentCore Gateway (MCP tool ingress and outbound targets), and AgentCore Identity (credential storage for payment providers). AWS developers can connect Coinbase x402 Bazaar as an AgentCore Gateway target for discovery and paid tool calls, and can use AgentCore Payments with CDP Wallets so agents complete x402 payment flows on behalf of users.
AgentCore payments is currently available as an AWS preview. Features and APIs may change before general availability.

​
What you can build

With the Coinbase integration on AgentCore you can:
  1. Provision and sign with CDP user wallets — End users authenticate and grant agent permissions through a wallet UI; agents use AgentCore Payments to complete x402 payment flows on their behalf (subject to user-configured permissions, and your budgets and policies on the AWS side).
  2. Discover and pay for x402-enabled services — Add the Coinbase x402 Bazaar target to AgentCore Gateway so agents can search the same catalog documented in x402 Bazaar (Discovery Layer).
CDP remains the source of truth for facilitator URLs, Bazaar behavior, and wallet concepts. AWS controls Gateway wiring, credential storage in AgentCore Identity, IAM, and runtime configuration.

​
Bedrock AgentCore products in this integration

ProductRole with CDP
AgentCore PaymentsOrchestrates x402 payment flows on the agent side — receives HTTP 402 responses, signs transactions through your configured wallet provider, and returns payment proof to merchants.
AgentCore GatewayExposes MCP tools to your agents. Add the Bazaar MCP server as an outbound target so agents can call search_resources and proxy_tool_call through your Gateway URL.
AgentCore IdentityStores Coinbase CDP API credentials as a PaymentCredentialProvider so agents can sign without embedding secrets in code.
Typical setup order: configure CDP credentials in AgentCore Identity → give end users a wallet UI to sign in and grant delegation → create a Payment Manager and Connector in AgentCore Payments → add the Bazaar target to AgentCore Gateway → wire the Gateway MCP URL and payments plugin into your agent runtime.

​
User-facing wallet UI

AgentCore Payments signs on behalf of end users only after they authenticate and grant a time-bound delegation. You need a frontend where users sign in, fund wallets (optional), and approve agent access. Choose one of two paths:
Coinbase also offers a hosted wallet UI (Wallet Hub) for AgentCore integrations where developers prefer not to build a frontend. Wallet Hub is currently available in a limited preview for AgentCore use cases — contact your AWS or Coinbase integration point for access. General availability for all CDP developers is planned separately.

​
Prerequisites on the CDP side

Use this section when you configure AgentCore Payments to use CDP Wallets. You do not need these steps solely to add the Coinbase x402 Bazaar Gateway target for discovery.
  1. Create or select a CDP project and generate API credentials as described in CDP API authentication (API key ID, API key secret, and Wallet Secret).
  2. In the CDP Portal, under Products > Non-custodial Wallet > Security, enable Delegated signing.
  3. Provide a user-facing wallet UI so end users can sign in and grant delegation before your agent signs on their behalf.
Store CDP credentials only in AWS systems designed for secrets (for example AgentCore Identity PaymentCredentialProvider), not in agent source code. Credential fields and rotation guidance are in AWS’s prerequisites for AgentCore payments.

​
Configure Bazaar in AgentCore Gateway

Add the Coinbase x402 Bazaar as an outbound target so agents connected to your Gateway can discover and call paid x402 endpoints.

​
Target configuration

FieldValue
Target typeIntegrations → Coinbase x402 Bazaar (console) or mcp-server (CLI/API)
MCP endpointhttps://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp
Outbound authenticationNo Authorization (only supported option)
Tools exposedsearch_resources (semantic catalog search), proxy_tool_call (invoke a discovered paid endpoint)
Agents connect to your Gateway’s MCP URL (for example https://<gateway-id>.gateway.bedrock-agentcore.<region>.amazonaws.com/mcp), not directly to the Bazaar endpoint above. The Gateway forwards tool calls to the Bazaar target. For tool behavior and client-side payment handling, see Bazaar MCP Server and the MCP server guide.

​
Setup paths on AWS

Choose one path to register the target. AWS documents each in Coinbase Bazaar via AgentCore Gateway:
In the Amazon Bedrock console, open AgentCore > your Gateway > Targets:
  1. Choose Add target
  2. For Target type, select Integrations
  3. Select Coinbase x402 Bazaar (pre-populated — no manual endpoint entry needed)
  4. Leave Outbound authentication as No Authorization
  5. Deploy the Gateway and note the Gateway MCP URL for your agent runtime
agentcore add gateway-target \
  --name CoinbaseTarget \
  --type mcp-server \
  --endpoint https://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp \
  --gateway MyGateway

agentcore deploy
Use bedrock-agentcore-control create_gateway_target with an mcpServer endpoint pointing at the Bazaar MCP URL. See the full request shape in AWS’s Coinbase Bazaar via AgentCore Gateway guide.
Once the target is live, configure AgentCore Payments (Payment Manager, Connector, and payments plugin) so agents can automatically settle HTTP 402 responses from Bazaar-discovered endpoints. See AWS’s Process a payment guide. AWS setup and operations CDP protocol, wallets, and templates