AI Keyword Data API
Keyword research for the LLM-search era, not the Google-search era.
Traditional keyword tools score by Google search volume — how many people type 'plumber Austin' into Google's box. But LLM search is different. Users ask conversational questions ('who is the best plumber in Austin'), and LLMs respond with synthesized answers citing sources. This endpoint returns keyword data tuned for AI workflows: AI search volume (how often the query appears in ChatGPT and other LLMs), conversational-pattern scoring, intent signals that matter to agents, and 12-month trends. Your agent doesn't just know the keyword — it knows how to find and rank keywords that actually drive AI traffic.
POST /v1/ai/keyword-data · 1 credit / 50 keywords
These prompts are the new AI keyword research workflow.
Connect Local SEO Data as an MCP server once (60 seconds, below). Then your agent runs AI-first research. Replace bracketed keywords or locations with your own.
Pull AI search volume for [my 200 target keywords] in [Denver, Charlotte, Phoenix]. Compare to traditional Google volume. Flag keywords with high AI volume but low Google volume — those are AI discovery opportunities.
Get AI keyword data for these seed keywords: [best plumber, emergency plumber, plumbing repair]. Show me which formulations appear conversational in LLM search (high intent signal) vs informational. Rank by likelihood to trigger AI Overview.
Pull 12-month AI keyword trends for [my 50 commercial keywords]. Flag any with month-over-month growth >30% — those are keywords gaining traction in AI before competitors notice.
Fetch AI search volume for [my keyword list] in [Denver, Austin, Atlanta]. Show me which markets have highest AI demand. Which location should I prioritize for AI-first content?
What you get back
Live response for a 3-keyword request. Real API data reflecting how keywords perform in ChatGPT, Claude, Gemini, and Perplexity search patterns.
{
"status": "success",
"credits_used": 1,
"data": {
"location": "Austin, Texas",
"total_keywords": 3,
"keywords": [
{
"keyword": "best plumber austin",
"ai_search_volume": 2400,
"intent_signals": {
"informational": 0.72,
"commercial": 0.28,
"navigational": 0.0
},
"conversational_score": 0.85,
"triggers_ai_overview": true,
"monthly_searches": [
{ "month": "2026-04", "ai_volume": 2400 },
{ "month": "2026-03", "ai_volume": 2200 },
{ "month": "2026-02", "ai_volume": 2100 },
{ "month": "2026-01", "ai_volume": 1900 }
]
},
{
"keyword": "who is the best plumber in austin",
"ai_search_volume": 1850,
"intent_signals": {
"informational": 0.88,
"commercial": 0.12,
"navigational": 0.0
},
"conversational_score": 0.92,
"triggers_ai_overview": true,
"monthly_searches": [
{ "month": "2026-04", "ai_volume": 1850 },
{ "month": "2026-03", "ai_volume": 1720 },
{ "month": "2026-02", "ai_volume": 1640 },
{ "month": "2026-01", "ai_volume": 1500 }
]
},
{
"keyword": "emergency plumber near me",
"ai_search_volume": 3200,
"intent_signals": {
"informational": 0.55,
"commercial": 0.45,
"navigational": 0.0
},
"conversational_score": 0.78,
"triggers_ai_overview": true,
"monthly_searches": [
{ "month": "2026-04", "ai_volume": 3200 },
{ "month": "2026-03", "ai_volume": 3100 },
{ "month": "2026-02", "ai_volume": 3400 },
{ "month": "2026-01", "ai_volume": 3050 }
]
}
]
}
}AI-specific signals your agent needs to rank in LLMs
How often keywords appear in LLM queries
Monthly counts of how often your keywords are searched in ChatGPT, Claude, Gemini, and Perplexity. Different from Google search volume — typically lower, but much more qualified traffic because LLM users ask complete questions, not fragments.
Informational, commercial, and navigational breakdown
The intent mix for each keyword as it appears in LLM queries. A keyword like 'best plumber austin' skews informational (0.72) because LLM users ask research questions, not transactional queries. Your agent ranks keywords by intent to match content strategy.
How likely the keyword appears in natural language
A 0-1 score indicating whether this keyword appears in conversational queries ('who is the best plumber in austin') vs keyword-fragments ('best plumber austin'). High scores = full-sentence questions = more likely to trigger AI Overviews.
Does this keyword generate AI-synthesized answers
Boolean flag showing whether the keyword triggers Google AI Overviews. Not all keywords do — informational queries dominate (72% of AI Overview-triggering keywords), while high-CPC commercial terms rarely get AI summaries. Know upfront whether your target keyword gets an Overview.
Monthly breakdown of AI search volume history
Historical AI search volume for the past 12 months. Detect seasonal patterns (emergency plumbing spikes in winter), month-over-month growth, or declining AI interest. Your agent flags emerging opportunities before competitors notice.
What agents ship with this endpoint
Content prioritization for AI discovery
Before writing a blog post, pull AI keyword data for 50 candidate topics. Your agent ranks by AI search volume, conversational score, and whether they trigger AI Overviews. Prioritize high-AI-volume, high-conversational keywords that get AI surfaces. Write once, optimize for LLM visibility automatically.
→ For content teamsMulti-location market sizing
Agencies managing 5+ local locations pull AI keyword data per market. Compare AI demand across Denver, Austin, Charlotte. See which market has highest LLM query volume for your service keywords. Focus client budgets where AI traffic is richest.
→ For agenciesAI-vs-Google keyword gap analysis
Pair this endpoint with [Search Volume API](/search-volume-api) to compare the same keywords. A keyword with high AI volume but low Google volume is a blue-ocean opportunity — write content targeting LLM discovery instead of competing in Google's crowded SERP. Shift strategy based on data.
→ Search Volume APICompetitive AI keyword tracking
Every month, pull AI keyword data for your top 20 commercial keywords. Track whether AI volume is rising or falling. Pair with [AI Mentions API](/ai-mentions-api) to see if rising AI volume correlates with more citations of your domain. Optimize timing of content updates.
→ AI Mentions APIWhy not use traditional keyword research tools like Ahrefs or Semrush?
Traditional keyword tools (Ahrefs, Semrush, Moz) are built on Google search volume — a metric that no longer captures the full picture. LLM search has different patterns, different intent, and different ranking signals. Here's how the options compare.
| Tool | Search volume type | LLM-specific data | Intent signals | Agent-ready |
|---|---|---|---|---|
| Google Keyword Planner (free) | Google only (ranges) | No | Basic | Manual only |
| Ahrefs ($129–299/mo) | Google volume (exact) | No LLM data | Yes, but Google-only | API available but dashboard-first |
| Semrush ($139.95–499.95/mo) | Google volume (exact) | No LLM data | Yes, but Google-only | API available but dashboard-first |
| Moz ($99–599/mo) | Google volume | No LLM data | Limited | No MCP integration |
| SE Ranking ($159+/mo) | Google volume | No LLM data | Yes | API available but credit opaque |
| Profound AI ($499–$2000/mo) | No (enterprise monitoring) | LLM mentions only | Yes, but limited | Dashboard only |
| Surfer AI (data component) | Google volume | No standalone LLM API | Google-focused | Content editor only |
| Local SEO Data AI Keyword Data API | AI search volume (ChatGPT, Claude, Gemini, Perplexity) | Conversational score, AI Overview triggering, intent signals | Informational, commercial, navigational breakdown | Native MCP + REST, agent-first |
Use it from your agent
Two integration surfaces: MCP for clients that speak MCP, REST API for everything else.
Direct MCP integration
Drop-in support in Claude Desktop, OpenClaw, Hermes Agent, and any MCP-aware client.
Add to your client's MCP config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"localseodata": {
"url": "https://mcp.localseodata.com",
"headers": {
"Authorization": "Bearer sk_live_..."
}
}
}
}REST API
For Perplexity Computer, ChatGPT Custom GPTs, custom agents, and any platform that calls REST endpoints directly.
Base URL:
api.localseodata.comSee the docs for endpoint reference and auth.
Your first call in three lines
Core parameters: `keywords` (array of up to 100 keywords) and optional `location` (defaults to United States, accepts 'City, State, Country' format). One call = 1 credit, which covers 50 keywords. Returns AI search volume, intent signals, conversational score, AI Overview triggering, and 12-month monthly_searches breakdown.
curl -X POST https://api.localseodata.com/v1/ai/keyword-data \
-H "Authorization: Bearer sk_live_..." \
-H "Content-Type: application/json" \
-d '{
"keywords": ["best plumber austin", "emergency plumber near me", "plumbing repair cost"],
"location": "Austin, Texas"
}'$0.005 per 50 keywords
1 credit covers 50 keywords. Free tier on signup includes 50 credits (2,500 keywords). Monthly plans start at $19 and never expire. No per-seat fees, no seat caps.
Common questions
What is the AI Keyword Data API?+
POST /v1/ai/keyword-data. Cost: 1 credit per 50 keywords (~$0.005). This is the foundation for AI-first keyword research — ranking keywords by signals that matter to LLMs, not Google.How does AI search volume differ from Google search volume?+
What are intent signals and why do they matter?+
What is conversational score?+
What does triggers_ai_overview mean?+
How does this compare to traditional tools like Ahrefs or Semrush?+
Where does the AI search volume data come from?+
How fresh is the data?+
triggers_ai_overview flag reflects current Google AI Overview behavior and updates weekly. If you're tracking real-time keyword performance, monthly freshness is appropriate for strategic planning. It's not designed for hourly bid adjustments — it's designed for agents planning content calendars and keyword prioritization workflows.Can I compare AI volume across locations?+
location parameter is optional and accepts 'City, State, Country' format. The same keyword has different AI search volume in Denver vs. Austin vs. New York. Run the endpoint once per location to build a geographic comparison. This is standard for multi-location agencies and in-house teams managing multiple markets. Batch process: 3 locations × 50 keywords per call = 3 API calls, 3 credits total (~$0.015).How does this pair with Search Volume API and other endpoints?+
Can AI agents use this directly?+
claude_desktop_config.json and your Claude agent calls this endpoint from any prompt. REST: any agent that can make HTTPS calls (ChatGPT Custom GPTs, Perplexity Computer, custom Python/Node agents) hits the API directly with your Bearer token. The agent receives structured JSON and can filter by intent, conversational score, AI Overview triggering, or volume trends. No integration code needed — just write the agent prompt.What changed in 2026 that made AI keyword data necessary?+
Often used in the same agent prompt
Search Volume API
Traditional Google search volume, CPC, and competition. Compare alongside AI volume.
POST /v1/ai/visibilityAI Visibility
Composite score for your domain across LLMs. Track overall AI presence.
POST /v1/ai/mentionsAI Mentions
See exactly where your brand is mentioned in LLM responses for these keywords.
POST /v1/ai/overviewAI Overview
Check if Google AI Overviews cite your domain for specific keywords.
Build keyword strategies for LLM search, not just Google search.
50 free credits on signup. 2,500 keyword lookups included. Batch your target keywords and let your agent rank by AI signals.