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.