The Agent That Signed Up and Paid for Its Own Analytics

This morning I shipped vigie, agent-first web analytics. Tonight an agent became its first self-serve customer — it discovered the API, created an account, hit the free quota, and paid for more with its own wallet. No signup form, no credit-card modal, no human on either side. What follows is the actual transcript against the production instance.

1. Discovery

Everything an agent needs is in the service's own llms.txt:

$ curl -s https://vigie.intrane.fr/llms.txt | tail -6

HOSTED SELF-SERVE (this instance):
  1. POST /v1/signup {"email":"you@x.com","org":"my-org"} -> org Bearer token (shown once) + 10k free events/mo
  2. POST /api/sites?domain=your-site.com (Bearer) -> register; GET /v1/org/sites -> read keys for /report + /globe
  3. Over quota -> HTTP 402 with a peage pay pointer: fund a wallet, POST /v1/org/wallet, retry.
  4. GET /v1/org/quota anytime (solvency preflight).

2. Signup — one POST, token shown once

$ curl -s -X POST https://vigie.intrane.fr/v1/signup \
    -d '{"email":"agent-demo@intrane.fr","org":"demo-agent"}'
{
  "ok": true,
  "org": "demo-agent",
  "token": "vo_[redacted — shown once, stored by the agent]",
  "free_events_per_month": 10000,
  "next": ["POST /api/sites?domain=... to register a site", "..."]
}

Rate-limited per IP, org names validated, the free tier is the entire blast radius of an unverified signup. The response body is the onboarding doc.

3. Work happens, then the wall

The agent registers its site and instruments its service (for this demo I set the org's plan to 25 free events and a 2-cent block so we hit the wall quickly — production defaults are 10k free and €1 per 100k). Event 26:

$ curl -s -X POST https://vigie.intrane.fr/api/event -d '{"site":"demo-agent.app","t":"event","name":"api-call",...}'
{"ok":false,"error":"monthly event quota exceeded","org":2,
 "pay":{"rail":"peage","url":"https://peage.intrane.fr",
        "price_cents":2,"per_events":100000,
        "how":"fund a peage wallet, then POST /v1/org/wallet {wallet_token} with your org Bearer token"}}
HTTP 402

This is the part I care about. A classic SaaS answers this moment with an email to a human. vigie answers with a machine-readable HTTP 402 that names the rail, the price, and the exact call to make. The error is the payment UI.

4. The agent pays

The agent already holds a prepaid péage wallet (funded once by a human via a Stripe link — the human's last appearance in this story). It links the wallet and retries:

$ curl -s -X POST -H "Authorization: Bearer $ORG_TOKEN" \
    https://vigie.intrane.fr/v1/org/wallet -d '{"wallet_token":"pw_..."}'
{"ok":true,"wallet_linked":true,"note":"over-quota ingest now charges this wallet per 100000-event block"}

$ # retry:
{"ok":true}
HTTP 200

$ curl -s -H "Authorization: Bearer $ORG_TOKEN" https://vigie.intrane.fr/v1/org/quota
{"ok":true, "events_used":26, "free_events":25, "charged_blocks":1,
 "remaining_before_charge":99999, "wallet_linked":true, ...}

On the péage side, the receipt is real and publicly verifiable: charge c_0f3e9ce72c94..., 2 cents, memo vigie: 100000 events (2026-07), merchant m_553d7fe31a93. Actual money moved on the live rail while the retry loop ran.

Why this matters more than the analytics

The loop that just closed — discover → sign up → work → hit a paywall → read it → pay → continue — ran with zero human involvement and zero web pages. Every step was a curl an LLM can compose from the service's own documentation. That's the actual thesis of the agent-web stack: péage pays, relais receives, portier authenticates, and vigie watches — each one a small binary speaking JSON, each one operable by the things that actually operate software now.

The wallet model keeps it safe: prepaid only, per-charge and per-merchant daily caps, so a rogue merchant can't drain an agent and a rogue agent can't spend what its human didn't fund. And the free tier means signup abuse buys an attacker nothing but 10k anonymous pageview counts.

vigie's self-serve endpoints (/v1/signup, /v1/org/wallet, /v1/org/quota, /v1/org/sites) are live now. If your agent wants analytics, point it at vigie.intrane.fr/llms.txt and get out of its way.