readrail.com

What It Is

ReadRail positions itself as a payment rail for “agentic web access.” Its core is not traditional acquiring or a wallet, but rather a way for media and publishers to turn content access into a micro-payment flow that can be priced, settled, and proven. A site declares preview rules, full-access pricing, and allowed Agents via /.well-known/readrail/policy.toml. When an Agent requests the full text, it receives an HTTP 402 signed quote; after settlement, it revisits with a proof token and receives the full content.

Core Capabilities and Payment Flow

Based on the copy, ReadRail’s design revolves around three things: policy, quote, and proof. Publishers can make previews free, charge per request for full access, set pricing by path, allowlist by Agent identity, and reject scrapers. The system records request states such as paid, preview, and blocked. Each settled read generates a signed receipt, which has value for attribution, auditing, and export. It claims a p50 latency of 38ms and is compatible with robots.txt and sitemap.xml. Agents that have not integrated the protocol, as well as humans and search engines, keep the original experience.

Pricing and Settlement

The example price is $0.0012/req, while the console also shows a read record of $0.0040, indicating support for content-level micropayments and path-based differentiated pricing. For settlement, the copy says Agents can settle on-chain or off-chain, with x402:base given as an example, and notes that publishers can receive daily payout to your account. However, the platform commission, withdrawal fees, supported currencies, fiat settlement, and minimum payout threshold are not disclosed.

Compliance, Risk Controls, and Integration

Compliance information is the main blank spot: there is no visible explanation of licensing, KYC/AML, custody of funds, or tax handling. The risk-control side is more focused on access control, including Agent identity allowlists, blocking known scrapers, signed quotes, a 60-second settlement window, and auditable proof. Integration appears lightweight, emphasizing no SDK requirement, HTTP-based access, and well-known configuration, with support for exporting proof to S3, data warehouses, or CDPs.

Pros, Cons, and Best-Fit Users

The main advantage is that ReadRail connects monetization, attribution, and auditing for AI content reads. It is well suited to media outlets, publishers, data-content sites, and AI platforms that want to access content in a compliant way. The downside is that the ecosystem depends on protocol support from Agents, while payment methods, fees, and regulatory arrangements are not sufficiently disclosed. At present, it only shows 12 launch publishers, so its ability to scale still needs validation. The copy does not mention access from China, so network availability, RMB settlement, and local alternatives cannot be confirmed.