What do I need before it runs?

Your product URL, and a model. The URL gets you the overview and your first X post on our model. After that the engine drafts on a model you connect: Claude Code from your terminal, or an API key of your own (Anthropic or Kimi), verified live when you save it and stored encrypted, decrypted only at the moment of use. Until one is connected the engine stays dark by design: nothing fires and no placeholder content is generated.

Do I need an API key?

No. Connect Claude Code instead and the drafting, research and critique run in your terminal on your subscription; the project keeps the plan, the queue, the checks and the audit log, and every result lands on the same dashboard. Add a key as well and the engine keeps the queue full between your sessions.

Which model does it use?

Your choice per project: Anthropic (Claude Sonnet 5) or Kimi (kimi-k2.6, with research on kimi-k3), each on your own key. You can keep a key for both and switch without pasting again. Our own model is used for exactly two calls, both during setup: the overview of your site and your first X post.

Does it post to my accounts?

Not unless you let it. By default you approve and you post — the email includes a pre-filled composer link so it takes seconds. Per action you can grant a veto window from day one, and where marketinque posts through an API (your blog, Bluesky, dev.to, your Discord) an action can run on its own once it has earned 5 clean approvals; one veto takes that back. Email to your own list earns the same way, and a bounce or complaint spike sends it straight back to asking. LinkedIn and X you always post yourself, cold outreach asks, and spend always asks.

How does it decide what to work on?

Your active goal is the master dial. Every project starts with a default awareness goal you can edit; the strategist re-plans each cycle against that goal, your live metrics, what has already shipped, and the recorded outcomes — so the plan improves as the loop learns.

What happens to weak ideas?

They are culled before they reach you, and the cull is logged so the stats stay honest. The floors are enforced in code: confidence or impact below 4 of 10, an unsupported factual claim, or too much similarity to a recent idea all end a draft. When drafts compete, critic-passing losers are logged as outranked — you only ever see the winner.

How does the learning actually work?

You are never asked to rate anything. The engine learns from the decisions you already make — every approve and reject is a judgement on the idea — and from tracked-link clicks on what you post, which resolve into a lower-weighted verdict on their own. Both aggregate into a per-type track record, and distilled lessons are embedded in memory and recalled, with their dates, the next time they are relevant.

How much of my attention does it cost?

About a minute per idea, by design: every card carries its evidence, score, and steps so you can decide fast. The critic culls the weak ideas, the engine holds new proposals while your approval queue is deep, and digest mode batches everything into one daily email if you prefer.

how it works

An engine that shows its work

One loop takes your product from a self-written brand brief to researched, claim-checked ideas on your dashboard — and it sharpens every time you say what worked. This page walks it end to end: how it starts, where the model comes from, what runs on its own, and what waits for you.

Two steps to a running engine

step 01

Paste your URL

The engine reads your site and writes a short overview for you to check: what the product is, who it is for, why buyers pick it. Save it and your first X post is drafted in the background, so something real is waiting on the dashboard before you have connected anything. Those two calls run on our model; they are the only two we pay for.

step 02

Connect a model (or skip it)

Claude Code from your terminal, an API key of your own (Anthropic or Kimi), or both. Each connection is checked live: the key is tested before it is saved, and the Claude Code panel watches for the first call so you know the paste worked. Skip it and the first post is still yours to review; nothing else drafts until a model is connected.

Two ways to run it

The engine holds the plan, the queue, the checks and the log. The model can be yours in either of two places, or both.

Claude Code · MCP

From your terminal

Connect the project to Claude Code with one line. You run slash commands; it researches, drafts, critiques and fills in directory forms on your subscription, and records every step here. No API bill. Every decision, and every post, is still yours.

An API key · Anthropic or Kimi

On its own

Save a key and the engine runs the loop below on a schedule: a strategist plans, ideas are researched and critiqued, and each survivor waits for your approval, or for the rule you set for that kind of action. You pick the provider; the key you chose is the key that pays, on the model you chose it for.

Both at once is the full setup: the engine keeps the queue full between sessions and your terminal takes the work that needs a person at the keyboard. How the Claude Code connection works.

The loop, end to end

01 · the engine

It briefs itself before it drafts

