For Developers
AI search visibility you can integrate.
Foglift tracks, monitors, and responds to how ChatGPT, Claude, Perplexity, Gemini, and Google AI Overview cite your brand. Available as a typed REST API, an MCP server, a CLI, and an npm tracker. The same data the dashboard shows is available everywhere you ship code.
Free tier requires no API key. Paid plans start at $49/mo.
5-minute integration
One of our paying customers shipped from signup to first scan in 6 minutes: Stripe checkout, API key, CLI install, working integration. Pick the surface that matches where you already work.
REST API (no install)
Curl a public scan. No key needed.
curl "https://foglift.io/api/v1/scan?url=example.com"CLI
Run from terminal or CI. Colored output, JSON, threshold gating.
npm install -g foglift-scan
foglift scan https://example.com --jsonMCP server (Claude Code, Cursor, Windsurf)
13 tools available inside your AI editor.
// ~/.claude/mcp.json
{
"mcpServers": {
"foglift": {
"command": "npx",
"args": ["foglift-mcp"]
}
}
}npm tracker
Record AI crawler hits from your own site.
npm install foglift-tracker
import { track } from "foglift-tracker";
track({ apiKey: process.env.FOGLIFT_API_KEY });What developers build with Foglift
Three patterns we see most often from teams that wire Foglift in directly.
CI/CD gating
Scan every pull request against your tracked prompts. Fail the build if AI Readiness drops below threshold. Same pattern as Lighthouse CI, applied to AI search.
# .github/workflows/aeo.yml
- run: npx foglift-scan https://preview-${{ github.sha }}.example.com --threshold 75Custom dashboards and observability
Pull geo_results, sentiment, and citation data from /api/v1/historyinto Grafana, Metabase, your internal BI tool, or a Notion database. AI search visibility becomes a metric your team already watches alongside latency and conversion.
curl -H "X-API-Key: $FOGLIFT_KEY" \
"https://foglift.io/api/v1/history?workspace_id=$WS&limit=100" \
| jq '.results[] | {date, visibility_rate, by_model}'Agentic content workflows
The MCP server lets Claude Code or Cursor refactor a page, re-scan it, and iterate. The agent sees the live AEO score and dimension breakdown in the same loop where it writes the markup. Closed-loop AEO without leaving the editor.
# In Cursor or Claude Code, with the MCP server installed:
"Scan /pricing on the preview deploy, then add FAQ schema to fix the
top recommendation, then re-scan and report the delta."API surface at a glance
Nine endpoints cover the full platform. Full reference in /docs.
| Endpoint | Verb | Purpose |
|---|---|---|
| /api/v1/scan | GET | Public website audit. No key. AEO + SEO + security + a11y scores in JSON or text. |
| /api/v1/scan/batch | POST | Scan up to 10 URLs in one request. API key required. |
| /api/v1/aeo-score | GET | Detailed AEO breakdown across 8 dimensions, grade, top recommendations. |
| /api/v1/content-brief | GET | Target prompts, content gaps, structure recommendations for a page. |
| /api/v1/monitor | GET | Read AI visibility results, model breakdown, citations, trends. All plans. |
| /api/v1/monitor/run | POST | Trigger on-demand AI Visibility scan. Enterprise. |
| /api/v1/prompts | GET/POST/DELETE | CRUD for monitoring prompts. API key required. |
| /api/v1/history | GET | Paginated visibility history with per-model breakdown. |
| /api/v1/crawler-analytics | GET | AI bot visits to your site (GPTBot, ClaudeBot, PerplexityBot, etc.). |
Authenticate with an X-API-Key header. Generate keys in Settings → Developer.
Pricing for builders
The Launch plan exists for solo founders and small teams who want the full API, MCP, and CLI surface without committing to an agency-tier price.
Launch
API + MCP + CLI
- •4,000 tokens/mo
- •Daily AI Visibility monitoring
- •All 5 AI engines
- •3 brands tracked
- •100 API reads/day
Growth
Twice-daily monitoring
- •11,500 tokens/mo
- •Twice-daily monitoring
- •10 brands tracked
- •1,000 API reads/day
- •Webhooks
Enterprise
Read + write API
- •27,000 tokens/mo
- •Hourly monitoring
- •Unlimited brands
- •Unlimited API reads
- •10 on-demand scan triggers/day
Free tier (no API key) gets 15 public scans per day. Full plan comparison on /pricing.
Ready to wire it up?
Generate an API key in your dashboard. Or open the docs and try a public scan first.
For AI-first founders
A working series on AI search visibility from the operator’s seat. Written for founders shipping AI-native products who care about how their own brand surfaces in ChatGPT, Claude, Perplexity, Gemini, and Google AI Overview.
Live
How I Optimize AI Search Visibility for My SaaS and Let Agents Close the Loop
The active optimization loop a solo AI-first founder runs: visibility surfaces the gap, recommendations point at the fix, an MCP-in-Cursor agent applies it, the next scan confirms.
Live
Why Your AI Product is Invisible to ChatGPT (and How to Fix It)
Diagnosing why ChatGPT recommends competitors instead of your AI product, with a 4-step fix using AEO scoring and prompt-targeted content.
Coming soon
The AI-First Founder Content Stack: Writing for LLMs as Your First Reader
Structure, citations, and FAQ patterns that turn marketing pages into answer-extraction-ready surfaces for AI search engines.
Coming soon
Building AI Search Visibility Into Your Product From Day One
Schema markup, entity disambiguation, and on-page signals to ship alongside your MVP, before you have a single customer to point at.
Coming soon
A 90-Day AI Search Visibility Plan for AI-First Founders
Week-by-week plan covering setup, baseline measurement, content shipping, citation building, and the metric you measure on day 90.