Cloudflare Launches Beta for AI Payment Solutions
On September 30, Cloudflare initiated the beta phase for two innovative AI payment solutions. The Monetization Gateway allows sellers to impose charges on AI agents for each API request, tool utilization, dataset access, or website interaction.
Currently, this service is in a closed beta and available exclusively to sellers and buyers operating within the United States.
Another product, Pay Per Use, is in beta as well and aims to financially compensate publishers when an AI entity acknowledges the use of their content post-retrieval.
Cloudflare first introduced the Marketplace Gateway on July 1, subsequently launching a waitlist for interested participants.
In my previous analysis dated September 18 regarding AI content monetization frameworks, I referenced Cloudflare’s July announcement of Pay Per Use as an exploratory venture.
This Gateway grants sellers the autonomy to select which requests incur fees and the pricing structure tied to them.
In contrast, in the Pay Per Use model, the AI organization dictates usage parameters and pricing, leaving publishers the choice to accept or reject the offer.
Monetization Gateway: Charges on Each Request
With the Monetization Gateway, sellers impose fees for every request initiated by an AI agent; the seller determines the pricing.
As highlighted in Cloudflare’s official communication, this system is tailored for resources that necessitate transactional engagement with each request, including tools, APIs, and data feeds.
The Gateway operates via the x402 protocol alongside the HTTP 402 Payment Required status code. When an agent seeks access to a secured resource, payment terms are presented, and authorization must be provided prior to re-attempting the request.
Payment processing occurs concurrently with the request and is authenticated before the seller’s server can issue a response, as detailed in the documentation.
Each set of regulations delineates domain specifications, URLs, pricing, and audience targeting, with elaboration available on the monetization rules page. The targeted audience may encompass a broad segment, or solely verified bots recognized by Cloudflare’s BotBase.
Fixed pricing models ensure uniform costs for requests with predetermined inputs, while variable pricing establishes a ceiling.
For variable pricing, the seller’s origin reports the actual amount charged, with settlements starting from $0.001 and peaking at $100.
Payments are executed using the USDC stablecoin on the Base blockchain via the x402 Facilitator by Coinbase. Plans have been shared to incorporate an array of additional payment modalities in the future.
Current Eligibility for the Gateway
The Gateway remains in a closed beta state, and according to the eligibility criteria, both buyers and sellers must be based in the United States.
Sellers are required to maintain a credit card on file, a verified email account, and an account older than 60 days.
Furthermore, the domain must be proxied through Cloudflare for over 30 days and must pass security evaluations. Sellers have the option to request access through the dashboard.
Four Active Deployments by Cloudflare
Cloudflare identifies four existing live implementations, one of which is its proprietary AI Gateway.
Ceramic.ai offers a web search API catering to agents, with fixed pay-per-search rates necessitating no API key acquisition.
Cloudflare previously highlighted Ceramic in July as a Pay Per Use collaborator, compensating content providers whenever their material surfaces in search results. Within the Gateway framework, Ceramic assumes the role of the seller.
The AI Gateway accepts remuneration per inference request across four publicly accessible models for users in the U.S., as elaborated in its documentation.
Stocktwits levies charges for each market signal request delivered through a designated access route for agents.
API2PDF presents a PDF generation API characterized by variable pricing that corresponds to compute and bandwidth exerted per request.
Reports indicate that API2PDF witnessed a greater than 50% dip in conversion when it began requiring a credit card from customers post the initial month.
Understanding Pay Per Use
Cloudflare’s Pay Per Use explanation elucidates that Pay Per Crawl “incurs charges for access,” while Pay Per Use “remunerates for subsequent actions,” such as delivering a referenced answer in AI-driven searches.
The delineation of roles within this framework is as follows:
Every AI company establishes the usage they will financially compensate for, determining a price accordingly.
Publishers select the offers they deem acceptable, gaining insight into their content’s usage frequency and revenue generation. Cloudflare manages enrollment, keeps utilization records, oversees billing, and facilitates payments.
Each program’s stipulations specify the permissible actions the AI company may take regarding the content, including potential restrictions on its application for training purposes.
The buyer is tasked with documenting each instance of usage, submitting a timestamp, the original URL, and an event ID.
Reporting on usage is self-reported, while regulations stipulate exhaustive documentation. Cloudflare ensures each reported usage corresponds with an enrolled publisher before proceeding with billing and distributing payments monthly.
Throughout the beta duration, Cloudflare is collaborating directly with buyers and participating publishers, without disclosing buyer identities.
Context of the September 18 Analysis
On September 18, my analysis juxtaposed the Pay Per Crawl alongside the Pay Per Use alternatives, incorporating insights from Google’s AI contribution initiative and Microsoft’s Publisher Content Marketplace.
With the inclusion of the Gateway, Cloudflare’s spectrum has expanded to three distinct transactional events.
Pay Per Crawl registers a fee for each successful paid retrieval, as dictated by the site owner’s rate. The Gateway ritualistically charges per request at a seller-defined rate.
Meanwhile, the Pay Per Use structure rewards for each reported instance at a price set forth by the AI entity.
Significance of These Developments
For publishers utilizing Cloudflare, the Pay Per Use model signifies that the AI entities define both the usage parameters and the associated costs.
As a seller, one retains the discretion of accepting or declining offers, with the usage data impacting earnings sourced from the buyer’s reporting.
A U.S.-based vendor providing an API, MCP tool, or dataset attains control over request-specific pricing upon entry into the Gateway’s closed beta.
Neither Cloudflare’s Gateway release nor its Pay Per Use update discloses transaction volumes or payout figures.
Future Prospects
Cloudflare asserts that the Pay Per Use beta will assist in refining mechanisms that allow publishers to negotiate buyer pricing and establish differentiated charging based on varied usages.
Anticipate updates regarding the identification of AI companies engaging in transactions via Pay Per Use. For the Gateway, Cloudflare asserts that geographic support expansion is “on the horizon.”
Source link: Searchenginejournal.com.
