Anchor Browser with Agentic Payments
Anchor Browser · Intelligence & Research
Certification per AWS Marketplace.
Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
Anchor Browser
Enterprise AI agent teams require browser sessions that are reliable, persistent, and observable, without the fragility of improvised headless automation. Anchor Browser is cloud-native browser infrastructure purpose-built for AI agents, providing isolated, production-grade sessions with the operational rigor that enterprise deployments demand.
Show the rest of the publisher’s description (17 more lines)
Anchor Browser with Autonomous Payments
Co-innovated with the AWS Generative AI Innovation Center (GenAIIC) Partner Agent Factory (PAF), Anchor Browser with agentic payments eliminates payment friction from agent workflows. When an agent's session encounters a paywalled resource or protected API, Anchor Browser completes the transaction in-session and without intervention. Developers are not required to manage wallet keys, payment headers, or retry logic within their agent code.
This capability is powered by Amazon Bedrock AgentCore payments.
How It Works
Amazon Bedrock AgentCore provides the services to build, connect, and optimize AI agents securely at scale. Its payments capabilities enable end-to-end transaction processing with developer-defined spending limits.
When the feature is enabled, Anchor Browser provisions a dedicated, budget-scoped AgentCore payment session for each browser session. Upon encountering an x402 (HTTP 402 Payment Required) or Merchant Payment Protocol (MPP) response, AgentCore payments:
Intercepts the payment-required response
Allows AI agents to autonomously sign zero-gas EIP-712 payment authorization proofs
Presents the signed transaction to the merchant
Unlocks the paywalled content or API while enforcing the predefined budget
The result is seamless access to paid web content within agent workflows, with built-in spending controls and no custom payment integration required.
Benefits
Autonomous payments, zero integration effort. Enable a single session flag. There are no wallet keys or payment headers for the agent developer to manage.
Budget-scoped by design. Every session receives its own AgentCore payment session with a hard spending ceiling and a time-bound authorization window. A runaway agent cannot overspend.
Built on open standards. Implements the x402 protocol (v1 X-PAYMENT and v2 PAYMENT-SIGNATURE) and MPP for internet-native payments. Compatible with any x402- or MPP-enabled merchant or API.
Production-grade browser, not a sandbox. Runs on Anchor Browser's existing cloud infrastructure. Payments inherit the same session reliability and observability as every other capability.
Graceful fallback. If a payment cannot complete (budget exhausted, unsupported network, or malformed merchant response), the original 402 response passes through untouched. The agent can handle it explicitly rather than failing silently.
Highlights
Highlighted by the publisher on AWS Marketplace.
Toggle-based activation. Enable with a single session flag (session.x402: true). No other code changes required.
Per-session spending controls. Each session receives its own AgentCore payment session with a configurable spend limit and expiration window.
Automatic protocol handling. Supports both x402 v1 and v2 payment header formats and MPP without additional configuration.
Preview
1 image
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Plans and pricing as listed
3 listed- Units
- Units
- Units
Refund terms
As stated by the publisher on AWS Marketplace.
Follow the policy in the contract.
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.