AWS bedrock-agentcore documentation change
Summary
Added automation tip, expanded ProcessPayment invocation methods from 3 to 5, restructured CLI examples
Security assessment
Documentation reorganization and added automation guidance without security context or vulnerability fixes
Diff
diff --git a/bedrock-agentcore/latest/devguide/payments-process-payment.md b/bedrock-agentcore/latest/devguide/payments-process-payment.md index da32eb016..01dd060e8 100644 --- a//bedrock-agentcore/latest/devguide/payments-process-payment.md +++ b//bedrock-agentcore/latest/devguide/payments-process-payment.md @@ -22 +22,5 @@ Once both exist, call `ProcessPayment` with the payment session ID, payment inst -There are three ways to invoke the ProcessPayment API: +###### Tip + +You can automate the steps on this page with the AgentCore Payments skill in the AWS agent toolkit. The skill is part of the **aws-agents** plugin and lets an AI coding agent create your Payment Manager, connector, credential provider, payment instrument, and session using the `agentcore` CLI, and add an x402 payment tool to your agent. For details, see the [quickstart](./payments-getting-started.html) and the [AWS agent toolkit on GitHub](https://github.com/aws/agent-toolkit-for-aws/tree/main). + +There are five ways to invoke the ProcessPayment API: @@ -25,0 +30,23 @@ There are three ways to invoke the ProcessPayment API: +AgentCore CLI + + +If your agent is deployed with payment capabilities configured, invoke it with payment context and the x402 interceptor handles payment processing automatically: + + + agentcore invoke \ + --prompt "Access the premium endpoint at https://example-x402-merchant.com/paid-api" \ + --payment-instrument-id <INSTRUMENT_ID> \ + --auto-session \ + --payment-user-id [email protected] + +To use an explicit session instead of auto-creating one: + + + agentcore invoke \ + --prompt "Access the premium endpoint at https://example-x402-merchant.com/paid-api" \ + --payment-instrument-id <INSTRUMENT_ID> \ + --payment-session-id <SESSION_ID> \ + --payment-user-id [email protected] + +The deployed agent’s x402 plugin intercepts HTTP 402 responses, calls `ProcessPayment`, and retries the request with proof. Requires AgentCore CLI v0.19.0 or later. + @@ -137,23 +163,0 @@ Use the `PaymentManager` class to generate payment headers manually within any a -AgentCore CLI - - -If your agent is deployed with payment capabilities configured, invoke it with payment context and the x402 interceptor handles payment processing automatically: - - - agentcore invoke \ - --prompt "Access the premium endpoint at https://example-x402-merchant.com/paid-api" \ - --payment-instrument-id <INSTRUMENT_ID> \ - --auto-session \ - --payment-user-id [email protected] - -To use an explicit session instead of auto-creating one: - - - agentcore invoke \ - --prompt "Access the premium endpoint at https://example-x402-merchant.com/paid-api" \ - --payment-instrument-id <INSTRUMENT_ID> \ - --payment-session-id <SESSION_ID> \ - --payment-user-id [email protected] - -The deployed agent’s x402 plugin intercepts HTTP 402 responses, calls `ProcessPayment`, and retries the request with proof. Requires AgentCore CLI v0.19.0 or later. -