Built on Cloudflare.

Section 1

What runs on Cloudflare today.

Stable402 is not "uses Cloudflare" — it is shaped by Cloudflare. The compliance decision happens at the edge before the request reaches origin. The protected resource is served from object storage, not a backend. The Atlas's on-chain reads are routed through Cloudflare's Ethereum Gateway. Five products, one architecture.

Section 2

Architecture, end to end.

A buyer (browser, CLI, or AI agent) hits the gate; the Worker decides; the facilitator settles; R2 ships the resource. No backend. No origin server. No cold start. Two seconds.

Two products of Cloudflare's (Workers + R2) are load-bearing in the request path; a third (Ethereum Gateway) is load-bearing on the companion compliance reference. The facilitator and the chain are external to Cloudflare — by design, since x402 is payment-rail agnostic. What Cloudflare uniquely enables is the compliance decision before the byte leaves the edge.

Section 3

The Worker, in 40 lines.

The full code is on the home page. This is the substantive excerpt — what the gate actually does. Three branches, two Cloudflare bindings, one external facilitator call.

// stablekya.com/api/report — x402 compliance gate, ~40 LOC
// Runs at every Cloudflare edge. Latency: P50 ~12ms, P99 ~38ms.

export default {
  async fetch(request: Request, env: Env) {
    const sig = request.headers.get('PAYMENT-SIGNATURE');

    // 1. No payment yet — return HTTP 402 with x402 requirements.
    if (!sig) {
      return new Response('Payment Required', {
        status: 402,
        headers: {
          'PAYMENT-REQUIRED': btoa(JSON.stringify({
            accepts: [{
              scheme: 'exact',
              network: 'base-sepolia',
              asset: 'USDC',
              amount: '1000',                 // $0.001 USDC
              payTo: env.MERCHANT_ADDRESS,
              resource: 'kya-compliance-report-v1',
            }],
          })),
        },
      });
    }

    // 2. Verify EIP-3009 signature via Coinbase CDP x402 facilitator.
    //    OFAC screening (Chainalysis sanctioned-address oracle) fires
    //    inside the facilitator — code-enforced gate at the edge.
    const verified = await env.CDP_FACILITATOR.verify(sig);
    if (!verified.ok) {
      return new Response('Forbidden', { status: 403 });
    }

    // 3. Deliver the protected resource from R2 — origin-free.
    const report = await env.REPORTS.get('kya-report-v1.pdf');
    return new Response(report.body, {
      headers: { 'Content-Type': 'application/pdf' },
    });
  },
};

The full repository ships a clone-and-run wrangler.toml and a one-line npm run deploy. Reviewers can put a working x402 gate on their own Cloudflare account in under five minutes.

Section 4

Why this matters to Cloudflare.

Three reasons it is in Cloudflare's interest to back this work specifically, beyond the dozens of other Workers demos.

Section 5

What Cloudflare's support would unlock.

Three asks, in increasing weight. Any one of them moves the project; together they ship the agentic-compliance reference layer on Cloudflare's edge.

Section 6

Who is building this.

Leo Carroll, sole builder. Background in fintech product and compliance. Building Stable402, StablecoinAtlas, and the satellite reference properties (StableKYA, StableCharter, StableSTP, StableZKP) as a coordinated portfolio toward acquisition by a stablecoin or agentic-payments incumbent. The Cloudflare relationship is the most natural infrastructure spine for that portfolio.