Agent readiness.
One API call.
Build website audits into your own tools. Our free Agent Readiness API returns an explainable score, individual findings and actionable recommendations as JSON.
60 scans per account per hour. Need more? Talk to Barnabas.
URL → AgentReady → JSON
curl --max-time 60 https://adaptmypage.com/api/scan \
-H "Authorization: Bearer $AGENT_READY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","profile":"website"}'One bearer key for your server-side integration. Never put it in frontend code or public repositories.
Run your first scan
- Create a free account and make an API key in your API keys panel.
- Store that key on your server.
- Send it in the Authorization header with a public URL to POST /api/scan.
| Field | Meaning |
|---|---|
url | Required. Public HTTP(S) URL, up to 2,048 characters, without credentials, query parameters or fragments. |
profile | Optional. Default: auto. website, merchant, api, marketplace, mcp-server, agent-service. |
JavaScript / Node.js
const response = await fetch(
"https://adaptmypage.com/api/scan",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.AGENT_READY_API_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
url: "https://example.com",
profile: "website"
}),
signal: AbortSignal.timeout(60000)
}
);
const report = await response.json();
if (!response.ok) throw new Error(report.error.message);
console.log(report.score, report.findings);What does the Agent Readiness API check?
The open-source AgentReady scanner checks public discovery, policy, data and security signals. API, commerce, MCP server and agent-service checks depend on the selected profile.
- AI discovery: robots.txt, sitemaps, llms.txt and structured data.
- Access and trust: agent policies, support information and security indicators.
- Integration: machine-readable interfaces and profile-specific findings.
Passive alpha scan, not a certification: we do not execute JavaScript, purchases or complete agent tasks. MCP server discovery is not browser WebMCP verification. llms.txt is a proposed convention, not a guaranteed ranking factor.
Findings, not a black box
The response includes score (0–100), weighted category scores, findings with statuses, evidence and recommendations, and scan metadata. AgentReady’s original English findings and weights are preserved.
{
"agentreadyVersion": "0.1.0-alpha.0",
"profile": "website",
"score": 48,
"scores": [
{
"key": "discoverability",
"label": "Discoverability",
"score": 18,
"weight": 35,
"applicableFindings": 6
}
],
"findings": [
{
"id": "discoverability.robots_txt",
"title": "robots.txt is available",
"status": "warn",
"severity": "minor",
"category": "discoverability",
"evidence": [
{
"message": "/robots.txt not available (HTTP 404)."
}
],
"recommendation": "Publish robots.txt so automated clients can understand crawl preferences."
}
]
}Abbreviated example, not a live result. Category scores are points out of their weight—not all percentages.
pass · fail · warn · unknown · info · not_applicable
Unknown does not mean failed. A high score does not establish successful agent interaction.
Clear limits
- Every scan requires a bearer API key.
- Free accounts can make 60 scans per hour. Responses include
RateLimit-*headers. - At the limit, the API returns
429 rate_limit_exceededand tells you to contact barnabas@adaptmypage.com for higher limits. - Public HTTP(S) URLs only, up to 2,048 characters, with no credentials, parameters or fragments.
- Passive checks only: no JavaScript, forms, login or agent actions.
Only scan websites you are authorized to assess. Follow the returned HTTP status and error details.
Common questions
Is this an AI SEO or LLMO API?
It provides technical AI discovery and agent-readiness signals that you can use in SEO or LLMO audits. It does not measure rankings, citations or visibility in ChatGPT.
Does the API automatically make my website agent-ready?
No. The API audits and reports. Implementation and the experimental Agent Tag pilot are separate.
Are scan reports stored?
Reports are processed in memory for the response, not kept in a report archive. Accounts, key hashes and usage counters are stored. Technical provider logs may still be retained.
Can I use the API in n8n or an agent workflow?
Yes. Use an HTTP request step with POST, a JSON body and bearer authentication. Store the key in the tool’s credential store, not in a prompt. Our automation guide has worked examples for a batch script, an n8n schedule and a GitHub Actions check.
Automate your next audit.
Create an account, configure your key, check a URL, get JSON.
Create a free account & API key