What exactly happens when Actuant “launches” my app?

An agent works through the launch checklist you'd otherwise do by hand: it writes your llms.txt, robots.txt and sitemap as a GitHub pull request, submits your app to 20 curated launch directories — filling each form live in a browser you can watch, and leaving the submit button to you. Anything that touches your code arrives as a pull request; nothing merges without your approval. Launch-copy drafting, analytics installed for you, and Stripe payments set up inside your app are on the roadmap, not shipped.

Does it work with my builder?

Yes. Actuant doesn't integrate with builders — it works on the app itself: the live URL, the GitHub repo, and your domain. If your app has a URL, Actuant can audit it; if it has a repo, Actuant can fix it. Lovable, Bolt, v0, Replit, Base44, Cursor, Claude Code, or hand-written all work the same way.

I've shipped five apps. Do I need five subscriptions?

No. One account covers your whole portfolio: the free plan covers 1 app, Launch covers 3, Portfolio is unlimited. Re-auditing an app you've already added is unlimited on every plan. The Signal dashboard that compares those apps side by side is still being built — today you get each app's audits, fixes and launch work in one place.

Will you spam directories with my half-finished app?

No. The audit runs first, and the agent only submits when your app clears the quality bar — that protects your launch and everyone else's. We maintain a curated list of directories that send real traffic, not a firehose of 400 link farms, and the agent never presses submit for you: it fills the form and hands the browser back.

What does the free plan actually include?

One app, unlimited re-audits of it, the full launch-readiness score and report with per-check fix guidance, and access to the MCP server for your coding agent. Agent runs are metered, and the free plan's usage is a one-time $5 of credit — roughly 16 deep audits — not a monthly allowance. Paid plans add a weekly usage allowance, monthly credit, and the agent doing the fixing and launching rather than just the diagnosing.

Can I share a report with someone else?

Not yet. Reports live in your dashboard behind your login today; public, shareable report links are on the roadmap. Anything on this site marked “coming soon” isn't built — we'd rather you buy the plan for what it does now.

Agents & MCP

MCP tools reference (all 13)

The complete Actuant MCP tool list: eight free tools (scan_app, get_scan, audit_app, get_audit, list_apps, scan_history, explain_check, get_account) and five plan-gated tools for the Launch and Portfolio plans.

Last updated 2026-07-19

Actuant exposes 13 tools. The eight free tools work the moment you're connected; the five plan-gated tools are always visible but the server rejects them with a clear plan_required error if your plan is too low.

Tool names are a contract and are deliberately unchanged, so scan_app and get_scan still run the single-page audit even though the product now calls it an audit everywhere else.

Ungated tools

Available on every plan. Two of them cover the single-page audit; two cover the whole-site audit.

Tool	Arguments	What it does
scan_app	{ url }	Run the single-page launch-readiness audit. ~20s; returns score, per-check findings, advice, and a report link.
get_scan	{ scanId }	Fetch any previous single-page audit's full report.
audit_app	{ url }	Start a whole-site audit: opens and tests every reachable page in a real browser. Runs for minutes, so it returns an auditId immediately.
get_audit	{ auditId }	Poll a site audit: status, a live browser-view link while it runs, per-page scores, and site-wide findings.
list_apps	{ }	The account's audited apps with the latest score per app.
scan_history	{ url?, limit? }	Past runs, newest first — how the score moved over time.
explain_check	{ check, host? }	Deep-dive on any check key: what it verifies, why it matters, how to fix it.
get_account	{ }	Plan, app usage vs limits, total runs, connected keys.

The whole-site audit (audit_app / get_audit)

scan_app grades one URL. audit_app crawls the site: it drives a real browser over every reachable page, scores each one, and reports the site-wide problems a single page can't show — broken links, dead assets, mixed content, orphan pages, runtime JavaScript errors, and inner pages that are weaker than the homepage.

Because a real-browser crawl takes minutes, audit_app returns an auditId and a reportUrl straight away and the crawl continues on a durable worker. Call get_audit with that id to poll. While the run is live, get_audit also returns a browserViewer URL — a full-screen view of the browser doing the crawl, worth handing to the person you're working for.

audit_app is metered

A whole-site audit is metered: it draws on your plan's weekly usage limit and then on usage credits. If the limit is exhausted, audit_app returns a message telling you to top up in Settings → Usage rather than starting a run. The single-page audit isn't metered this way.

Plan-gated tools

Tool	Plan	What it does
fix_app	Launch	Open a GitHub pull request that fixes a run's failing checks with additive files (llms.txt, robots.txt, sitemap.xml). Needs GitHub connected and the app mapped to a repo.
submit_directories	Launch	The curated 20-directory launch checklist for an audited app: submit links, why each matters, prefilled copy, and what's already submitted. Assisted — you send the submission.
get_signal	Launch	Traffic / sign-up / revenue signal across your apps. Not live yet — on a qualifying plan it answers `not_yet_available` until the engine ships.
monitor_ai_visibility	Portfolio	Track when AI answers (ChatGPT, Claude, Perplexity) start citing your app.

Valid check keys for explain_check — all 52 of them, generated from the audit engine: reachability, https-redirect, compression, http-version, redirect-chain, caching, hsts, csp, x-content-type, frame-guard, referrer-policy, permissions-policy, no-version-leak, security-txt, analytics, title-meta, canonical, meta-robots, title-length, desc-length, search-indexing, single-h1, heading-order, image-alt, internal-links, lang-attr, ai-visibility, ai-crawlers-allowed, ssr-content, semantic-landmarks, jsonld-present, org-schema, social-preview, og-complete, twitter-card, favicon, apple-touch-icon, manifest, doc-size, third-party, render-blocking, lazy-images, image-dimensions, mobile, theme-color, privacy-linked, terms-linked, footer-identity, contact-method, social-presence, payments, primary-cta.

If a tool returns plan_required, don't retry — the error names the plan and price to unlock it. The free plan covers one distinct app with unlimited re-runs.

Keep reading

Connect an agent

Step-by-step: add the Actuant MCP server to Claude Code, Cursor, VS Code, or Codex CLI, complete the OAuth sign-in, and verify all 13 tools are available.

API keys

For headless environments and CI where a browser can't open for OAuth, mint a manual bearer API key in Settings and pass it as an Authorization header to the Actuant MCP server.

Audit overview

Actuant scores any app URL 0–100 across 52 deterministic launch-readiness checks — delivery, security headers, analytics, SEO, AI-search visibility, structured data, social, performance, mobile, trust, and conversion. Here's every check and how it's weighted.