Official vendor OpenAPI document · agent-readyMarketingSeo SemapiKey58 EndpointsREST
For Agents
Research keywords, analyse SERPs, audit backlinks, and generate content briefs and on-page QA for a target domain, with queued rank tracking and webhook job notifications.
Use for: Analyze the top search results for 'project management software' in the United States, Find keywords my competitor ranks for that my domain does not, I want to see which domains link to my site and which anchors they use, Get a content brief for a new article targeting 'best CRM for startups'
Not supported: Does not publish content, edit websites, or manage paid search campaigns. Use for SEO research, content planning, backlink analysis, and rank tracking only.
The AgentSEO API returns search, SERP, keyword, backlink, and content-planning data shaped for AI agents working on search optimisation. It runs web searches and page extraction, analyses a keyword's SERP and AI overview, and reports a domain's ranked keywords, competitors, traffic estimate, and backlink profile including anchors and referring domains. Content endpoints produce briefs, SERP outlines, draft QA, title and meta suggestions, internal link plans, and cannibalisation checks from a keyword and a URL or markdown. Rank tracking runs as a queued job with status polling, and webhook endpoints notify a client when jobs finish.
Install Jentic One Beta
Connect the AgentSEO API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AgentSEO API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fagentseo.dev%2Fagentseo" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fagentseo.dev%2Fagentseo" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AgentSEO API.
Analyze the SERP for a keyword by location and device, and extract the AI overview shown for it
Research keywords with idea suggestions, search-volume metrics, and keyword clustering
Audit a domain's backlink profile: summary, link list, anchors, referring domains, and new or lost links over time
Compare a domain against competitors with ranked keywords, keyword intersection, and traffic estimates
Generate content briefs, SERP outlines, and title and meta suggestions for a target keyword
Check a draft or live page with content draft QA, technical publish QA, and CRO and CTA review
Queue rank tracking for a keyword and URL, then read the rank history once the job completes
Use Cases
Patterns agents use AgentSEO API for, with concrete tasks.
★ AI SEO research agent through Jentic
An AI agent asked to plan content for a site needs keyword and SERP data without a hand-built client. Through Jentic the agent searches for 'analyze the SERP for a keyword', receives the AgentSEO operation with its input schema, and calls POST /analyze/serp with the keyword, location, and device. It then calls POST /keyword-ideas/suggest to widen the list and returns a ranked set of target keywords with the SERP features that compete for each.
Call POST /analyze/serp with keyword 'project management software', location 'United States', and device 'desktop', then call POST /keyword-ideas/suggest with the same keyword and limit 50, and summarise the top opportunities
Competitor keyword gap analysis
A marketer wants the keywords a competitor ranks for that their own domain misses. AgentSEO's POST /domain/intersection takes target1 and target2 domains and returns shared and exclusive ranking keywords, while POST /domain/ranked-keywords lists each domain's rankings with search volume and rank filters. Combined with POST /domain/traffic-estimate, the agent can prioritise gaps by the traffic they carry.
Call POST /domain/intersection with target1 'example.com' and target2 'competitor.com', then POST /domain/traffic-estimate with both domains in targets, and list the ten highest-volume keywords only the competitor ranks for
Backlink profile audit
An SEO lead reviewing link health needs counts, sources, and anchor text for a domain. POST /backlinks/summary returns the headline profile, POST /backlinks/referring-domains and POST /backlinks/anchors break it down by source and anchor, and POST /backlinks/new-lost-timeseries shows gained and lost links between date_from and date_to. The dofollow_only and broken_only filters on POST /backlinks/list isolate the links worth acting on.
Call POST /backlinks/summary for target 'example.com', then POST /backlinks/list with target 'example.com' and broken_only true, and report the broken links with their referring pages
Content brief and pre-publish QA
A content team drafts against what the SERP rewards and checks the page before it goes live. POST /content/brief builds a brief for a keyword with audience, brand_voice, and page_type inputs, POST /content/draft-qa scores a draft_url or draft_markdown against the keyword, and POST /content/title-meta proposes a title and meta description. POST /content/technical-qa then checks canonical and on-page issues before publishing.
Call POST /content/brief with keyword 'best CRM for startups' and page_type 'article', then POST /content/draft-qa with the same keyword and the draft_markdown text, and list the gaps the QA reports
Rank tracking with job webhooks
A site owner wants to know where a page ranks for a keyword over time. POST /rank/track queues a tracking job for a keyword and URL, GET /jobs/{id} reports the job's status, and GET /rank/track returns the rank history for the keyword and url pair. Registering a webhook with POST /webhooks/endpoints lets a client receive job events instead of polling, and failed deliveries can be retried with POST /webhooks/deliveries/{id}/retry.
Call POST /rank/track with keyword 'crm for startups' and url 'https://example.com/crm', poll GET /jobs/{id} until it completes, then call GET /rank/track with the same keyword and url to read the history
Key Endpoints
58 endpoints — the agentseo api returns search, serp, keyword, backlink, and content-planning data shaped for ai agents working on search optimisation.
METHOD
PATH
DESCRIPTION
POST
/analyze/serp
Analyze the SERP for a keyword
POST
/keyword-ideas/suggest
Suggest keyword ideas from a seed keyword
POST
/domain/ranked-keywords
List keywords a domain ranks for
POST
/backlinks/summary
Summarise a domain's backlink profile
POST
/content/brief
Generate a content brief for a keyword
POST
/rank/track
Queue rank tracking for a keyword and URL
GET
/jobs/{id}
Get job status
POST
/webhooks/endpoints
Create a webhook endpoint
POST
/analyze/serp
Analyze the SERP for a keyword
POST
/keyword-ideas/suggest
Suggest keyword ideas from a seed keyword
POST
/domain/ranked-keywords
List keywords a domain ranks for
POST
/backlinks/summary
Summarise a domain's backlink profile
POST
/content/brief
Generate a content brief for a keyword
POST
/rank/track
Queue rank tracking for a keyword and URL
GET
/jobs/{id}
Get job status
POST
/webhooks/endpoints
Create a webhook endpoint
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AgentSEO API
- Non-Ready (F)37/100
44
Foundational Compliance57
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience93
Agent Usability50
Security51
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
77%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
27%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
51%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
51
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
51%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring AgentSEO by hand means sending the key in the x-api-key header, shaping request bodies for dozens of POST operations, and polling queued jobs or registering webhooks for rank tracking. Through Jentic you install once, import AgentSEO from the API Directory, store the key once, and your agent calls it.
Permission scoping
AgentSEO carries its targets (keywords, domains, URLs) inside request bodies, so rules bound which operations your agent may call, not which domain it researches. You choose the operations it may call, so webhook changes like deleting an endpoint are not included unless you add them.
Credential isolation
Your AgentSEO API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'analyze the SERP for a keyword' or 'audit a domain's backlinks', and Jentic returns the matching AgentSEO operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AgentSEO API through Jentic.
What authentication does the AgentSEO API use?
The AgentSEO API authenticates with an API key sent in the `x-api-key` request header, declared as the ApiKeyAuth scheme in its OpenAPI spec and applied globally to its operations. Through Jentic the key is held by your own Jentic One instance and attached to each call, so the agent never handles it.
Can I audit a domain's backlinks with the AgentSEO API?
Yes. POST /backlinks/summary returns the headline profile for a target, POST /backlinks/referring-domains and POST /backlinks/anchors break it down by source domain and anchor text, and POST /backlinks/new-lost-timeseries shows links gained and lost between date_from and date_to. POST /backlinks/list accepts filters such as dofollow_only and broken_only.
How does rank tracking work in the AgentSEO API?
Rank tracking is asynchronous. POST /rank/track queues a job for a keyword and url, GET /jobs/{id} returns the job status, and GET /jobs/{id}/events streams status updates. Once the job is done, GET /rank/track with the same keyword and url returns the rank history. You can also register a webhook with POST /webhooks/endpoints to be notified of job events.
What are the rate limits for the AgentSEO API?
The OpenAPI spec does not specify rate limits. Check the AgentSEO documentation at https://www.agentseo.dev for current limits and plan quotas before running large keyword or backlink batches.
How do I analyze a keyword's SERP through Jentic?
Search Jentic for 'analyze the SERP for a keyword', load the POST /analyze/serp operation, and execute it with keyword plus optional location, device, and language. Pair it with POST /ai-overview/extract to capture the AI overview for the same keyword. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there an AgentSEO MCP server?
You don't need an MCP server to give your agent AgentSEO. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the SERP, keyword, and backlink operations it needs on demand, without loading a full set of tool definitions into its context.
Can I limit what my agent is allowed to do with the AgentSEO API?
Yes. For a research-only agent, write a rule that allows POST /analyze/serp, POST /keyword-ideas/suggest, and POST /backlinks/summary, and leave out the webhook operations. The agent can then read SERP, keyword, and backlink data but cannot create, change, or delete webhook endpoints, and each call it makes is logged.
GET STARTED