Skip to main content
v1.4.0
July 2026

Sturdier runs and honest refunds

No big new surface this time. v1.4.0 is a consolidation release: fixes and improvements that make runs finish reliably and keep billing honest.

Fixed

Stalled scheduled runs recover on their own. A scheduled visibility run that got stuck used to sit “running” forever and quietly block new runs for that project. Stuck runs are now detected and restarted automatically.Scheduled runs are never blocked by manual-run limits. Guards built to stop rapid manual clicking no longer apply to your schedule, so two projects due in the same window both run.Canceling an AI Indexing run refunds what it should. Cancel before pages start checking and the full reservation comes back. Cancel mid-run and the dialog shows exactly how many pages are billable and how many return to your allowance. Canceling twice can no longer refund twice.One run of a kind at a time. Starting the same check twice on one project now brings the second attempt to the already-active run instead of creating a duplicate. This is enforced at the database level, so it holds even under simultaneous clicks.Readiness keeps your www pages on apex domains. If your site redirects example.com to www.example.com, page discovery now keeps all your sitemap URLs instead of dropping them.Failed AI Indexing pages show as failed. Individual page failures can no longer stall a run or hide in the report.The billing page no longer flickers on first load. A mismatch between the server-drawn and browser-drawn page forced a visible re-render for some users. Both now draw the same page.

Improved

AI Indexing reports are shareable links. Every run has a stable URL you can reload, bookmark, or paste to a teammate. Reports stay sign-in protected: someone else’s run link shows “not available,” never your data.Delete topics and brands without losing history. Deleting now hides the item from management and future runs while keeping every past report intact, and you can re-add the same name later.A clearer plan comparison. The pricing and billing pages share one rebuilt plan table that reads correctly in both light and dark mode.Visibility report PDFs show progress. A generating state replaces the silent wait.

For API and MCP users

Batch writes. The MCP write tools now accept batches, so an agent can set up prompts, topics, and competitors in a few calls instead of dozens.
Breaking MCP tool renames. Every write tool was renamed to a plural form and now takes an array: add_competitoradd_competitors, delete_topicdelete_topics, create_workstreamcreate_workstreams, and so on for all 17 write tools. If you call these tools directly, update your integration before your next run. The MCP tools reference lists the current names.
A video walkthrough of the MCP server. The MCP docs page now embeds a short Loom showing setup end to end.

Questions?

If a refund looks wrong or a run misbehaves, email contact@aibread.com and we’ll sort it out.
v1.3.0
June 2026

AI Index Coverage, Content Audit, and a cleaner MCP surface

Two new tools answer the questions agencies keep asking: which of my pages do AI platforms actually know about, and what should I fix first to get cited. The MCP server also gets a safety and naming cleanup.

New

AI Index Coverage. Point a run at your site and see, page by page, whether ChatGPT, Claude, and Gemini have your content indexed. Every page gets a clear verdict: indexed, not indexed, or unknown. It lives on its own page in the dashboard, next to Site Readiness. We validated the checks against a hand-labeled dataset, so verdicts are measured, not guessed. When we mark a page indexed on ChatGPT or Claude, we only count pages the assistant actually cited or returned, so those verdicts are highly accurate. Gemini is a lower-confidence signal, since it can occasionally surface a URL it reconstructed rather than one it retrieved, and we are actively tightening it. A run also harvests the citations it already collected and uses them to confirm pages other checks missed, which recovers real coverage at no extra cost. Free includes a monthly page allowance so you can try it on a real site; paid plans raise the cap and unlock full per-page detail.Content Audit. Audit your whole site for how well each page can be cited by AI, then work a prioritized list instead of a wall of data. Each page gets a citation-potential score. You get an ordered worklist of what to fix first, an impact-versus-effort view, and a side-by-side of the current text against a stronger version you can copy. A cross-reference helper points you at a page you already wrote that does the weak part well, so you can mirror it. Free orgs see every page’s score and the worklist; full fix detail, rewrites, and PDF export are on Starter and Agency. Monthly page allowances are 30 on Free, 1,000 on Starter, and 10,000 on Agency.

Improved

