canonical: https://jentic.com/apis/402registry.com/402registry

# 402registry

The 402registry API runs a pay-per-check audit of whether an AI crawler can actually see and read a given website, then lists the results in a public registry. Callers can browse the registry by category, read a single site's profile and report, request a free check, or buy additional checks and a machine-readable dataset. Checks and purchases are settled per call over the x402 protocol using USDC on Base, with no account or card required.

## For AI agents

Audit whether an AI crawler can see a website, browse the public registry of audited sites, and buy checks or reports paid per call over x402.

## Scope

Does not handle content rewriting, keyword research, or search-ranking reports. Use for auditing AI-crawler visibility of websites only.

## Capabilities

- Browse the public registry of audited sites, filtered by category
- Read one site's audit profile and discoverability report
- Request a free crawler-visibility check for a site
- Buy extra checks or a quick review, paid per call over x402
- Look up a site's status badge without payment

## Use cases

### Agent-Run Visibility Audit

A site owner wants to know whether AI crawlers can actually read their pages before investing in content. An AI agent requests a free check for the domain, reads back the resulting report, and summarizes whether the site is visible to crawlers and what is blocking it, all without the owner creating an account.

Example prompt: Request a free crawler-visibility check for a domain and read back the resulting report

### Competitor Discoverability Tracking

A marketing team tracks how discoverable competitor sites are to AI crawlers. The 402registry API lists audited sites by category and returns each site's profile, so an agent can browse the registry, pull profiles for the sites of interest, and compare their visibility over time.

Example prompt: Browse the registry for a category and pull the audit profile for each competitor site in it

### Paid Bulk Dataset Pull

A data team wants the whole registry as one machine-readable file to load into its own tooling. The 402registry API sells the full dataset and individual reports per call over x402, so an agent can pay for and download the dataset in a single automated step without a subscription.

Example prompt: Pay for and download the full registry dataset over x402 in one automated call

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/registry` | Browse the public registry of audited sites |
| GET | `/registry/{category}` | Browse audited sites by category |
| GET | `/site/{host}` | Read one site's audit profile |
| POST | `/submit` | Request a free discoverability check |
| GET | `/r/{id}` | Read a check report by id |
| GET | `/api/check` | Free badge lookup for a host |
| GET | `/badge/{host}` | Retrieve a site's status badge |

## Key resources

- **Registry** — Browse audited sites, by category or as a machine-readable list
- **Sites** — Read a single site's profile, report, and status badge
- **Checks** — Request a free check or buy additional checks and reviews over x402

## 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:** 52 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 48 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/402registry.com/402registry/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 402registry by hand means handling x402 micropayments in USDC on Base and polling check results yourself. Through Jentic you install once, import it from the API Directory, and your agent calls the audit and purchase operations directly.
- **Permission scoping:** You choose which 402registry operations your agent may call, so it can browse the registry and request free checks while the paid purchase operations stay out of the set unless you add them.
- **Credential handling:** 402registry needs no account, card, or key: its checks settle per call over x402. For any API you add that does use a key, your own Jentic One instance keeps it encrypted and injects it at execution time so it never reaches the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check if an AI crawler sees my site', and Jentic returns the matching 402registry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Semrush API** — Semrush measures search-engine SEO and rankings; 402registry measures whether AI crawlers can read a site.
- **Ahrefs API** — Ahrefs audits backlinks and organic search; 402registry audits AI-crawler discoverability and lists it in a registry.
- **Firecrawl API** — Firecrawl crawls and extracts a site's content; 402registry judges whether an AI crawler can see it in the first place.

## FAQ

### Does the 402registry API require authentication?

The 402registry API requires no API key or account, per its OpenAPI spec. The registry, site profiles, and a free check are open, and paid operations are settled per call over the x402 protocol using USDC on Base. There is nothing to sign up for before an agent can call it.

### Can I check whether an AI crawler sees my site?

Yes. The API accepts a request for a free discoverability check, returns a per-site report you can read by its id, and offers a free badge lookup for a host. An agent can request the check and read the report to see whether crawlers can read the site and what is blocking them.

### What are the rate limits for the 402registry API?

The OpenAPI spec does not define rate limits. Check the 402registry documentation at https://402registry.com for the current limits, since paid operations are metered per call over x402 rather than by a request quota.

### How do I audit a site through Jentic?

Import the 402registry API from the Jentic directory and give your agent an intent such as 'check if an AI crawler sees my site'. Jentic returns the check operation with its input schema, your agent submits the domain and reads back the report, and paid operations settle per call over x402. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the registry-browse and free-check operations, so your agent can audit sites and read reports but cannot trigger the paid purchase operations, and every call it makes is logged.

### Is there a 402registry MCP server?

You don't need an MCP server to give your agent 402registry. Jentic connects it directly from the API Directory: import it and your agent calls the audit and purchase operations. Paid checks settle per call over x402, with no key to manage.