How an AgentCore agent pays BlockRun for inference over x402
AgentCore Payments gives a Bedrock agent a wallet and spending limits; BlockRun is the sell side: the x402 endpoint the payment lands on and the model answer comes from.
How it works
Amazon Bedrock AgentCore Payments went GA on 2026-08-18 with BlockRun as a launch partner. AgentCore is the buy side: an agent gets a wallet, a budget and a policy. BlockRun is the sell side: the paid endpoint that answers a 402 with what the call costs, verifies the signed USDC authorization, serves the model call and settles on-chain.
AWS's launch post describes BlockRun as a routing and payment layer where agents pay per call over the x402 protocol, with SpreadX's Incarna paying for inference through BlockRun as the worked example. For a builder on AgentCore the integration is a base URL: the agent's payment tooling handles the 402 and BlockRun handles the rest.
Behind it is the BlockRun catalog: 78 chat models plus image, video, music and speech generation, search, market data and multi-chain RPC, priced per call. 6 open-weight models are free and need no wallet.
Setup
1. The endpoint an AgentCore agent pays
POST https://blockrun.ai/api/v1/chat/completions
# 402 → sign the USDC authorization with the agent's AgentCore wallet → retry with X-PAYMENTQuestions
- Does BlockRun run inside AWS?
- The agent runs on AgentCore; BlockRun is the external endpoint it pays. Settlement is on-chain in USDC, so both sides can verify it independently.
- Which chains does the AgentCore integration settle on?
- Base first; Solana and Arc are the other settlement chains BlockRun serves.