canonical: https://jentic.com/apis/limpiaudit.com/limpiaudit

# Limpiaudit Limpi API

The Limpi API runs asynchronous SEO and GEO audits of public websites: you submit a URL with crawl limits such as max_pages, max_depth, crawl_delay, and exclude patterns, then poll the audit as it moves from queued to running to completed. A finished audit returns a structured report with an overall score, section scores, per-page data such as titles, canonicals, and heading counts, individual checks, and prioritized recommendations with how-to guides for platforms like WordPress, Wix, and Squarespace. Errors follow RFC 9457 problem+json, and a usage operation reports the monthly page quota.

## For AI agents

Launch SEO and GEO audits of a website, track their status, fetch the finished report with scores, checks, and recommendations, and check the monthly page quota.

## Scope

Does not track keyword rankings, report backlinks, or edit your website. Use for crawling a site and reporting SEO and GEO audit findings only.

## Capabilities

- Launch an asynchronous SEO and GEO audit of a public URL with max_pages, max_depth, crawl_delay, and exclude patterns
- Track audits by status, such as queued, running, completed, failed, or cancelled, with cursor pagination
- Fetch a completed audit's report with overall and section scores, page-level data, checks, and recommendations
- Cancel a running audit before it finishes
- Check the monthly page quota, pages used, and pages available for the next audit
- Read the API key's identity and scopes

## Use cases

### Agent-run site audits through Jentic

An AI agent helping with a website can start a Limpi audit, poll it until the status is completed, and then summarize the report's top recommendations for the developer. Through Jentic the agent finds the create, read, and report operations by intent and loads their schemas, including the required Idempotency-Key header, so retries never launch a duplicate audit.

Example prompt: Create an audit for https://example.com with max_pages 50 and max_depth 3 using a unique Idempotency-Key, poll the audit by its job_id until status is completed, then fetch the report and list the three highest-priority recommendations.

### Client audit reports for agencies

Agencies auditing client sites can tag each audit with client_name and analyst_name, then pull the finished report's overall score, section scores, strengths and weaknesses from the professional opinion, and recommendations with platform-specific fixes to build a client deliverable.

Example prompt: Create an audit for a client URL with client_name 'Acme' and analyst_name 'Sam', then fetch the report and return the score, section scores, and the professional opinion headline.

### Quota-aware audit scheduling

Audits are billed by pages analyzed against a monthly page quota. Before a large crawl, an agent reads usage to see monthly_pages_remaining and available_for_next_audit, then sets max_pages so the audit fits the remaining quota.

Example prompt: Read usage, then create an audit with max_pages set to the smaller of available_for_next_audit and 200.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/audits` | Create an asynchronous audit |
| GET | `/audits` | List audits |
| GET | `/audits/{job_id}` | Read an audit |
| GET | `/audits/{job_id}/report` | Read a completed audit's report |
| POST | `/audits/{job_id}/cancel` | Cancel an audit |
| GET | `/usage` | Read quota and usage |

## Key resources

- **Audits** — Asynchronous site audits that can be created, listed by status, read, and cancelled
- **Reports** — The public report of a completed audit with scores, pages, checks, and recommendations
- **Usage** — Plan, monthly page quota, pages used, and quota reset time
- **Identity** — The current API key's id, name, scopes, and expiry

## AI readiness

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.

- **Score:** 71 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 65 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 56 / 100
- **View full report:** https://jentic.com/apis/limpiaudit.com/limpiaudit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Limpi by hand means sending a scoped bearer key, generating an Idempotency-Key for each audit, polling asynchronous jobs, and parsing RFC 9457 problem+json errors. Through Jentic you install once, import Limpi from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Limpi puts the audit id in the URL path (`/audits/{job_id}`), so a rule can pin your agent to one audit and its report. You choose the operations it may call, so ones like creating or cancelling audits are not included unless you add them.
- **Credential handling:** Your Limpi 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.
- **Discovery method:** Agents search Jentic by intent such as 'run an SEO audit' or 'get audit recommendations', and Jentic returns the matching Limpi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Ahrefs API** — Backlink, keyword, and site audit data
- **Moz Links API** — Link metrics and domain authority
- **PageSpeed Insights API** — Page performance and Core Web Vitals
- **Google Search Console API** — Search performance and indexing data from Google

## FAQ

### What authentication does the Limpi API use?

Per its OpenAPI spec the Limpi API uses HTTP bearer authentication: you send your Limpi API key in the Authorization header as a bearer token. Operations also name a required key scope, such as audits:read, audits:write, reports:read, or usage:read. Reading the OpenAPI contract itself needs no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at request time.

### Is there a Limpi MCP server?

You don't need an MCP server to give your agent the Limpi API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the audit, report, and usage operations on demand.

### Why does creating a Limpi audit need an Idempotency-Key?

Audit creation requires an Idempotency-Key header of 8 to 128 characters. If a request is retried with the same key, Limpi replays the original response and marks it with the Idempotency-Replayed header instead of starting a second audit, which protects your page quota.

### What are the rate limits for the Limpi API?

The OpenAPI spec does not state numeric limits. It declares an HTTP 429 response carrying Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, so read those headers for your current limits, and check https://limpiaudit.com for plan details.

### Can I limit what my agent is allowed to do with the Limpi API?

Yes. For example, write a rule that allows only the audit read and report operations for `/audits/abc123`, so the agent can follow one audit and summarize its report but cannot start new audits that spend your page quota or cancel running ones. Every call it makes is logged.

### How do I run an SEO audit with the Limpi API through Jentic?

Search Jentic for 'run an SEO audit', load the create audit operation, and pass the url with optional max_pages and max_depth plus an Idempotency-Key header. Poll the audit by its job_id until the status is completed, then fetch the report. To run it on your own infrastructure, install Jentic One from its GitHub repo.