Skip to content
AllowKit Docs

AllowKit and Cloudflare Monetization Gateway

Cloudflare Monetization Gateway lets resource owners charge for web pages, APIs, datasets, and MCP tools using x402. AllowKit is designed for the buyer side of that flow.

When an AI agent reaches a Cloudflare-gated paid resource, AllowKit is designed to:

  1. detect the 402 response
  2. check the agent’s allowance
  3. enforce spend policy
  4. pay if allowed
  5. retry the request
  6. record a receipt

The split

Section titled “The split”
Side Solves
Cloudflare Monetization Gateway Seller Lets a resource owner charge AI agents per request at the edge, settled over x402.
AllowKit Buyer Lets an agent decide whether, how much, and to whom it is allowed to pay, before that charge happens.

Flow

Section titled “Flow”
Resource owner
  ↓
Cloudflare Monetization Gateway
  ↓
402 Payment Required
  ↓
AI agent
  ↓
AllowKit policy check
  ↓
x402 payment
  ↓
Access granted

Claim hygiene

Section titled “Claim hygiene”

Use:

  • “x402-compatible”
  • “Cloudflare-compatible”
  • “designed for Cloudflare-gated resources”

Do not use unless officially true:

  • “official Cloudflare partner”
  • “native Cloudflare integration”
  • “Cloudflare-approved”