Company profile · 2 min read
Limy AI: measuring how brands appear in AI search
Limy positions itself as an AI-search visibility, attribution and analytics platform.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Limy helps companies observe how AI systems discover and describe their brands, then connect that visibility to traffic and pipeline questions.
What it does
The company homepage names Limy attribution, analytics, AI bot traffic and ads. Its documentation describes a tracking pixel and CDN integration for detecting AI bots and analyzing behavior. The pages frame the workflow as discovery-to-revenue measurement rather than ordinary rank tracking.
Buyer and task
Marketing, SEO and growth teams that need to see how AI systems discover and describe a brand.
Workflow boundaries
No current pricing, traffic lift or independent visibility result is established in the checked public pages. The product claims remain company claims.
What I would ask
Ask which crawlers are identifiable, how attribution is assigned, and where bot detection stops being a reliable explanation of pipeline.
Why it fits
Limy’s wedge is the measurement gap created when discovery happens inside an AI answer instead of a search-results click. The homepage separates attribution, analytics, AI bot traffic, ads and an AI traffic monitor. The documentation describes a lightweight tracking pixel and a CDN integration for detecting AI bots, analyzing their behavior and connecting that activity to the company’s agentic-web visibility question.
For a marketing team, the practical workflow is: establish what the brand is being recommended for, observe which AI systems or bots reach the site, then decide whether the traffic or pipeline can be attributed with enough confidence to change content or distribution. That is different from treating a rank-tracking dashboard as proof that a buyer saw or trusted an answer. The checked pages describe the product surface; they do not show the team’s attribution denominator, crawler coverage or independent pipeline result.
A serious evaluation should keep bot observations, referral traffic, assisted conversion and revenue as separate measures. It should also ask whether the pixel or CDN path changes page performance or privacy obligations. Limy is most relevant when a team already has a demand-capture system and needs to understand an emerging discovery layer, not when it is still guessing at its basic audience.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer | Marketing, SEO and growth teams |
| Product surface | AI-search visibility, attribution, analytics, bot traffic and ads |
| Collection paths named | Tracking pixel and CDN integration |
| Pricing and outcomes | Not documented in the checked public pages |
Sources checked
official Speedrun profile · company homepage · source page
Sources checked — September 20, 2026.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