agent.ai
agent.ai
Scanned 6/7/2026, 3:15:32 PM
How to access agent.ai as an agent
- ○Identify yourself at the edge before doing anything else
This site is protected by bot management. Anonymous scans see nothing because every request is challenged or blocked. Even if you have valid OAuth or API credentials, you'll need to either (a) be on the operator's allowlist, (b) sign your requests via Web Bot Auth so the bot-management product can recognize you, or (c) request inclusion in the verified-bots / signed-agents directory the operator uses.
- ○Respect explicit crawler block
robots.txt disallows known AI crawlers. Do not crawl with those user-agents. Look for a partner / data-licensing path before automating.
- ○Check for an undocumented developer API
No OpenAPI at the standard paths. Look for /developer, /developers, /docs, /api for hand-authored documentation.
https://agent.ai/developers - ●Register an OAuth application
OAuth/OIDC discovery is published. Register a client, pick narrow scopes, implement signature verification on webhooks.
https://agent.ai/.well-known/oauth-authorization-server - ●Talk to the A2A agent directly
An agent-card is published - your agent can call this site's agent via A2A.
https://agent.ai/.well-known/agent-card.json - ○Publish your own agent identity
Generate an Ed25519 keypair, host a public key directory, sign your HTTP requests (Web Bot Auth), apply to Cloudflare's bots & agents directory if you cross their edge.
https://developers.cloudflare.com/bots/concepts/bot/verified-bots/ - ●Respect robots.txt and Content Signals
Even when you are an approved agent, honor the site's policy preferences. Cache them; refresh weekly.
What we found
| Signal | Status | Evidence | Points |
|---|---|---|---|
| blocked_by_bot_management | found Edge-protected by Cloudflare Bot Management. cf-mitigated="challenge" (status 403). The scanner can only see what reaches the application - if you protect with bot management, expect agents to be unable to discover your well-known files even if you publish them. | agent.ai/ | -20 |
| llms_txt | found Title: "Agent.ai" · 9 sections · 0 links | agent.ai/llms.txt | +5 |
| a2a_agent_card | found Agent.ai · 7 skills | agent.ai/.well-known/agent-card.json | +25 |
| oauth_discovery | found OAuth/OIDC discovery document present | agent.ai/.well-known/oauth-authorization-server | +12 |
| robots_allows | found 33 UA rules · sitemap: yes | agent.ai/robots.txt | +4 |
| blocks_automation | found Explicit Disallow for: gptbot, ccbot, bytespider, amazonbot, diffbot | agent.ai/robots.txt | -30 |
| ai_plugin_json_legacy | found Legacy OpenAI plugin manifest present (deprecated signal) | agent.ai/.well-known/ai-plugin.json | 0 |
Show 9 signals not present
- · llms_full_txt (+3 if found)
- · agents_txt (+6 if found)
- · agents_json (+15 if found)
- · agents_md (+4 if found)
- · openapi (+18 if found)
- · content_signals (+5 if found)
- · mcp_registry (+25 if found)
- · in_llms_txt_hub (+0 if found)
- · in_agent_friendly_directory (+4 if found)
If you own this site
Concrete moves that would raise agent.ai's AgentRank:
- →Publish /agents.txt declaring which agent protocols you support.
- →Publish /AGENTS.md with human-readable agent instructions.
- →Publish your API as OpenAPI 3.x at a discoverable location.