Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey1 EndpointsREST
For Agents
Programmatically get an analytics report. Covers 1 operations with apiKey authentication.
Use for: I need to an analytics report, Find available analytics operations, Get the current status of SEMrush API resources, List all records from SEMrush API
Not supported: Does not handle payments, communications, or crm - use for analytics only.
SEMrush Analytics API provides access to SEO and competitive intelligence data including domain analytics, keyword research, backlink analysis, and URL-level reports. The API uses a single endpoint with a 'type' parameter to specify the desired report. The API exposes 1 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the SEMrush API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SEMrush 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%2Fsemrush.com%2Fsemrush" | 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%2Fsemrush.com%2Fsemrush" | 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 SEMrush API.
Get an analytics report
Manage analytics data programmatically
Integrate SEMrush API into automated workflows
Query and filter SEMrush API records by parameters
Monitor SEMrush API operational status and events
Use Cases
Patterns agents use SEMrush API for, with concrete tasks.
★ Analytics Operations
Use the SEMrush API to perform analytics operations programmatically. The API provides 1 endpoints covering core functionality including get an analytics report.
Call GET / to get an analytics report
Data Retrieval and Monitoring
Query SEMrush API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary SEMrush API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call SEMrush API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get an analytics report', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — semrush analytics api provides access to seo and competitive intelligence data including domain analytics, keyword research, backlink analysis, and url-level reports.
METHOD
PATH
DESCRIPTION
GET
/
Get an analytics report
GET
/
Get an analytics report
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.
S
SEMrush API
- Foundational (D)46/100
100
Foundational Compliance64
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience94
Agent Usability15
Security50
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
5%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
53%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
33%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
50
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
50%
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 the SEMrush API by hand means learning that the key travels as a query parameter, assembling report requests against api.semrush.com, and parsing its responses yourself. Through Jentic you install once, import the SEMrush API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The SEMrush API exposes a single report endpoint, so scoping is operations-only: limit the agent to the report operation it needs and nothing more. You choose the operations it may call, so anything you do not add stays out of reach.
Credential isolation
Your SEMrush 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 'get an analytics report' or 'pull domain metrics', and Jentic returns the matching SEMrush API 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 SEMrush API through Jentic.
What authentication does the SEMrush API use?
The SEMrush API uses an API key passed in the `key` query. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get an analytics report with the SEMrush API?
Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SEMrush API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get an analytics report through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get an analytics report'. Jentic returns the matching SEMrush API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SEMrush API have?
The SEMrush API exposes 1 endpoints covering default operations.
Can I limit what my agent is allowed to do with the SEMrush API?
Yes. The SEMrush API exposes a single analytics report endpoint, so scoping is operations-based: in your own self-hosted Jentic One instance, you decide which operations the agent may call, and any operation you do not add stays out of reach. Because you also control which stored credentials the agent can use, the API key you save is injected only when the agent runs the report operation you permitted. If you add only the report call, that is the sole thing your agent can do with SEMrush.
GET STARTED