02-use-cases/pay-for-api-agent: add AgentCore Payments Pay-for-API#1504
Open
ggChris2 wants to merge 1 commit into
Open
02-use-cases/pay-for-api-agent: add AgentCore Payments Pay-for-API#1504ggChris2 wants to merge 1 commit into
ggChris2 wants to merge 1 commit into
Conversation
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
Latest scan for commit: Security Scan ResultsScan Metadata
SummaryScanner ResultsThe table below shows findings by scanner, with status based on severity thresholds and dependencies: Column Explanations: Severity Levels (S/C/H/M/L/I):
Other Columns:
Scanner Results:
Severity Thresholds (Thresh Column):
Threshold Source: Values in parentheses indicate where the threshold is configured:
Statistics calculation:
|
ggChris2
force-pushed
the
pay-for-api-agent
branch
6 times, most recently
from
1c5c0c4 to
70724dc
Compare
github-actions
Bot
added
01-tutorials
ggChris2
force-pushed
the
pay-for-api-agent
branch
5 times, most recently
from
b7023a0 to
b12c144
Compare
…d use case Strands buyer agent that pays autonomously for a metered HTTP API via AgentCore Payments. The seller is a Fun Facts API behind API Gateway + Lambda that returns HTTP 402 with an x402 payment requirement; the agent consumes the requirement, calls ProcessPayment via the AgentCorePaymentsPlugin, retries the request with the signature header, and returns the fact along with the dollar amount spent. Includes: - Fun Facts seller (CDK + Lambda + x402 facilitator integration) - Buyer agent (Strands + bedrock-agentcore plugin) - Two credential providers (Coinbase CDP + Privy) - Four payment instruments (EVM + Solana per provider) - AgentCore Runtime deployment via CodeBuild (no local Docker) - AgentCore Memory wiring for per-user session continuity - CloudWatch + X-Ray observability with vended log delivery The notebook clones the Privy Wallet Hub frontend from privy-io/aws-agentcore-sdk on first run (Apache-2.0, jointly maintained by Privy and AWS AgentCore) and drives its lifecycle inline. The clone target lives under privy-delegation/ and is gitignored so it never re-enters the repo.
ggChris2
force-pushed
the
pay-for-api-agent
branch
from
b12c144 to
df9f4d0
Compare
leewc
reviewed
May 16, 2026
| role=build_trigger_role, | ||
| timeout=Duration.minutes(15), | ||
| memory_size=128, | ||
| code=aws_lambda.Code.from_inline( |
leewc
reviewed
May 16, 2026
| """Pay for API — buyer agent CDK stack. | ||
|
|
||
| Provisions the full AgentCore Runtime stack for the buyer agent **without | ||
| requiring Docker on the machine running `cdk deploy`**: |
There was a problem hiding this comment.
Also - why did you need a Lambda to provision runtime? I understand to work around the need for docker (smart!) but it looks like it's possible doing it without a provisioner lambda?
leewc
reviewed
May 16, 2026
| @@ -0,0 +1,363 @@ | |||
| #!/usr/bin/env bash | |||
| # setup-roles.sh — create the four IAM roles the notebook assumes into. | |||
There was a problem hiding this comment.
do we still need this file if you've set up roles via CDK?
leewc
approved these changes
May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…e case
Strands buyer agent that pays autonomously for a metered HTTP API via AgentCore Payments. The seller is a Fun Facts API behind API Gateway + Lambda that returns HTTP 402 with an x402 payment requirement; the agent consumes the requirement, calls ProcessPayment via the AgentCorePaymentsPlugin, retries the request with the signature header, and returns the fact along with the dollar amount spent.
Includes:
Notebook walks through cred-provider setup, manager + connector + four instruments, two sessions, four (provider, network) local agent runs, and a runtime deploy with the same four-run matrix.
Amazon Bedrock AgentCore Samples Pull Request
Important
review readylabel to it. Only PRs withreview readywill be reviewed.Issue number:
Concise description of the PR
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.