The moment your project has a model, the engine researches your brand with live web search and writes its own brief: who the product is for, the pains that make them buy, where those people already gather, how you are positioned, and what genuinely sets you apart. On Claude Code the same brief is one command. Every later step — planning, drafting, judging — grounds on this analysis.

02 · the engine

A strategist plans every cycle

Nothing is drafted at random. Each cycle the strategist reads your active goal (awareness by default — the goal is the master dial), your live metrics, everything already shipped, and what the loop has learned, then emits a plan: which ideas to pursue and why. It skips channels with fresh work, caps its own load, and holds new proposals while your queue is deep — a quiet week costs almost nothing.

03 · the engine

Ideas are researched, not imagined

For each planned idea the engine reads the open web and returns a structured proposal: ready-to-post content, the real target — the actual subreddit, publication, event, or directory, with its rules — candidate partners with public links, execution steps, a success metric, and every source it read. Before writing a word, it recalls the lessons and proven plays most relevant to this exact idea.

04 · the engine

A critic tries to kill it

A second agent judges every draft before it may cost you attention. It fetches the cited pages and checks each factual claim against the text it finds there; judges brand fit against the brief; culls anything too similar to an idea from the last 90 days; and scores confidence, impact, and effort. Drafts compete in parallel and only the winner survives. If the critic itself cannot run, the draft is culled — the gate fails closed, never open.

05 · the gateway

One gate decides what leaves

Every action passes a single gateway that looks up its risk class in the policy engine. Drafts run on autopilot, because a draft cannot hurt you. Every publish, send, and dollar of spend stops and waits for your say-so: a yes on each item, or the veto window or earned autonomy you granted that kind of action. Spend always waits for a yes. Spam, fake reviews, and mass DMs are BLOCK-classed — no execution path exists. Every decision is appended to a hash-chained, append-only log the database re-verifies.

06 · you

You approve in about a minute

Each surviving idea lands at the top of your dashboard as one card — the content, its sources, the claim ledger, the score, the steps — and, if you gave an address, in your inbox with single-use approve and reject links and a pre-filled composer for the target platform. You make the call, and you do the posting. Prefer batches? Digest mode collects the day into one email.

07 · you + the engine

Your verdict trains the next cycle

The engine learns from the decisions you already make. Every approve and reject builds a per-type track record that steers what gets proposed next; the lesson lands in semantic memory and is recalled, with its date, when it next applies. Reversible actions on your own surfaces can earn autopilot after 5 consecutive clean approvals — and lose it the moment you veto one.

The gate, in depth

The banned-action registry, the schema constraints that make staked-plus-autopilot unrepresentable, and a live hash-chain verification — rendered from the running database on the trust page.

What runs without you, preset by preset

Every project starts on Cautious. A preset sets many actions at once, you can still change any single one, and none of them raises a gate: money always asks, and the forbidden never runs.

Cautious

Every publish, send and spend waits for your yes. The default for every project.

Drafting, research, claim checks, plan steps ticked from evidence: Runs on its own
Publishing to your blog: Asks you
Posts to Bluesky, dev.to and your Discord: Asks you
LinkedIn and X posts: Asks you; you post
Directory, Product Hunt and G2 submissions: Asks you; you submit
SEO fixes and site experiments: Asks you; you apply
Email to your own list: Asks you
Outreach: cold email, DMs, pitches, community replies: Asks you: no health sensor can see the damage yet
Ad spend and payouts: Always asks
Spam, fake reviews, mass DMs, vote manipulation: Never runs
Kill switches, the audit log, the daily report of what went: On

Balanced

Posts and publishes go out after a 24-hour window you can cancel, and email to your own list joins them once it has earned it and its health sensor is clean; cold outreach and spend still ask.

Drafting, research, claim checks, plan steps ticked from evidence: Runs on its own
Publishing to your blog: Goes out after a 24h window unless you cancel
Posts to Bluesky, dev.to and your Discord: Goes out after a 24h window unless you cancel
LinkedIn and X posts: Approved after a 24h window unless you cancel; you post
Directory, Product Hunt and G2 submissions: Approved after a 24h window unless you cancel; you submit
SEO fixes and site experiments: Approved after a 24h window unless you cancel; you apply
Email to your own list: Goes out after a 24h window unless you cancel once earned, while bounces and complaints stay low; until then, asks you
Outreach: cold email, DMs, pitches, community replies: Asks you: no health sensor can see the damage yet
Ad spend and payouts: Always asks
Spam, fake reviews, mass DMs, vote manipulation: Never runs
Kill switches, the audit log, the daily report of what went: On

