New64 developer platforms, traced by hand: how long it takes an agent to get an API keySee the benchmark →
AgentsReady
Readiness index · #1055 of 1846

goldbelly.com

Run the agent liveReport a change
33Readiness score / 100
L1 Agent-readableBeats 42% of 1,846 companies
Access6/20
Context0/20
Interfaces16/32
Onboarding11/19
Trust0/9
MCP · https://api.goldbelly.com/mcp

Biggest gains

  1. +10 Agents get the real page, not a bot wall. Serve the homepage to AI user-agents (Claude-User, ChatGPT-User) without a challenge or 403.
  2. +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
  3. +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
  • FAILAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • FAILContent is server-rendered4
  • FAILllms.txt exists8
  • FAILllms-full.txt exists3
  • FAILDocs available as markdown6
  • FAILSitemap2
  • FAILStructured metadata1
  • FAILPublic developer docs4
  • FAILMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • FAILSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • FAILFree tier or test mode3
  • FAILAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 16 changes, up to +67 points

Each change is ready to paste, filled in for goldbelly.com, with a command to check it worked. Or hand the whole list to your coding agent.

Your homepage returned a challenge or 403 to a Claude-User agent. Agents acting for a person give up and pick a competitor.

Where: Your WAF or bot-management rules (Cloudflare, Akamai, Vercel Firewall, AWS WAF)
Cloudflare: Security > WAF > Custom rules > Create rule
  Name: Allow user-triggered AI agents
  Expression:
    (http.user_agent contains "Claude-User") or (http.user_agent contains "ChatGPT-User")
    or (http.user_agent contains "Perplexity-User") or (http.user_agent contains "OAI-SearchBot")
    or (http.user_agent contains "Claude-SearchBot")
  Action: Skip > All remaining custom rules, Super Bot Fight Mode, Browser Integrity Check

Also in Security > Bots: turn on "Allow verified bots".
Keep rate limits on; only the challenge page is the problem.
Check it worked:curl -s -o /dev/null -w "%{http_code}\n" -A "Claude-User/1.0" https://goldbelly.com/ # expect 200

Want the full treatment, not just these fixes? Get the prompt that takes your coding agent through every phase.

Add the badge to your README

AgentsReady badge for goldbelly.com
[![AgentsReady](https://agentsready.dev/badge/goldbelly.com)](https://agentsready.dev/c/goldbelly.com)