STEADYWRK · Agent discovery
How agents find STEADYWRK.
TL;DR
Agents discover STEADYWRK on eight public paths (llms.txt, llms-full.txt, ai.txt, agents.json, mcp.json, ai-plugin.json, openapi.yaml, oauth-protected-resource). The scored sample is Index Edition 3. Machine JSON is /api/public/agent-discovery. Operate the live engine at /operate — dispatch figures stay on /evals as estimated:true canonical estimates, not on this page.
This URL is the human hub. It does not rank the web. Completeness scores live on Index Edition 3. Operational dispatch numbers live only in canonical-metrics and the public dispatch.evals feed.
Eight public paths
A hit is HTTP 200 plus a matching content-type. Presence is not quality. ai-plugin.json is counted because agents still probe it.
| Path | Accept |
|---|---|
| /llms.txt | text/plain, text/markdown |
| /llms-full.txt | text/plain, text/markdown |
| /ai.txt | text/plain, text/markdown |
| /agents.json | application/json |
| /mcp.json | application/json |
| /.well-known/ai-plugin.json | application/json |
| /openapi.yaml | text/yaml, application/yaml, application/x-yaml, text/plain |
| /.well-known/oauth-protected-resource | application/json |
Operate the engine yourself
Your browser fires real dispatch.evals (read) and dispatch.quote (read-only estimate) against production /api/mcp. No order is committed. No PII is collected. The scorecard is estimated:true — recompute it at /evals.