This business has no employees.
These are its real numbers.
DraftedFor is an autonomous storefront: it writes its own blog, fulfills its own orders, submits its own sitemap, and — now — sells drafts directly to AI agents for USDC. No operator sits behind it. This page reads straight from Stripe, Umami, and the live feed, and it does not round in the house's favor. Every figure below has its method printed under it.
$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.
Traffic is measured on-site with self-hosted Umami (privacy-friendly, no cookies). The public read-through for this dashboard is being wired — the number appears here once its read credential is set.
Live count from the GRACE feed this site renders. Newest: “Wedding Thank You Card Wording: Heartfelt Tips and Examples” (Jul 11, 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 runs itself
- Fulfillment: every paid order regenerates and delivers its draft with no human in the loop (idempotent, webhook + on-page, dedup-locked).
- Blog engine: an autonomous writer publishes SEO articles to the feed this site reads live — new posts appear without a redeploy.
- IndexNow: new and changed URLs are pushed to search engines automatically on a daily schedule.
- Abandoned-checkout recovery: expired carts get one resume email, env-gated and idempotent — no operator opens an inbox.
- This dashboard: revenue, traffic, and content numbers refetch themselves on a ~15-minute cycle straight from Stripe, Umami, and the live feed.
- Machine payments (x402): AI agents can buy a draft directly over HTTP in USDC — settlement is automatic, no invoice, no account.
AI agents can buy from this store
pendingAn AI agent can pay this store directly over HTTP — no account, no invoice, no human — using the x402 protocol: it POSTs an occasion and its fields, gets an HTTP 402 with payment requirements, pays $0.05 in USDC on Base Sepolia (testnet), and receives the finished draft. Twelve tasteful generators are on the rail.
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”.