How long-running jobs work.

Some tools — full articles, audits, AI-visibility checks and briefs — take longer than a chat reply. They hand your assistant a ticket and finish in the background, and the assistant checks back for the result.

Why some tools run as jobs

A full article, an audit or an AI-visibility run can take a minute or more — longer than most assistants will wait for a single tool reply. Rather than time out and leave you with nothing, these tools return immediately with a job ticket and do the real work in the background. Your assistant gets a way to check back, and the run finishes on its own.

How it works

1

You ask for the work

You ask for the article, audit or check. The run tool starts the work in the background and returns a job ID straight away, so nothing hangs waiting.

2

The assistant checks status

Your assistant calls get_job with that ID to see where things stand — queued, running, done or failed. This poll is free and works with any job.

3

The result comes back

When the job is done, get_job returns the finished result — the article, the audit, the check — and your assistant shows it to you.

You don't manage this by hand. A capable assistant polls and reports back on its own, so you usually just wait a moment for the answer. If it seems to pause, you can also ask "is that audit done yet?" and it will re-check.

Which tools are jobs

Most tools return their result directly. These are the ones that run as background jobs:

  • generate_blog_article — write a full long-form article.
  • run_ai_visibility_check — run an AI-visibility check across your prompts.
  • run_seo_audit — run an SEO audit for a brand.
  • run_site_ai_audit — run a site AI-visibility audit.
  • generate_daily_brief — build a fresh daily brief.
  • run_competitor_analysis — add and analyse a competitor.

get_job is the free poll that works with any of them. Everything else returns its result the moment you ask.

When you're charged

Credits are charged after the job succeeds, never on the ticket. If a run finds nothing to do — for example an AI-visibility run where no answers came back — nothing is charged. This mirrors the app exactly, so what you pay through your assistant matches what you'd pay in ScoutRival. Your first SEO or site audit per brand is free. See credits and pricing for what each tool costs.

// IF YOUR ASSISTANT SEEMS TO STOP

If your assistant appears to go quiet after starting an audit or an article, it is usually just waiting on the job. Ask it to check the job status, or wait a moment and ask for the result.

Limits and results

To keep things responsive, there's a small cap on how many jobs run at once per account — a handful in parallel. Extra requests wait their turn rather than piling up. A job's result is kept so your assistant can fetch it with get_job after the work finishes; if you lose the thread, ask again and it can re-check by ID and hand you the result.

Still stuck?
Contact support