Shows which AI crawlers and agents a site lets in: robots.txt rules per agent for a given path, llms.txt, noai page tags and AI usage signals, with a plain verdict for each.
curl -X POST "https://api.primaryapi.com/v1/run/site.ai_access" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.nytimes.com/section/technology"}'{
"output": {
"found": true,
"data": {
"origin": "<string>",
"path": "<string>",
"robotsTxt": {
"httpStatus": "<integer | null>",
"groups": "<integer>",
"status": "<ok | not_found | unreachable | red…",
"aiTrainingPreference": "<disallowed | allowed | null>", …
},
"llmsTxt": {
"title": "<string | null>",
"present": "<boolean>",
"url": "<string>"
}, …
}
},
"credits": 1
}Input and output
3 fields
https://www.nytimes.com/section/technol….9 fields
Good to know
Follows RFC 9309. The most specific matching rule wins (Allow on a tie), the * group applies only to agents without their own group, a 4xx robots.txt means no restrictions and a 5xx or unreachable one means complete disallow.
A host that does not resolve is a free miss. A miss is an answer, not an error, and it costs nothing.
robots.txt is a request, not an access control.
Output is stable between runs. So a monitor fires only when a rule, file or tag changes.
The same key and credits work for every API.