Hands-off

Anything that has earned it and posts through an API runs on its own, email to your list included while its health sensor is clean; the rest of the posts go out after a 12-hour window; cold outreach and spend still ask.

Drafting, research, claim checks, plan steps ticked from evidence: Runs on its own
Publishing to your blog: Runs on its own once earned; until then, goes out after a 12h window unless you cancel
Posts to Bluesky, dev.to and your Discord: Runs on its own once earned; until then, goes out after a 12h window unless you cancel
LinkedIn and X posts: Approved after a 12h window unless you cancel; you post
Directory, Product Hunt and G2 submissions: Approved after a 12h window unless you cancel; you submit
SEO fixes and site experiments: Approved after a 12h window unless you cancel; you apply
Email to your own list: Runs on its own once earned, while bounces and complaints stay low; until then, asks you
Outreach: cold email, DMs, pitches, community replies: Asks you: no health sensor can see the damage yet
Ad spend and payouts: Always asks
Spam, fake reviews, mass DMs, vote manipulation: Never runs
Kill switches, the audit log, the daily report of what went: On

Capability	CautiousEvery publish, send and spend waits for your yes. The default for every project.	BalancedPosts and publishes go out after a 24-hour window you can cancel, and email to your own list joins them once it has earned it and its health sensor is clean; cold outreach and spend still ask.	Hands-offAnything that has earned it and posts through an API runs on its own, email to your list included while its health sensor is clean; the rest of the posts go out after a 12-hour window; cold outreach and spend still ask.
Drafting, research, claim checks, plan steps ticked from evidence	Runs on its own	Runs on its own	Runs on its own
Publishing to your blog	Asks you	Goes out after a 24h window unless you cancel	Runs on its own once earned; until then, goes out after a 12h window unless you cancel
Posts to Bluesky, dev.to and your Discord	Asks you	Goes out after a 24h window unless you cancel	Runs on its own once earned; until then, goes out after a 12h window unless you cancel
LinkedIn and X posts	Asks you; you post	Approved after a 24h window unless you cancel; you post	Approved after a 12h window unless you cancel; you post
Directory, Product Hunt and G2 submissions	Asks you; you submit	Approved after a 24h window unless you cancel; you submit	Approved after a 12h window unless you cancel; you submit
SEO fixes and site experiments	Asks you; you apply	Approved after a 24h window unless you cancel; you apply	Approved after a 12h window unless you cancel; you apply
Email to your own list	Asks you	Goes out after a 24h window unless you cancel once earned, while bounces and complaints stay low; until then, asks you	Runs on its own once earned, while bounces and complaints stay low; until then, asks you
Outreach: cold email, DMs, pitches, community replies	Asks you: no health sensor can see the damage yet	Asks you: no health sensor can see the damage yet	Asks you: no health sensor can see the damage yet
Ad spend and payouts	Always asks	Always asks	Always asks
Spam, fake reviews, mass DMs, vote manipulation	Never runs	Never runs	Never runs
Kill switches, the audit log, the daily report of what went	On	On	On

“Once earned” means 5 clean approvals in a row, and it is only offered where marketinque itself sends. Cancelling one item in its window sets that action back to asking. The rules, the banned list and the live audit chain are on the trust page.

One idea, fully argued

Every surviving idea arrives as one card: the content, the real target, the evidence, the score, and the steps. The same card renders in the email, the approvals queue, and the action page.

New idea · Reddit / community postconfidence 7 · impact 6 · effort 2

Answer the “first 100 users” thread in r/SaaS with your onboarding playbook

why now: the thread is six hours old and still climbing

targetr/SaaS — rules checked: no bare links, context required

Draft included — 240 words, written in your voice, ready to paste.

claim check

“Founders report first users from communities” — supported, quote on file
“Rule 4 allows self-promo with context” — supported, quote on file
“Thread ranks top-5 this week” — unverifiable, labeled instead of hidden

steps

Read the thread and the subreddit rules (linked).
Post the reply from the pre-filled composer.
Answer follow-up comments within the hour.

