Your Brands
Acme API > Overview
GEO Score
How well Acme API is optimized for AI
Overall Score
82/100
↑ 4 pts vs last week
Score Breakdown
Agent Citations
How often Acme API is recommended across top coding agents
Cursor
84%
Top recommended
Claude Code
62%
2nd recommended
OpenAI Codex
23%
Needs improvement
GitHub Copilot
42%
Needs improvement
Used by teams from
Your API wasn't built for the AI era
AI is generating more code than ever — but it's getting your API wrong.
Agents hallucinate endpoints, recommend competitors, and generate broken integrations. Your docs weren't designed for how AI reads them.
The result? Lost developer adoption, more support tickets, and an API that's invisible to the tools developers actually use.
AI
Generating code...
Add Acme payment processing to my checkout flow
Sure! Here's the Acme integration:
import Acme from 'acme'
const acme = new Acme(key)
// Create a charge
const charge = await acme
.charges.create({
amount: 2000,
currency: 'usd',
})
Deprecated API
charges.create was deprecated in 2022. Use PaymentIntents instead.
You might also try competitor-payments which has better docs...
Get your GEO Score
GEO Score Trend
Doc Quality
91
↑ 8 pts
Agent Citations
247
↑ 34%
Hallucination Rate
3.2%
Fix Kit
Auto-generated fixes for your API based on your GEO audit results
Acme API
3 critical fixes · 5 improvements available
Recommended fixes
Add OpenAPI 3.1 schema for /v1/payments endpoint
Schema fixInclude error response examples in documentation
Doc updateAdd llms.txt file to API root for agent discovery
Agent compatMonitor & improve
Agent Compatibility
| Dimension | Cursor | Copilot | Claude |
| Schema parsing | ● | ○ | ○ |
| Auth handling | ● | ● | ○ |
| Error recovery | ● | ○ | ○ |
| Code examples | ○ | ● | ○ |
| Rate limiting | ○ | ○ | ● |
| Webhook setupNeeds work | ○ | ○ | ● |
The GEO difference
Without GEO
With GEO
The numbers
speak for
themselves
70%
of all code will be AI-generated by 2027, according to industry projections. Is your API ready?
3x
more API calls are made through AI than through manual developer integration for top-optimized APIs.
85%
of APIs fail basic compatibility checks with AI — resulting in hallucinated endpoints and broken code.
Frequently asked questions
Everything you need to know about Generative Engine Optimization and how Sapient helps your API get recommended by AI.
Got
questions?
What is Generative Engine Optimization (GEO)?
GEO is like SEO, but for AI. Just as SEO helps websites rank on Google, GEO helps your API get recommended when developers use tools like Cursor, Claude Code, GitHub Copilot, and other AI coding assistants.
How does the GEO Score work?
Your GEO Score is a 0-100 rating based on five dimensions: Documentation Quality, Schema Clarity, Error Handling, Example Coverage, and Agent Compatibility. Higher scores mean AI is more likely to correctly recommend and implement your API.
Which AI does Sapient support?
Sapient optimizes for all major AI including Cursor, Claude Code, GitHub Copilot, Windsurf, Amazon Q, Gemini, OpenAI Codex, and Cline — with more being added regularly.
How long does it take to improve my score?
Many improvements take effect within days. Our Fix Kit provides ready-to-use templates and code that you can implement immediately. The Monitor dashboard tracks your progress in real time so you can see results as they happen.
Is Sapient available now?
Sapient is currently in early access. Get Started to get early access and be among the first API teams to optimize for the AI era.