> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Amazon Bedrock AgentCore

Amazon Bedrock AgentCore is AWS's managed platform for deploying and operating AI agents.
AgentCore Gateway connects agents to tools and services, while AgentCore Payments gives them
controlled access to payment instruments. The Coinbase integration connects that payment layer to
a CDP wallet and the x402 Bazaar, allowing agents to discover and pay for x402 services
autonomously.

## Set up on AWS first

If you haven't already, create an AgentCore [Payment Manager and CoinbaseCDP connector](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-create-manager.html),
then add the [Coinbase x402 Bazaar Gateway target](https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/payments-connect-bazaar.html).
Every x402 payment made through the CoinbaseCDP connector is verified and settled by the
[CDP Facilitator](/x402/seller/facilitator). You do not need to configure a separate
facilitator.

## What "Coinbase x402 Bazaar" actually is

The Gateway target named "Coinbase x402 Bazaar" is CDP's x402 discovery service: a
semantic-search catalog of more than 23,000 x402 resources, exposed as three MCP tools:
`search_resources`, `proxy_tool_call`, and `validate_endpoint`. AWS's console shows you how to
wire it in; it doesn't say what it actually is or what it guarantees.

It's a discovery layer of hosted listings; Coinbase can't guarantee the uptime or correctness
of any individual listing.

Want to query the same catalog directly, or the buyer-side detail on reading a result? See
[Discover services](/x402/buyer/discover-services).

## Reaching the wallet directly

The wallet behind a `PaymentInstrument` created through your CoinbaseCDP connector is a real CDP
end-user wallet, and everything that happens to it runs through CDP APIs.

Two things follow from that:

**Funding and granting permission already happen outside AgentCore.** When you create the
instrument, the response includes a `redirectUrl` to Coinbase's hosted WalletHub — that's where
your end user funds the wallet and grants your agent delegated-signing permission. There's no
API for either step; WalletHub is the only activation path, by design. If you'd rather host that
flow yourself instead of redirecting to Coinbase's, fork
[`coinbase/cdp-agentcore-template`](https://github.com/coinbase/cdp-agentcore-template), a
reference Next.js app built on the same self-custodial wallet packages (`@coinbase/cdp-core`,
`@coinbase/cdp-hooks`, `@coinbase/cdp-react`) plus the CDP SDK on the backend.

**You can also operate on that wallet yourself, outside the agent.** The same CDP API key and
Wallet Secret already sitting in your PaymentCredentialProvider work directly against the CDP
SDK — check a live balance, send or receive outside the x402 flow, or pull transaction history.
See [Delegated signing](/wallets/using-wallets/delegated-signing),
[managing end-user accounts](/wallets/using-wallets/create-and-manage-wallets), and the
[end-user accounts REST API](/api-reference/v2/rest-api/end-user-accounts/end-user-accounts).