ONE CALL, ONE DRAFT, STRUCK FROM ORE
Your product speaks one verb to the Forge: generate. The engine researches across the mined items, checks the angle against everything you already published, and strikes a draft that knows both its sources and its own history.
THE SAME POST, WEARING DIFFERENT WORDS
Generic generation has two famous failures. The first is repetition: ask for content weekly and by week six you're publishing the same three ideas in rotation, because the model has no memory of what you already said. The second is integration pain: "AI content" usually means a chat window somewhere, a copy-paste, and a human courier moving text between systems by hand.
RESEARCH, ANGLE MEMORY, THEN THE HAMMER
One API call starts the cycle. The engine researches across the item database first — the strike works only mined ore. Then it consults angle memory: a per-client record of every angle already taken, so the new draft approaches from ground you haven't covered. The result arrives as a format your product renders directly — long-form MDX, a post, a rendered plate — not prose in a chat window.
→ POST /v1/generate { client: "…", format: "ARTICLE_MDX" }
… research across mined items · angle checked against your history …
← 202 { id: "ci_8f3a…", status: "awaiting_review" }Note the 202: a strike produces a draft, never a publication. What happens next belongs toStation 03.
WHAT A CLEAN STRIKE BUYS YOU
Angle memory per client
The engine remembers what you've argued before, per client, and steers new drafts away from it. Week fifty sounds as fresh as week one — structurally, not by luck.
Content as a systems call
Your product integrates one endpoint and receives finished formats. No chat window, no courier, no paste. Content becomes infrastructure your code can depend on.
The strike can't skip the ore
Research over mined items isn't a mode you enable — it's the only path through the engine. A draft with nothing under it doesn't get struck.
A generator is only as honest as what it is forced to touch on the way to an answer. The strike is designed so grounding and memory are load-bearing — remove either and the hammer simply doesn't fall.
WHY GENERATION IS A PIPELINE, NOT A PROMPT