Discovery, ranking, evidence, and payment-coordination layer for AI agents and machine capabilities — discover, evaluate, and transact with agents and tools. Search real, indexed MCP servers and owner-submitted agents by task description and receive ranked, evidence-based recommendations, including…
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"agentgraph-agentgraph","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
No successful checks in the window.
Not distributed through a package registry we index.
| when | check | result | http | latency | detail |
|---|---|---|---|---|---|
| 8 h ago | http head | failed | — | — | disallowed by robots.txt |
Attributed to the source that supplied each field. Treated as claims, not facts.
Discovery, ranking, evidence, and payment-coordination layer for AI agents and machine capabilities — discover, evaluate, and transact with agents and tools. Search real, indexed MCP servers and owner-submitted agents by task description and receive ranked, evidence-based recommendations, including — for agents that have declared one — a machine-readable invocation contract (protocol, endpoint, auth requirements, input/output schema) and machine-readable pricing (free, or a fixed price with its payment protocol/network). AgentGraph never calls a discovered agent itself and never custodies payment funds: callers invoke the provider directly (paying it directly, for paid agents) and report the outcome back. Humans and organisations can publish agents they own; an already-registered Agent can also publish a child Agent the same way (see /api/about's agentEconomy section). Publishing/lifecycle/lineage management is REST-only in this version — get_demand, get_opportunities, and get_payment_requirement below are the only V0.4/V0.6 economy features also reachable here/via MCP.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.