Larger page allowances on multi-seat plans. AI Indexing and Readiness page allowances now scale with the number of paid seats in your organization, so larger teams get proportionally more room without changing plans.More accurate AI Indexing on Free. The citation cross-check that upgrades a “not indexed” page to “indexed” now runs for everyone, including Free, so free runs report the same corrected coverage paid runs do.

For API and MCP users

Breaking MCP tool renames. If you call these tools directly, update your integration before your next run.
  • manage_schedule is replaced by get_schedule (read) and update_schedule (write).
  • manage_workstream is replaced by create_workstream, update_workstream, archive_workstream, and unarchive_workstream.
Read and write are now separate, and every tool says which it is. No tool both reads and writes anymore, and each one carries a hint marking it read-only or as making changes. Compatible MCP clients can run reads without a per-call confirmation and prompt before anything that modifies or deletes. Tools that consume your plan’s allowance now say so in their description.New MCP tools. Agents can drive the two new features end to end:
  • run_ai_index_coverage, get_ai_index_coverage_run, list_ai_index_coverage_runs
  • run_content_audit, get_content_audit_status, get_content_audit_results, list_content_audits
  • Site Readiness is now MCP-callable too: run_readiness_check, get_readiness_run, list_readiness_runs.

Questions?

If a verdict looks wrong, a limit doesn’t fit how you work, or a renamed tool is blocking you, email contact@aibread.com and we’ll sort it out.
v1.2.0
June 2026

Site & Agent Readiness

Readiness is a new product surface that audits your own site instead of measuring what AI platforms say about you. It crawls a project’s site, scores how discoverable and retrievable it is to AI agents and crawlers, and tells you exactly what to fix. It lives at Readiness in the dashboard, alongside your visibility view.

New

Readiness runs and a score out of 100. Point a run at your site and get an overall readiness score with a verdict, broken down across six categories: Discoverability, Content Accessibility, Bot Access Control, Protocol Discovery, Agentic Commerce, and Agentic Browsing. Every check is marked pass, warn, or fail, and carries the issuing authority and maturity behind the standard it tests (Sitemaps.org, IETF, Cloudflare, Google, Schema.org, and more). Results stream in live as the run crawls, check by check.Run history. Every run is saved per project. Reopen any prior run in full detail to see how the site has changed.Tiered scope and a monthly page allowance. Two levers control how much a run crawls: a per-run page cap and a calendar-month pooled page allowance. A run that exceeds your balance is clamped to what’s left, not blocked. Lighthouse sampling stays small and flat, so larger crawls never slow runs down. See limits and allowances for the per-plan numbers.A real taste on Free. Free orgs run a full scan, see the overall score and every check’s status, and get full detail on the first two flagged checks. Upgrade for full detail on every check.Scheduled runs. Starter schedules weekly or monthly; Agency adds daily. A schedule fires automatically so your score keeps tracking your site.PDF export, branding, and share links. Download any run as a PDF, plain or branded with your logo and brand color, with standards-credibility marks. Agency plans can publish a public, revocable share link to a run.Agent Journey waitlist. Join the waitlist for Agent Journey from the Readiness surface.

Questions?

If something looks wrong or a limit doesn’t fit how you work, email contact@aibread.com and we’ll sort it out.
v1.1.0
June 2026

A small signup addition, and reliability work behind the scenes

Most of this release was internal plumbing to make the product more reliable. One change is visible when you sign up.

New

“Where did you find us?” on sign-up. New accounts can tell us how they found OpenLens. It’s optional and takes one click. It helps us learn which channels bring in the people who get the most out of the product.

Improved

Steadier behind the scenes. We tightened how account and subscription changes flow through our systems and moved tracing onto a faster pipeline, so fewer things slip through the cracks. Nothing in your dashboard changes.

Questions?

Email contact@aibread.com any time.
v1.0.0
June 2026

Teams, plans, and your full platform coverage

This release turns OpenLens into a multi-seat product. You can now bring your whole team and your clients into one workspace, pick a plan that fits how you work, and track every major AI platform, including Grok, which is back. Existing accounts keep their current limits as a permanent floor, so nothing you rely on today gets smaller.

New

Organizations, seats, and client logins. Your workspace is now an organization you can invite people into.
  • Roles that match how agencies work. Owners and admins manage the account; members do the work; clients get a read-only login to see only their own projects.
  • Seats only count editors. Viewers and client logins are free and unlimited. You pay for the people who actually run and edit work, not for everyone you want to show a dashboard to.
  • Invite teammates and clients from your organization settings, and move a teammate’s project access around without removing and re-adding them.