track record — reddit ideas so far: 4 shipped · 2 solid · 1 banger

ApproveRejectOpen pre-filled composersingle-use signed links

An illustrative idea — the blocks are the product’s real card anatomy, the numbers are what a real card carries.

It shows its work

Every factual claim is checked against a fetched copy of its cited source. An unsupported claim caps the score below the cull floor in code, and an unverifiable one is labeled — never hidden.

Trust at a glance

Confidence, impact, and effort out of ten, plus one line on why now. The floors are hard: below 4 on confidence or impact, the idea is culled instead of sent.

Your own track record

Each card carries how ideas of its type have actually performed for you, from your own verdicts — not somebody else’s benchmark.

A minute, not a meeting

Approve and reject are one tap from the email, and the composer opens pre-filled. Posting stays yours.

The numbers that govern it

channels in the catalog

Every one maps to a funnel stage and carries a policy row — there is no unclassified egress.

curated idea types

From SEO articles to event sponsorships. Each maps to exactly one gateway action, so approval and audit apply unchanged.

drafts per tournament

Parallel drafts compete, the critic scores them all, and only the winner reaches your inbox. Losers are logged, not lost.

4 / 10

the cull floor

Confidence or impact below it and the idea is culled in code, whatever the model’s verdict says.

93%

the novelty gate

More similar than this to any idea from the last 90 days? Culled. Measured in embedding space — it cannot be talked out of it.

clean approvals to run on its own

Only where marketinque itself sends. A veto window needs no streak, and one veto inside a window sends the action back to asking.

These constants are imported into this page from the same package the worker runs — when the engine changes, this page changes with it.

The mechanism, asked directly

What do I need before it runs?: Your product URL, and a model. The URL gets you the overview and your first X post on our model. After that the engine drafts on a model you connect: Claude Code from your terminal, or an API key of your own (Anthropic or Kimi), verified live when you save it and stored encrypted, decrypted only at the moment of use. Until one is connected the engine stays dark by design: nothing fires and no placeholder content is generated.
Do I need an API key?: No. Connect Claude Code instead and the drafting, research and critique run in your terminal on your subscription; the project keeps the plan, the queue, the checks and the audit log, and every result lands on the same dashboard. Add a key as well and the engine keeps the queue full between your sessions.
Which model does it use?: Your choice per project: Anthropic (Claude Sonnet 5) or Kimi (kimi-k2.6, with research on kimi-k3), each on your own key. You can keep a key for both and switch without pasting again. Our own model is used for exactly two calls, both during setup: the overview of your site and your first X post.
Does it post to my accounts?: Not unless you let it. By default you approve and you post — the email includes a pre-filled composer link so it takes seconds. Per action you can grant a veto window from day one, and where marketinque posts through an API (your blog, Bluesky, dev.to, your Discord) an action can run on its own once it has earned 5 clean approvals; one veto takes that back. Email to your own list earns the same way, and a bounce or complaint spike sends it straight back to asking. LinkedIn and X you always post yourself, cold outreach asks, and spend always asks.
How does it decide what to work on?: Your active goal is the master dial. Every project starts with a default awareness goal you can edit; the strategist re-plans each cycle against that goal, your live metrics, what has already shipped, and the recorded outcomes — so the plan improves as the loop learns.
What happens to weak ideas?: They are culled before they reach you, and the cull is logged so the stats stay honest. The floors are enforced in code: confidence or impact below 4 of 10, an unsupported factual claim, or too much similarity to a recent idea all end a draft. When drafts compete, critic-passing losers are logged as outranked — you only ever see the winner.
How does the learning actually work?: You are never asked to rate anything. The engine learns from the decisions you already make — every approve and reject is a judgement on the idea — and from tracked-link clicks on what you post, which resolve into a lower-weighted verdict on their own. Both aggregate into a per-type track record, and distilled lessons are embedded in memory and recalled, with their dates, the next time they are relevant.
How much of my attention does it cost?: About a minute per idea, by design: every card carries its evidence, score, and steps so you can decide fast. The critic culls the weak ideas, the engine holds new proposals while your approval queue is deep, and digest mode batches everything into one daily email if you prefer.

See it run before you run it

This loop is not a roadmap — it is the production system marketing marketinque itself. The blog it drafts and its live metrics are public. Join the waitlist to point it at your funnel.