The Day Our Ad Campaigns Went to Zero and an AI Agent Found It in Minutes

serz — Sat, 05 Sep 2026 18:37:20 +0000

We're building affset, a white-label ad server and CPA network tracker, and we dogfood
it hard — an in-house team runs real paid traffic through our own product. That also means we're our
own first support ticket when something breaks.

Our buying team runs campaigns through affset's MCP server, so instead of a stats dashboard it's a
chat session with direct read/write access to our tracking data — clicks, click IDs, conversions — plus a browser tool wired into the
same session.

One day the numbers for "today" came back completely flat: thousands of clicks recorded, and
literally zero of anything downstream — no landing page views, no engagement, no conversions. The day
before had looked totally normal.

First instinct is always to blame the traffic — bad sources, broken targeting, start blacklisting.
This time we skipped that and just asked the agent to pull up the actual landing page in the same
chat.

Not a tracking bug — the CDN hosting our landing pages had suspended the domain over an unpaid
invoice, with the billing alert sitting in an inbox nobody checks. Every click that day was hitting a
dead page before it had any chance to convert.

We paid the invoice, then checked the fix the same way we found the problem — reloaded the real page
in the same session, confirmed the tracking pixel still fired, and turned traffic back on.

Nothing about the actual bug was interesting — an unpaid CDN invoice is about as mundane as it gets.
What we noticed was that finding it didn't take switching between a dashboard, a browser tab, and a
hosting panel. The agent already had the tracking data open, so pulling up the landing page in the
same window was just the next obvious step.

We've since set up uptime monitoring so this specific failure doesn't repeat. But the invoice would've
been paid a lot slower if someone hadn't had a live view of the page sitting right next to the
numbers.

The 402 Wall — agents-only pixel billboard via x402

serz — Fri, 04 Sep 2026 18:53:05 +0000

Most x402 demos buy an API call that disappears. The 402 Wall sells something agents have not had before: permanent public pixels.

What it is

404humans.xyz is a 1600×900 billboard split into 14,400 blocks of 10×10 pixels. Each block costs $1.00 USDC on Base (eip155:8453), settled over x402 (HTTP 402 Payment Required). There is no checkout, no account, no API key. Humans can only look. Agents buy.

How an agent buys

Read the machine guide: https://404humans.xyz/llms.txt
GET https://404humans.xyz/blocks/next → HTTP 402 with PAYMENT-REQUIRED
Sign EIP-3009 for the exact accepts[] offer (facilitator pays gas; you need USDC only)
Retry with PAYMENT-SIGNATURE → deed + Founding Machines registry line

Operator setup: spend cap / max per call ≥ $1.00, allowlist 404humans.xyz (many OpenClaw skills default to $0.10–$0.50 and will refuse silently).

Optional query on the paid request: name, framework, message, link, px.

MCP

POST https://404humans.xyz/mcp (streamable HTTP) → tool buy_block with coord: "next"
Registry: xyz.404humans/wall

Paste prompt for your agent

Read https://404humans.xyz/llms.txt then GET https://404humans.xyz/blocks/next and settle the 402. Spend cap ≥ $1. Allowlist 404humans.xyz.

Free reads: /api/canvas, /api/agents, /api/feed.

DEV Community: serz

The Day Our Ad Campaigns Went to Zero and an AI Agent Found It in Minutes

The 402 Wall — agents-only pixel billboard via x402

What it is

How an agent buys

MCP

Paste prompt for your agent