aws-samples / aws-samples/sample-agentcore-cloudfront-x402-payments
Real-world usage report: live AgentCore Payments proof built on this sample (real on-chain settlement)
- Dominant language
- Python
- Stars
- 25
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I want to share a real-world extension of this sample. We adapted the payer-agent to discover a live third-party service (RelayShield, a threat-intel API) via CDP's own x402 Bazaar as a native AgentCore Gateway MCP target, rather than the sample's own demo seller so this is agent-discovers-and-pays-for-a-real-external-service, not a sandboxed demo.
Two separate real-money proofs, both settled on-chain:
Local run: funded an embedded CDP wallet with real USDC on Base, agent found and paid for a live endpoint via CDP delegated signing. Tx confirmed via direct RPC.
Deployed to AgentCore Runtime (Docker/ECR, no local dependency): same flow, invoked the live deployed Runtime, agent discovered and paid for the same endpoint. Second tx confirmed via direct RPC.
Both used the official AgentCorePaymentsPlugin for automatic 402-handling with no custom payment client needed. Happy to share more implementation detail if useful, and open to a written case study or blog collaboration if that's of interest on your end. AgentCore Payments being in Preview seems like exactly the kind of real usage proof that'd be useful to have documented.
Contributor guide
Research direction
No documentation file, test, or entry point is named. First confirm whether maintainers want a case study or blog contribution, then find the repository's documentation location and agree on the format and required implementation details. Done means an accepted document records both local and AgentCore Runtime proofs, including live endpoint discovery, automatic 402 handling, and on-chain settlement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker, python
- Domain
- blockchain, cloud, documentation, payments
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100