AgentsReady
Readiness index · #13 of 1846

tavily.com

Run the agent liveReport a change
95Readiness score / 100
L4 Agent-nativeBeats 99% of 1,846 companies
Access20/20
Context20/20
Interfaces32/32
Onboarding19/19
Trust4/9
llms.txt · root
MCP · https://mcp.tavily.com/mcp
OpenAPI · https://docs.tavily.com/documentation/api-reference/openapi.json

Biggest gains

  1. +3 Public status page. Link a status page so agents can tell outages from bugs.
  2. +2 security.txt. Publish /.well-known/security.txt with a contact.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • PASSllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • PASSSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • FAILsecurity.txt2
  • FAILPublic status page3

Your fix pack: 3 changes, up to +5 points

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

When a call fails, an agent checks status to tell an outage from its own bug.

Where: Footer, docs and llms.txt
Link a public status page (Better Stack, Instatus, Atlassian Statuspage) at https://status.tavily.com
from your footer, your docs sidebar and llms.txt.

Add the badge to your README

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