The Frontier AEO Tracker: What Astra Chooses (and every other frontier model, and what you can do about it)
- ID
- 22208
- Status
- summarized
- Published
- 08 Sep 2026, 5:32 AM
- Fetched
- 08 Sep 2026, 6:28 AM
- Provider
- Latent Space
- Category
- developer-ai
- Original URL
- https://www.latent.space/p/aeo
- Source URL
- https://www.latent.space/feed
Summary
- Score
- 7.5
- Created
- 08 Sep 2026, 6:29 AM
- Tags
- Audience
- developersai_ml_learnerssaas_founders
What happened
Latent Space built a Frontier AEO (Answer Engine Optimization) Tracker running 6 prompt variations across 7 frontier models in 161 product categories, from coding agents to payroll software. They found clear self-bias (Claude models recommend Claude Code, Astra recommends Codex, Grok recommends Cursor), 28 categories with a universally dominant primary choice across all models, and consequential recommendation flips between model generations (Opus→Fable, Sol→Astra) that signal shifts in training data and RL priorities.
Why it matters
If you ship a SaaS product, AI agents are increasingly the recommender layer your users consult before trying or buying — this tracker shows which products already dominate agent recommendations and which categories are still contested battlegrounds. SaaS founders should check their own category in the tracker and invest in AEO (content, citations, documentation that agents surface) before a competitor locks in a dominant position. Developers building agent pipelines should expect and mitigate model self-bias when using recommendations for tool or vendor selection.
Discussion angle
Which categories in the tracker are still 'close contests' rather than locked-in dominators, and what concrete AEO moves (docs, structured data, citation-worthy content) could a Malaysian SaaS founder make to win agent recommendations in those battlegrounds?