MoltMentions
‹
01 / 06Six jobs
›
Use cases

AI search API use cases, step by step.Two customer journeys, from the first prompt to a weekly report.

Teams use the AI search API in two ways. Scenario 1 sends answers to your own S3 bucket or BigQuery and you build the reporting. Scenario 2 keeps answers in MoltMentions and uses its analytics, recommendations, Slack notifications and MCP.

Use cases

One API covers six jobs, from AEO and citation tracking to ChatGPT Ads monitoring.

01

AI visibility tracking

Where a brand is named, weekly.

02

Prompt research at scale

Prompts by persona, topic and market.

03

AEO and GEO reporting

One client report on share of voice.

04

Competitor analysis

Who AI names next to you.

05

ChatGPT Ads monitoring

Catch rivals who pay to appear.

06

Agents and assistants

Query the data from any AI agent.

At a glance

How does AI visibility tracking work with the AI search API?

Shared setupSteps 1 to 5, the same for both journeys
  1. 1Create a brand kit
  2. 2Build a set of prompts
  3. 3Test a few prompts in Live mode
  4. 4Review the output with a skill
  5. 5Iterate until the prompts are right
Scenario 1

Your own pipeline

Answers land in S3 or BigQuery. A skill builds the analytics wherever you need them.

  1. 6Create a destination for the output
  2. 7Schedule runs by tag in Claude
  3. 8Check the output
  4. 9Show the analytics in your app, Claude Artifacts, slide decks, billboards… anywhere
PlanWalletPay as you go
Scenario 2

Pre-built in MoltMentions

Answers stay in MoltMentions. Analytics, recommendations and alerts come built in.

  1. 6Use MoltMentions as the destination
  2. 7Create a schedule in MoltMentions
  3. 8Connect Slack for notifications
  4. 9Manage it all through MCP
PlanMonitorMonthly, by prompt volume
Customer experiences

Customer experiences:
how teams put the AI search API to work.

Scenario 1

Build an AI visibility product, or send a client weekly data

PlanWalletPay as you go

For teams building an AI visibility product and agencies that report to customers every week. You own the pipeline: answers land in your storage on a schedule, and your own page shows the trend. New to the idea? Read what AI visibility tracking is.

  1. 1Brand kit
  2. 2Promptstag + store
  3. ↻ repeat until right
    1. 3Live test
    2. 4Skill reviewClaude / ChatGPT
    3. 5Iteratedelete · update · create
  4. 6DestinationS3 · BigQuery
  5. 7Claude scheduleweekly · daily
  6. 8Check output
  7. 9Analytics anywherevia a skill
Steps 3 to 5 repeat until the prompts are right. Orange steps are specific to this scenario. Select a step to jump to it.
  1. Create a brand kit

    The brand kit describes the brand you track. Every prompt and run refers back to it, so set it up first.

  2. Build a set of prompts

    Use the Prompt creation library to generate the questions your buyers ask. Tag each prompt and store it, because tags decide what runs together later.

    • Generate from the Prompt creation library
    • Tag by topic, persona, intent and market
    • Store the set
    # 2. Generate prompts for a brand kit, then store them with tags
    POST /v1/prompts/generate
    { "brand_kit": "northwind", "topic": "client reporting",
      "persona": "agency owner", "count": 25 }

    Illustrative sample.

  3. Test a few prompts in Live mode

    Run a handful of prompts live and read the real answers before you schedule anything.

  4. Review the output with a skill

    Open the results in Claude or ChatGPT and let a skill review them, so you see which prompts return useful answers and which do not.

  5. Iterate until the prompts are right

    Use what the review found to tune the set. Repeat steps 3 to 5 until the answers match what your buyers ask.

    • Delete prompts
    • Update prompts
    • Create prompts
  6. Create a destination for the output

    Point the output at storage you own.

    • S3 bucket
    • BigQuery
    # 6. Register where runs are written
    POST /v1/destinations
    { "type": "bigquery", "dataset": "ai_visibility" }
    # → { "id": "dst_bq_01" }

    Illustrative sample.

  7. Schedule runs by tag in Claude

    Create a scheduled task in Claude that runs specific prompts by tag on a regular basis. Pass the destination with every run.

    • Weekly prompts: standard mode, results land 10 min to 1 hr later, destination passed
    • Daily prompts: destination passed as a parameter
    # 7. One call per cadence, e.g. run_prompts_by_tag(tags, destination)
    # Weekly, standard mode (delayed 10 min to 1 hr)
    run_prompts_by_tag(tags=["weekly"], destination="dst_s3_01")
    
    # Daily
    run_prompts_by_tag(tags=["daily"], destination="dst_bq_01")

    Illustrative sample.

  8. Check the output

    Open the S3 bucket or BigQuery table and confirm each scheduled run landed with its tags.

  9. Show the analytics in your app, Claude Artifacts, slide decks, billboards… anywhere

    Run a skill that reads the stored answers and puts the analytics wherever they are needed: your app, a Claude Artifact, a slide deck, even a billboard. Keep it current for your product or the client's weekly report.

