Agentic passive income · engine room · automate
Agents run the pipelines now. The loops are code you can read. And every stream ships with its real maintenance floor printed on it — that's how you know we're not lying to you.
streams · recurringeducation · openrevenue events — always labeled
Agents cut build costs by roughly an order of magnitude and made maintenance schedulable — but every stream still has a labor floor, a latency to first dollar, and ways it dies. We print all three on every card, because streams picked on honest numbers survive and streams picked on vibes don't. Ratings are lifted straight from the knowledge base, dated and re-verified.
Evidence-led comparisons of tools you actually use, monetized by disclosed links through a registry you control.
dies by: Program terms change without notice — and the biggest AI vendors run no affiliate programs at all.
full mechanics in knowledge/01 →A structured dataset rendered into many honest pages. The moat is the dataset and its freshness, not the prose.
dies by: Thin programmatic output gets flattened; data rot cascades to every page at once.
full mechanics in knowledge/01 →Package decisions you have already made — templates, agent packs, kits — sold self-serve through a merchant of record.
dies by: Stale products refund and reputation-burn; distribution is the hard part, not the product.
full mechanics in knowledge/01 →A regularly shipped email in a tight niche; disclosed tool recommendations, then sponsorships. Semi-passive at best.
dies by: Churn outpacing growth; one bad shill costs a year of trust.
full mechanics in knowledge/01 →A deep evergreen how-to corpus in a niche you practice, kept current by a scheduled agent refresh loop.
dies by: Reads as generic AI content unless first-hand experience is visible on the page.
full mechanics in knowledge/01 →Agents compress the production pipeline around a human presence. The back catalog is the passive part.
dies by: Burnout — the cadence eats creators; platform policy shifts you do not control.
full mechanics in knowledge/01 →A small piece of software — increasingly an MCP server sold to the agent ecosystem itself — billed by usage or license.
dies by: Upstream API changes; a security incident you are not staffed for; one-person bus factor.
full mechanics in knowledge/01 →Your product line listed on Whop or Gumroad — trading take-rate for discovery. A second surface, not a first home.
dies by: Rented distribution: race-to-bottom pricing and fee changes you do not control.
full mechanics in knowledge/01 →Curated licensable assets — music, stock visuals, code — earning long-tail royalties. Curation and rights hygiene are the moat.
dies by: Platform AI-content policies change without notice; everyone owns the same generators.
full mechanics in knowledge/01 →A membership where agents run onboarding, digests, and moderation flags — and you show up. Members pay for presence.
dies by: Churn spiral the moment the founder disengages; a trust-damaged category.
full mechanics in knowledge/01 →Agent-generated designs flowing into POD products and KDP books; the platform prints, ships, and pays royalties.
dies by: Saturation is the defining condition; a single account ban erases the catalog.
full mechanics in knowledge/01 →The awesome-list → dataset → API ladder. Verification is the product; the data is worthless the day it goes stale.
dies by: Staleness is instant, total value destruction; scope creep beyond what you can verify.
full mechanics in knowledge/01 →THE SELECTOR'S THREE RULES — one stream at a time; every stream gets a kill criterion at selection (result X by date Y, or sunset); and if your honest hours are zero, buy index funds — every stream here has a maintenance floor, and we publish it.
Structured facts in, gated artifacts out, a human approval between the machine and the public. Streams 1, 2, 4, and 5 in the atlas all run on this anatomy — and this site's own pipeline is the reference implementation you can read.
Structured facts with provenance and dates. Prose is regenerable; the registry is the asset.
Agents draft from the registry. Every claim carries its evidence label: hands-on · source-verified · desk review.
Claims · disclosure · freshness · links. Machines catch mechanical failures before a human looks.
Output is a pull request, never a direct write. The diff is the review surface.
Non-negotiable. Agents build; a human gates publication. Reviews verdicts and taste, not typos.
Merge deploys. Provenance ships in public: generation date, evidence labels, review date.
Scheduled re-verification: stale facts flagged, affected artifacts regenerated, refresh PR opened.
the maintenance loop — the refresh pass feeds back into the gates. 2–6 hrs/month of human review, published honestly. That's the real price of “passive.”
Every loop, always: idempotent · capped · observable · gated — no loop earns direct publish rights, ever.
Full anatomy with build order: knowledge/02 — content engines · floors and cadences: knowledge/06 — maintenance
/api is a stream engineer in your terminal: five staged commands, four specialist agents, four skills — installable in Claude Code, portable to Codex, Gemini CLI, Cursor, and OpenCode. Every stage ends with a written artifact in yourrepo. Advice that lives only in a chat doesn't exist.
Every file carries last_verified frontmatter and a quarterly review cycle. Stale facts are bugs; the refresh loop files them. Free on GitHub, forever.
The machinery and education are free forever. The paid layer is depth and updates — sold self-serve, generous refunds, no calls. Access states below are rendered from reality: nothing says “buy” until checkout actually exists.
All 12 archetypes with honest mechanics — labor floors, latency, ceilings, failure modes — plus the full knowledge base and the /api pack. MIT, no email required.
Turn one body of expertise into a versioned asset manifest, six-month scenario, passivity vector, authority policy, and explicit stop conditions.
Every stream pack, plus each future one — a single purchase with permanent updates, sold self-serve through a merchant of record. No calls, no funnels.
NO INCOME PROMISES — we sell machinery and education, never outcomes. Every stream page states its labor floor. Some research links are commission links, always disclosed inline with a non-affiliate alternative named. Doctrine: knowledge/03 — affiliate systems.
Three properties, three stages of the same discipline — each with its own pack, knowledge base, and open repo. Start where your situation says, not where the marketing does.
The hub. Capability → offers → revenue systems, with an agent team doing the assembly. Start here from zero.
agenticincome.ai →You are here. Streams that run on inspectable loops — content engines, product lines, honest affiliate systems. Every maintenance floor published.
agenticpassiveincome.comThe sovereign wealth substrate: income architecture structurally decoupled from hours. A doctrine, not a funnel — your ledger stays local.
disruptivepassiveincome.com →Weekly: what changed in the agent landscape, one stream teardown, pack updates. Factual, dated, unsubscribe in one click.
This property assumes you already have work worth automating — skills, surfaces, or a first income. If you're starting from nothing, the hub builds the earning machine first; come back here when there's something to put on a loop.