Start here
Credits, prices and top-ups
What each AuditAE action costs, how to top up (in the app, in AEBOT chat or from an agent), how auto-refill works, and what happens when credit runs out.
On this page· 8 sections
AuditAE is fully pay-per-use. There's no subscription, no minimum monthly spend, and credits never expire. New personal accounts get a free first audit, no card required. Some new accounts also start with free credit, and others get their first top-up matched, up to $5; the Billing page shows which applies to yours.
What costs money
- Audit checks: priced by engine per prompt × engine cell — Perplexity 5¢, ChatGPT 7¢, Google AI Overviews 9¢, Gemini 12¢. Cache hits bill at full price.
- Keyword rank checks: $0.05 each — a live SERP read with AI Overview citation + 12-month volume trend (Traffic → Keywords, MCP
track_keywords, and AEBOTtrack_keyword/refresh_keyword_rank). One-time history backfill is $0.25 (charged only if past data exists). - DataForSEO research pulls: keyword research at $0.25 and content gap at $0.25; open-web mentions (Content Analysis) at $0.25; AI citations (LLM-mentions corpus) at up to $0.75 (5¢ per prompt found, at least $0.30). Each saves a report you keep. Platform detection and backlink authority on the Technical tab are free.
- Playbook rows: auto-generated for two flows — mentioned-only (your brand was named but a competitor's URL got the citation) and pure-loss (your brand wasn't mentioned at all). Each row carries a specific fix and the prompt to re-run after you ship it. Priced dynamically via Sonnet at the 10× tier — measured average ~12¢ per row, up to ~20¢ for long answers. A 10-check audit where no answer cites you lands around $1.65 for its playbook, rollup included. Regenerating an audit's playbook bills only the existing rows that come out different: a row whose answer and site haven't changed is reused without a new call, and a row that comes back the same is free. A lost answer that had no row yet is diagnosed too and billed as a new row.
- Audit-level rollup: on top of the per-prompt rows, AuditAE clusters the playbook into 1–3 "do this first" actions per audit (across both loss types). One Sonnet call at the 10× tier — measured average ~45¢ per audit.
- AEBOT turns: token-based (input + output) × Anthropic list price × the tier markup for the underlying model (Haiku 3× / Sonnet 10× / Opus 10×), rounded up to 1¢ minimum. AEBOT runs on Opus 5.5 (specialist delegations bill at Sonnet rates). Measured over 15 customer replies in the 30 days to 2026-10-01: median about $1.07, 90th percentile about $2.56, the largest $3.12. A saved report adds 25¢. Questions in the free Documentation mode cost nothing.
- Fix plans (
get_fix_plan): $0.50 per plan; the same request within 24 hours is free. See Apply a fix plan. - Competitor prompt mining (
mine_competitor_prompts): 5¢. - Citation sources (
find_citation_sources): 10¢ per site per day; the same call again, or another filter on the site that day, is free, and a call with nothing lost to read isn't billed. - SEO data over MCP:
get_serp5¢,get_domain_keywords10¢,get_competing_domains10¢,get_keyword_metrics10¢ andget_referring_domains20¢ per call; the same call again within 24 hours is free, and a call that returns nothing isn't billed. - Single-page technical audits (
run_technical_auditover MCP,POST /api/v1/technical): the first 3 different pages a day are free per workspace, then 2¢ a page; the same page again that day, or one that didn't load, is free. - Site crawls (Site Audit): 1¢ per 10 pages fetched, billed as the crawl runs: $1.00 for 1,000 pages, $10.00 for a 10,000-page site. The 174 checks, Site Health, the theme scores, the link, image and script checks (up to 5,000 per crawl), the HTTPS, TLS and llms.txt site checks, Core Web Vitals on up to 10 pages and reading the results (in the app, over MCP or REST) are included. A crawl that runs out of credit stops with what it has and is scored on those pages. Scheduled crawls (weekly or monthly) are free to set up; each run is billed the same way when it runs, and a run that finds the balance at zero pauses the schedule until you top up and resume it. The homepage technical audit on a site's Technical tab is free.
- Image optimization (
optimize_image, over MCP, in AEBOT orPOST /api/v1/images/optimize): 1¢ per 5 images optimized, rounded up per call: 1¢ for 1–5 images, 4¢ for 20. An image that saves under 10 KB or 10%, a skipped or failed image, and the same image with the same settings again within 24 hours are free. It shows on Billing as Image optimization. On a paired WordPress site,wp_optimize_mediareplaces the images in place: one WordPress write (5¢) plus 1¢ per 5 images replaced, only when at least one image is replaced;wp_restore_media(undo) is free. - WordPress writes: 5¢ per standard write, billed per write;
wp_design_pageis 25¢. Reads are free. See WordPress permissions. - Scheduled audits: each run bills its checks, its fix plan and a 25¢ saved report, only when it runs.
Every charge is billed per use and debited from your balance the moment it posts, so the balance pill in the top bar is always current. If your account started with free credit, it's the first row at the bottom of the Billing page's activity feed — that's where the starting balance came from.
Topping up
- Go to Billing.
- Pick an amount ($5–$1,000 per top-up; a $10 first top-up is suggested if you haven't paid before, or $5 when your first top-up is matched).
- Click Add credit. Stripe Checkout opens inline.
- Pay. Credit is added as soon as Stripe confirms the payment, usually before the page reloads.
Payments are in USD. When your balance drops below $3, the Overview shows a balance card: until your first purchase, while you have credit left, it points you to AEBOT to spend what you have (under $1.50, that's one more reply, then the top-up); otherwise it offers a top-up.
Top up from the AEBOT chat
AEBOT needs $1.50 of credit to start a reply (a reply is usually about $1–2); before your first purchase, any credit left under that still gets one more reply, and an account that starts with no credit adds some before AEBOT's first reply. If you're short, the chat shows the top-up right in the conversation. Pay there and AEBOT picks up where it stopped: it sends the message it was holding, or carries on with the reply that ran out of credit. A stop that comes after a reply had already finished resumes nothing: until your first purchase the reply offers Add $10 and keep going under it, and after that the message links to Billing. Fix buttons on your audits read Add credit, then ask AEBOT when your balance is too low, and take you through the same top-up.
Auto-refill
Auto-refill is offered after your first purchase. On Billing, click Turn on auto-refill and save a card. Then set:
- Refill amount: how much to add each time.
- When below: the balance that triggers a refill.
- Monthly cap: the most auto-refill may charge in a month.
When your balance drops below the threshold, we charge the saved card for the refill amount and email a Stripe receipt. Auto-refill pauses when it reaches the monthly cap (until next month, or until you raise the cap), when a charge is declined, or when a payment is disputed; the Billing page says which and how to switch it back on.
Let agents spend without asking
Turn on Let agents spend without asking on Billing, and connected agents can use your credit without checking with you on each paid call. The balance is the limit. Recurring runs such as monitor_citations still need your OK. Agents read it from get_balance as spend_approved.
Top-ups for agents
Agents working for you can check your balance and add credit. Over MCP: get_balance and create_top_up_link (returns a Stripe Checkout link for you to pay). get_balance also shows how much of today's free single-page technical audits is used, and when the credit won't cover one citation check and auto-refill is off, it suggests a top-up link. Over REST: GET /api/v1/billing and POST /api/v1/billing/top-up with { "amount_usd": 20 }, or add "shared_payment_token": "spt_…" to pay directly. Amounts run from $5 to $1,000. See Connect Claude, ChatGPT or Cursor and REST API and API keys.
An agent working without an account (an agent workspace on /api/mcp/pay) gets a claim_url from create_top_up_link as well. Opening it and signing up moves that workspace's sites, reports, monitors and API key into your account, and any credit left in it carries over to your balance. A new account gets the usual sign-up offer (a free first audit); signing in to an existing account adds nothing. See Agents without an account.
When credit runs out
- REST API: a paid call your balance can't cover returns HTTP 402 with a
top_upobject holding the exact call to make (a crawl too big for your balance returns the same shape, with the errorInsufficient credits for that page count.and the crawl's worst-case cost as the amount required):
{
"error": "Insufficient credits",
"balance_cents": 0,
"required_cents": 5,
"top_up": {
"method": "POST",
"url": "https://auditae.app/api/v1/billing/top-up",
"body": {
"amount_usd": 5
},
"min_usd": 5,
"max_usd": 1000,
"note": "Returns a Stripe Checkout URL. Give it to the account owner to pay; credit lands within seconds."
},
"top_up_url": "https://auditae.app/dashboard/billing"
}
An agent workspace's key that has never been funded answers HTTP 403 workspace_unfunded (with the same top_up object) on every REST route except GET /api/v1/billing and POST /api/v1/billing/top-up.
- Audits over the API or MCP: API + MCP calls run through the same metered audit pipeline as the dashboard: 5–12¢ per check depending on the engine (Perplexity 5¢, ChatGPT 7¢, Google AI Overviews 9¢, Gemini 12¢), debited from your credit balance. When the balance hits zero, in-flight audits return
partial: truewith the cells that did run. - AEBOT: if your balance is below $1.50 when a turn starts (after your first purchase, or at $0 before it), AEBOT refuses the request rather than running up debt. Until your first purchase you're never charged past $0, so you never start with a debt: a reply stops when your balance reaches $0, and with less than $1.50 left AEBOT still takes one more reply and charges no more than what you have. Top up to unlock again.
Limits & guardrails
- The free check (homepage and
/ai-brand-monitor) is limited to 1 run per IP per 24 hours and 50 free checks a day site-wide. - Each engine call has a 30–60 second limit; cells that time out are marked failed and not billed.
- AEBOT turns require ≥ $1.50 balance before starting (defensive floor). Until your first purchase, a reply also stops when your balance reaches $0, and any credit left under $1.50 still gets one more reply.
- Credits never expire and there's no refund clock.
Teams, bulk usage and invoicing
Bulk usage / fixed monthly spend. There is no seat plan and no volume discount — checks cost the same at any scale, and team seats are free at every level (invite your team; everyone spends from one balance). Teams are capped at 5 members by default — email support@auditae.app to raise it, still free. For a subscription-style setup, turn on auto-refill on Billing, set the refill amount to your monthly budget (up to $1,000) and the monthly cap to match: one card charge and one Stripe receipt a month. Above $500/month, email support@auditae.app for invoicing instead of card charges and a response-time SLA.
All public prices: Pricing.
Try it in AuditAE
Open BillingRelated docs
- Apply a fix plan and check it workedTurn an audit into exact edits, apply them on WordPress or any other site, ping the crawlers, and re-check whether AI engines now cite you.
- Connect Claude, ChatGPT, Codex, VS Code or Cursor to AuditAE (MCP)Connect Claude, ChatGPT, Claude Code, Codex, VS Code or Cursor to AuditAE's MCP server: sign in or use an API key. No-account agents use /api/mcp/pay.
- REST API and API keysRun AuditAE from your own code with an API key and the same credit balance as the dashboard. Endpoints, prices, 402 top-ups and rate limits.
- Using AEBOTAEBOT is the AI assistant that runs your AuditAE workspace from chat: what it can do, what a reply costs (about $1–2), WordPress permissions and free docs mode.
- Site Audit: crawl a site and read Site HealthCrawl up to 10,000 pages for 1¢ per 10 pages and get Site Health, 9 theme scores and 174 checks, each with why it matters and how to fix it.
Still stuck? Signed in, ask AEBOT in Documentation mode (free). Or email support@auditae.app.