Scenario 2

Use the pre-built AI Visibility Analytics and Recommendations

PlanMonitorMonthly, by prompt volume

For teams that want reporting without building a pipeline. Answers stay in MoltMentions, which runs the schedule, sends notifications and turns the answers into AI share of voice analytics and recommendations.

  1. 1Brand kit
  2. 2Promptstag + store
  3. ↻ repeat until right
    1. 3Live test
    2. 4Skill reviewClaude / ChatGPT
    3. 5Iteratedelete · update · create
  4. 6MoltMentionsas destination
  5. 7Schedulein MoltMentions
  6. 8Slacknotifications
  7. 9MCPmanage it all
Steps 3 to 5 repeat until the prompts are right. Orange steps are specific to this scenario. Select a step to jump to it.

Steps 1 to 5:
the same as Scenario 1

  1. 1. Create a brand kit
  2. 2. Build a set of prompts
  3. 3. Test a few prompts in Live mode
  4. 4. Review the output with a skill
  5. 5. Iterate until the prompts are right
  1. Use MoltMentions as the destination

    Skip the bucket. Runs are stored in MoltMentions, where the pre-built AI Visibility Analytics and Recommendations read them.

  2. Create a schedule in MoltMentions

    Set which prompts run and how often inside MoltMentions. No scheduled task to maintain.

  3. Connect Slack for notifications

    Send notifications to a Slack channel, so the team hears about changes without opening a dashboard.

  4. Manage it all through MCP

    Use the MoltMentions MCP server to manage visibility, reporting and recommendations from your AI assistant.

    # Claude Code. Then run /mcp in a session to sign in.
    claude mcp add --transport http --scope user Thrivestack \
      "https://api.app.thrivestack.ai/mcp"

    Illustrative sample.

Which journey fits

Pick the journey by where you want the answers to live.

Both journeys use the same brand kit, prompts and Live mode testing.
What you needScenario 1: your own pipelineScenario 2: pre-built in MoltMentions
Best forAI visibility products and agencies reporting weekly to clientsTeams that want analytics and recommendations ready to use
Steps 1 to 5Brand kit, prompts, Live test, skill review, iterateSame as Scenario 1
Where answers are storedYour S3 bucket or BigQueryMoltMentions
SchedulingA scheduled task in Claude, by tag: weekly in standard mode, dailyA schedule within MoltMentions
AnalyticsAnywhere a skill puts it: your app, Claude Artifacts, slide decksPre-built AI Visibility Analytics and Recommendations
Day-to-day controlAPI calls and skillsMCP server, with Slack notifications
PlanWallet: pay as you go, buy credits when you need themMonitor: monthly, priced by prompt volume
FAQ

AI search API use cases, explained.

Which plan does each AI search API use case use?

Scenario 1, your own pipeline, uses the Wallet plan: pay as you go, with credits you buy when you need them. Scenario 2, pre-built in MoltMentions, uses the Monitor plan: a monthly plan priced by prompt volume. See the pricing page for current launch pricing, which may change.

Which AI search API use case should I start with?

Start with Scenario 2 if you want reporting quickly: answers stay in MoltMentions, which runs the schedule, sends Slack notifications and gives analytics and recommendations. Pick Scenario 1 if you are building an AI visibility product or an agency report and need the answers in your own S3 bucket or BigQuery.

Are the first five steps the same in both journeys?

Yes. Both start by creating a brand kit, building and tagging prompts with the Prompt creation library, testing a few prompts in Live mode, reviewing the output with a skill in Claude or ChatGPT, and then deleting, updating or creating prompts until they are right.

What is standard mode in the AI search API?

Standard mode runs prompts with a delay: results arrive 10 minutes to 1 hour after the run. It suits prompts you track weekly, where an hour does not matter.

How do I send AI search API results to my own warehouse?

Create a destination for an S3 bucket or BigQuery, then pass it with each run, for example run_prompts_by_tag(tags, destination) from a scheduled task in Claude. Tool and endpoint names are illustrative.

Can I manage MoltMentions from an AI assistant?

Yes. Connect the MoltMentions MCP server to Claude, Claude Code or Cursor and manage visibility, reporting and recommendations from the assistant.

Get started

Run your first prompts on the AI search API today.

Create a brand kit, build a prompt set and test it in Live mode. Then choose the journey that fits.