Amazon Web Services says Incarna used Amazon Bedrock AgentCore payments to let its AI agents pay BlockRun for model inference one request at a time, with the flow now running in production on Base. BlockRun is a pay-as-you-go inference router offering more than 90 models from more than 15 providers over x402, a protocol for paid web services. Each request receives its own quote and settlement. AWS says the managed service connects an agent to a wallet, signs payments and enforces spending limits outside the model.

Incarna completed the integration in three days: one day to build and two to test. The work took roughly 200 lines of application code, compared with the two to three months originally estimated. During beta, agents processed more than 1,000 payments, ranging from $0.001 to $0.05 per call, with each transaction settled individually on-chain using USDC on the Base network.

In the payment flow, BlockRun responds to an inference request with an HTTP 402 “Payment Required” challenge and a price. AgentCore payments checks the quote against the session’s spending cap, signs authorization from the agent’s wallet, and returns cryptographic proof for BlockRun to verify. BlockRun then supplies the inference and records the charge. Since payment happens per request, an agent pays only for calls it makes.

AgentCore payments supports two x402 schemes. The “exact” scheme is intended for a known price; “upto” lets an agent authorize a maximum for dynamically priced services, with the provider settling the actual usage up to that cap. Each payment session also has an expiry time. Incarna sets sessions to match a day’s budget, and AWS says the infrastructure enforces the ceiling even if the agent’s code or prompt is manipulated.

Incarna provisions wallets through a Coinbase CDP connector; customers own the wallets and give Incarna delegated authorization. Builders can store Coinbase CDP or Stripe Privy credentials in AWS Secrets Manager, then set up a Payment Manager, connector, spending limit and payment instrument. AWS says teams can configure the service through the Agent Toolkit for AWS in Claude Code, Kiro or Codex, or use the AgentCore CLI, SDK or AWS SDK. The customer funds the embedded wallet and grants signing permission through a redirect URL; test networks can use testnet USDC.

Amazon Web Services says Incarna used Amazon Bedrock AgentCore payments to let its AI agents pay BlockRun for model inference one request at a time, with the flow now running in production on Base. BlockRun is a pay-as-you-go inference router offering more than 90 models from more than 15 providers over x402, a protocol for paid web services. Each request receives its own quote and settlement. AWS says the managed service connects an agent to a wallet, signs payments and enforces spending limits outside the model.

Incarna completed the integration in three days: one day to build and two to test. The work took roughly 200 lines of application code, compared with the two to three months originally estimated. During beta, agents processed more than 1,000 payments, ranging from $0.001 to $0.05 per call, with each transaction settled individually on-chain using USDC on the Base network.

In the payment flow, BlockRun responds to an inference request with an HTTP 402 “Payment Required” challenge and a price. AgentCore payments checks the quote against the session’s spending cap, signs authorization from the agent’s wallet, and returns cryptographic proof for BlockRun to verify. BlockRun then supplies the inference and records the charge. Since payment happens per request, an agent pays only for calls it makes.

AgentCore payments supports two x402 schemes. The “exact” scheme is intended for a known price; “upto” lets an agent authorize a maximum for dynamically priced services, with the provider settling the actual usage up to that cap. Each payment session also has an expiry time. Incarna sets sessions to match a day’s budget, and AWS says the infrastructure enforces the ceiling even if the agent’s code or prompt is manipulated.

Incarna provisions wallets through a Coinbase CDP connector; customers own the wallets and give Incarna delegated authorization. Builders can store Coinbase CDP or Stripe Privy credentials in AWS Secrets Manager, then set up a Payment Manager, connector, spending limit and payment instrument. AWS says teams can configure the service through the Agent Toolkit for AWS in Claude Code, Kiro or Codex, or use the AgentCore CLI, SDK or AWS SDK. The customer funds the embedded wallet and grants signing permission through a redirect URL; test networks can use testnet USDC.