Starter and Agency plans. Two paid plans, each with a 7-day free trial and a 15% discount if you pay annually. See plans and pricing for what each tier includes.
  • Starter is for a single brand or a small team: up to 5 projects, with weekly tracking across the core platforms.
  • Agency is for running many clients: unlimited projects and seats, daily tracking, and Claude and Grok included.
  • Every plan includes the REST API, the MCP server, prompt attributes, full docs, and a public status page.
  • Read the full announcement in Introducing Starter and Agency.
A Usage page. A single place to see your plan, your seats, and how much of your monthly output allowance you’ve used, so there are no surprises.Grok is back, and Claude is included on Agency. We restored Grok coverage through a direct API integration, with citations, and Agency plans now include both Claude and Grok alongside ChatGPT, Perplexity, Google AI Overview, Gemini, and DeepSeek.

Improved

Existing accounts are protected. Every account that existed before this launch keeps its current limits as a floor, permanently. The new plan limits never claw back what you already had. If you were tracking more than the new defaults allow, you keep what you were using.A more reliable sign-in. We fixed several sign-in and sign-up issues, including a hang on the sign-up button in some browsers, accounts with two-factor authentication, and Google sign-up not always carrying you through to the app.A refreshed dashboard. The interface got a research-grade visual refresh, a new logo, and a faster, denser dashboard.A public status page. Check live platform health any time at openlens.com/status.

For API and MCP users

No breaking changes. No endpoints or MCP tools were renamed or removed, and existing API keys keep working. Two things are new:
  • Organization-scoped API keys and MCP. You can now issue keys at the organization level, and MCP sessions see the projects in your active organization. Your existing personal keys continue to work unchanged.
  • Per-plan usage on API and MCP. API and MCP calls are now metered against your plan. Each plan includes a monthly allowance; once you pass it, calls return a clear message with an upgrade prompt instead of failing silently.

Questions?

If a limit doesn’t fit how you work, or something looks wrong, email contact@aibread.com and we’ll sort it out.
v0.2.0
June 1, 2026

Durable prompt runs and sharper brand detection

This release rebuilds the engine behind prompt runs so they survive restarts and deploys without dropping or duplicating prompts, sharpens how we detect your brand and competitors, and adds alias management to project settings.

New

Durable, crash-safe prompt runs. We rebuilt how a prompt run executes. Each run is now tracked task-by-task in the database rather than only in memory, so a run keeps a complete, accurate record of which prompts and platforms it covers even if the server restarts mid-run (which happens routinely on every deploy).
  • No more dropped or duplicated prompts. If a run is interrupted, it resumes from exactly where it left off instead of re-running work it already finished or silently skipping work it hadn’t reached.
  • Self-recovering runs. A run that gets stranded by a server restart is now detected and driven to completion on its own, instead of blocking that project’s future scheduled runs until someone notices. Scheduled reports are far less likely to show a gap.
Brand alias management. You can now edit the list of aliases for each brand directly from project settings. Trade names, initialisms, short forms. OpenLens uses that list when deciding whether a mention in an AI answer is really your brand (or a competitor), so keeping it accurate directly improves your numbers.

Improved

More accurate brand detection. Brand matching now records which alias triggered each mention, so a mention is tied to the exact name it matched on. That makes detection easier to audit and tightens the line between a real mention and a coincidental substring.Historical reports are not auto-corrected. They reflect the detection logic that was live when the run happened. Run a fresh scan if you want a project re-scored against the latest logic.More complete answer coverage.
  • Google AI Overview retries. When a search doesn’t surface an AI Overview on the first try, OpenLens now retries before recording it as absent, so transient misses don’t understate your visibility.
  • Consistent outcome recording. Answers from every platform now consistently record whether they returned content, so success and no-content cases are reported accurately across all platforms.

For API and MCP users

No breaking changes for API or MCP integrations in this release. No endpoints or MCP tools were renamed or removed, and no request or response shapes changed in a way that requires you to update an existing integration.

Known issues

