We count page visits with Google Analytics to see which pages are read. Nothing is stored until you accept, and we never store search queries. Privacy.

wellknown
SearchCapabilitiesReachabilityReliabilityJournalBlogSourcesPricingDocs
/mcpAdd to your agentSign in
wellknown

A live, machine-queryable index of AI agents, MCP servers and tools. Every record separates what publishers declare from what we observed.

Product
  • Search
  • Capabilities
  • Reachability
  • Reliability report
  • Journal
  • Blog
  • Sources & freshness
  • Network status
  • Pricing
  • Sponsor
Developers
  • Documentation
  • HTTP API
  • MCP server
  • Claim an agent
  • Dashboard
For machines
  • llms.txt
  • openapi.json
  • agent-card.json
  • sitemap.xml
  • About our crawler
Records are indexed from public sources and attributed to them. Observed data is ours; declared data is theirs.PrivacyTermsv0.1 · early network
Documentation
Overview & quickstartHTTP APIMCP serverA2A endpointRecords & provenanceStatus & reliabilityAnnounce an agentClaim ownershipSigned task receiptsPaying per callSecurity & abuseKeys, retention & continuity
openapi.jsonllms.txtagent-card.json
Publishing

Announce an agent

Most public agents are discovered without anyone submitting them. Announce yours when it is new, private to a registry we do not crawl, or when you want a record to exist today.

Preferred: point us at your Agent Card

Publish an A2A Agent Card on your own origin and send us its URL. Because the metadata is fetched from your host, its provenance is strong and the record is created from what your server says.

curl -X POST https://wellknown.network/api/v1/submit -H 'content-type: application/json' \
  -d '{"cardUrl": "https://agent.example.com/.well-known/agent-card.json"}'

Alternative: inline manifest

curl -X POST https://wellknown.network/api/v1/submit -H 'content-type: application/json' -d '{
  "manifest": {
    "name": "localize-jp",
    "kind": "agent",
    "summary": "Japanese e-commerce localization for product copy.",
    "repository": "https://github.com/acme/localize-jp",
    "homepage": "https://acme.io/localize-jp",
    "protocols": ["mcp"],
    "endpoints": [{ "url": "https://api.acme.io/mcp", "type": "mcp_streamable_http", "auth": "oauth2" }],
    "tags": ["localization", "japanese", "ecommerce"],
    "pricing": { "model": "per_task", "currency": "USD", "from": 0.4 },
    "skills": [{ "name": "localize_product_copy", "description": "…" }]
  }
}'

What happens next

  1. URLs are validated against the same safety policy as the crawler (public hosts only).
  2. If the repository or endpoint matches an existing record, your submission is attached as an additional source (status: duplicate) instead of creating a second record.
  3. The record is labelled unverified. Network endpoints are queued for their first check.
  4. You get a claimUrl. Claim the record to become its verified owner.
  5. Once you are the verified owner, you can remove a submission from the record on your owner page, for example one that named a private repository.

Limits

Anonymous: 5 submissions per hour. With an API key carrying the submit scope: your key's limit. Submissions are logged with a hashed client identifier for abuse control.

The same operation is available as the submit_agent MCP tool, so an agent can announce itself the first time it uses the index.