The observed numbers,
including the zeroes.
DraftedFor automates its content feed and has code paths for paid fulfillment and machine payments. Code is not revenue, so this page separates what is observed, unavailable, pending, and live. Every figure below includes its method.
$0 so far — launched July 2026, and this page is the launch. When the first stranger (or the first agent) pays, this number moves by itself.
Gross from Stripe Checkout, paid sessions only, filtered strictly to DraftedFor products (metadata.product is a DraftedFor generator slug, or the literal “draftedfor”). The Stripe account is shared across the owner's projects; every other project's charge is excluded and never shown here. Scans up to the 2,500 most recent account sessions.
Gross from Stripe Checkout, paid sessions only, filtered strictly to DraftedFor products (metadata.product is a DraftedFor generator slug, or the literal “draftedfor”). The Stripe account is shared across the owner's projects; every other project's charge is excluded and never shown here. Scans up to the 2,500 most recent account sessions.
Self-hosted Umami analytics, last 30 days, this site's website ID. Read-only query, no third-party tracker.
Live count from the GRACE feed this site renders. Newest: “Five Minute Bedtime Stories for Toddlers” (Jul 16, 2026).
Number of URLs assembled into sitemap.xml at request time — generator landings, long-tail variants, free full-answer pages, topic hubs, and every published article.
Days since the public launch of the monetized storefront (2026-07-11). The underlying template engine and blog have been iterating since late May 2026 — this counter measures the store going public, not the first commit.
Time since this server container last started. It resets to zero on every deploy — shown as an honest liveness signal, not a cumulative record.
What is automated — and what is not yet proven
- Paid-order fulfillment is implemented through an idempotent webhook + confirmation-page path; no successful customer order has been observed yet.
- Blog engine: an autonomous writer publishes SEO articles to the feed this site reads live — new posts appear without a redeploy.
- Contact boundary: paid drafts and receipts are transactional; abandoned carts receive no automated reminder email.
- This dashboard attempts to refetch revenue, traffic, and content on a ~15-minute cycle; an unavailable source is shown as unavailable rather than estimated.
AI-agent payments are not live
pendingThe free schema catalog is readable, but the purchase endpoint returns HTTP 503 until a receiving wallet and live network are configured. The intended protocol is x402 protocol. When live, a POST receives HTTP 402 payment requirements before a paid retry. Current configured status: Base Sepolia (testnet) at $0.05 USDC for one editable draft. Twelve generator schemas are listed.
The rail is built and dark. Until the store's receiving wallet is funded and configured, the purchase endpoint returns HTTP 503 (“rail not yet activated”) and the catalog above stays readable. The same switch flips this badge to “live”.