Grok coverage is temporarily unavailable. Grok has moved its responses behind a paywall, which has taken our Grok scraper offline. Until we restore it, prompt runs with Grok enabled will complete every other platform normally but will not return Grok results. We’re actively working on a fix.
If Grok is a critical platform for your reporting, reach out and we’ll let you know as soon as coverage is back.

Questions?

If something broke, looks wrong, or you want a project re-scored against the latest brand-detection logic, email contact@aibread.com.
v0.1.0
May 16, 2026

Prompt attributes, workstreams, and clearer naming

The last two releases (May 8 and May 16) shipped a new way to slice your data, a portfolio view for tracking goals over time, more AI platforms behind the scenes, and a cleaner vocabulary throughout the product.

New

Prompt attributes. Tag every prompt with one or more attributes. Branded vs non-branded, language, or any custom label you define per project (intent, funnel stage, persona, region). Every dashboard, metric, and report can now be filtered by those tags, so you can answer questions like “how do we rank on non-branded prompts in Spanish?” in one click.
  • Manage attributes from the new Prompt Attributes section under project settings. Create, rename, and archive option lists per project.
  • Edit attributes in place on any prompt. Analytics recompute against the live label set, so re-tagging is instant.
  • Auto-tagging on new prompts. When OpenLens generates prompts during onboarding, it now also assigns attributes automatically using Claude Sonnet 4.6.
  • Live filter preview. The attribute filter shows which prompts will be included while you build the filter, before you apply it.
Workstreams. A new portfolio surface for tracking the topics and attributes that matter to a single goal. Group a set of topics and prompt attributes into a workstream, set a visibility target, and watch progress over time. Useful for tracking campaigns, content initiatives, or any recurring objective tied to AI visibility.Grok and Gemini coverage. OpenLens now scans Grok and Gemini alongside ChatGPT, Perplexity, Google AI Overview, Claude, and DeepSeek. New projects can enable either one from the platform picker; existing projects can turn them on from project settings.Public docs. We launched public documentation, including the MCP server setup guide and the REST API reference. The original URL openlens.com/docs 301-redirects here.

Improved

Clearer terminology. We renamed two long-standing concepts so the product matches how agencies actually talk about the work:
  • Keywords are now topics. A topic is the underlying buyer-intent theme; the prompts under it are the actual questions sent to AI platforms.
  • Queries are now prompts, and a query run is now a prompt run.
All dashboards, settings, navigation, and exports use the new names. Old URLs continue to redirect.More accurate brand detection. We rewrote the brand-matching logic to cut both false positives (mentions of unrelated brands that happened to share a substring) and missed short forms (initialisms and trade names). Brands now carry an explicit alias list you can edit from project settings.Historical reports are not auto-corrected. They reflect the detection logic that was live when the run happened. If you want a project re-scored against the new logic, run a fresh scan or contact us.

For API and MCP users

Breaking changes. The terminology rename and the new attributes system change a handful of endpoints and MCP tools. If you build on the API or have an agent connected via MCP, please update before your next scheduled run.
REST API renames.
  • /api/queries/run, /api/queries/status, and /api/queries/results are replaced by /api/prompts/run, /api/prompts/status, and /api/prompts/results.
  • The onboarding confirm payload accepts topicList in place of keywordList. The legacy field is still accepted during the transition.
MCP tool renames.
  • run_queries becomes run_prompts
  • get_query_results becomes get_platform_responses
  • add_keyword becomes add_topic, and the rest of the query_* and keyword_* tool surface follows the same rename.
  • add_prompt now requires a non-empty attributes array. The simplest valid value is ["branded"] or ["non-branded"]. You can also pass any custom attribute already defined on the project.
New MCP tools. Agents can now manage attributes and workstreams end-to-end:
  • list_prompt_attributes, add_prompt_attribute, archive_prompt_attribute, unarchive_prompt_attribute
  • list_workstreams, get_workstream, get_workstream_breakdown, manage_workstream, update_workstream_goal
PostHog event renames. If you mirror OpenLens analytics into your own warehouse: event names query_run_* are now prompt_run_*, and keyword_* events are now topic_*. Every event also stamps a form_factor property (web, api, mcp, or cron) so you can split usage by surface.

Questions?

If something broke, looks wrong, or you want a project re-scored against the new brand-detection logic, email contact@aibread.com.