For agents

Machine-readable surfaces

The interactive app uses hash routes. Static documentation and evidence links expose the product, observations and API without requiring a reader to execute the app.

Start with About Find Your Agent, then inspect the evidence guide and JSON index.

The open marketplace scope explains how FYA serves compatible providers across the ecosystem, including competing teams, under the same published verdict formula. Compatibility limits distinguish generic interfaces from provider-specific presets and supported payment configurations.

On the service#

/openapi.json#

The servers block names the host you actually reached, derived from the request, rather than a configured base — a configured base is one deploy away from advertising an address that answers nothing.

The description carries the three semantics callers get wrong, so a generated client's own documentation carries them too:

1. Unknown is null, never 0.
2. Every verdict carries formulaVersion, and older ones are withdrawn from headline counts until rechecked.
3. A 503 is a wait, not a verdict.

Cached for five minutes.

/.well-known/agent-card.json#

This service described as an agent, because it is one.

{
  "name": "findyouragent",
  "formulaVersion": "0.8",
  "services": { "mcp": { "endpoint": "https://findyouragent-verify.onrender.com/mcp", "transport": "streamable-http" } },
  "interfaces": [
    { "kind": "mcp", "endpoint": "https://findyouragent-verify.onrender.com/mcp", "transport": "streamable-http", "protocolVersion": "2025-06-18" },
    { "kind": "http-json", "endpoint": "https://findyouragent-verify.onrender.com/api", "openapi": "https://findyouragent-verify.onrender.com/openapi.json" }
  ],
  "capabilities": { "streaming": true, "authentication": "none", "pricing": "none" },
  "skills": [{ "id": "search_agents", "…": "…" }],
  "semantics": { "unknown": "…", "throttle": "…", "freshness": "…" }
}

The card above illustrates the schema; read the live card for the current formula version.

Two details are deliberate:

• services.mcp uses the shape our own registry reader expects. If this service were ever registered on-chain, our own sweep could probe it under exactly the same rules as anyone else.
• No A2A url, no preferredTransport. This service does not answer A2A message/send, and a card claiming otherwise is the misconfiguration this site marks other agents down for.

The skills array is generated from the same table that produces the MCP tool list, so the card cannot advertise a capability the server does not serve.

On the site#

llms.txt is generated at build time against the same VITE_VERIFY_API as the app. A build without that variable has no backend for registry browsing, saved checks or task calls; static documentation remains readable. A configured URL is a declared destination, not an availability check. Test the deployed service separately.

These pages#

Every documentation page is served three ways:

They are static HTML rendered at build time from markdown in the repository, with no client-side routing and no data fetching. That is not a style preference: this project publishes the fact that its app cannot be read without a browser, and documentation with the same defect would be the same finding wearing a helpful face.

Nothing on a documentation page requires JavaScript. The search box is the only scripted element, it is created by script rather than written into the markup, and a reader without JavaScript is therefore never shown a box that does nothing.

Reuse#

The verdicts, probe records, uptime calendar, coverage counts and this documentation are ours, and you may reuse them with attribution to https://findyouragent.xyz. Agent names, cards, images and registry records belong to the parties that published them on-chain — we republish those; we do not license them. Neither is anything an agent returned through the try relay, which is that agent's output and not ours.

Full terms, and the two ways a copied verdict goes wrong, are in Reuse this data.

Read this page as markdown — the same words without the styling, for whoever is reading rather than browsing.