deepsearch.app publishes an Agentic Resource Discovery manifest at
/.well-known/ai-catalog.json, declaring what an AI agent can call on this domain.
Everything below is read from that file. First seen by our crawler on 31 August 2026.
| Declared resource | Type |
|---|---|
| DeepSearch product briefnot yet checked What DeepSearch is, when an agent should reach for it, what it will not do, pricing, and an index of every public guide. endpoint: https://deepsearch.app/llms.txtidentifier: urn:air:deepsearch.app:doc:llmsllms-txt documentation trust identity: deepsearch.app | text/markdown |
| DeepSearch MCP servernot yet checked Streamable HTTP MCP server. Resolve a name, phone, email, or username to ranked candidate people, build a sourced dossier, and ask questions grounded in it. endpoint: https://deepsearch.app/.well-known/mcp/server-card.jsonidentifier: urn:air:deepsearch.app:mcp:deepsearchpublished to be found for: who is the person behind this email address · find the social profiles that belong to this username · verify a job candidate using public information · identify who called me from this phone number people-search osint identity-verification mcp search_people build_dossier ask_about_person trust identity: deepsearch.app | application/mcp-server-card+json |
| DeepSearch documentation MCP servernot yet checked4 verified tools Read and search DeepSearch's own documentation: the product manual, every published guide and blog post, the REST API reference, the legal pages, and the product brief. Every result cites the deepsearch.app URL it came from. Public, unauthenticated, and rea... endpoint: https://deepsearch.app/api/docs/mcpidentifier: urn:air:deepsearch.app:mcp:deepsearch-docspublished to be found for: what does DeepSearch cost · what can DeepSearch not see · how do I remove my information from DeepSearch · how do I authenticate against the DeepSearch API documentation mcp support api-reference read-only search_docs get_doc list_docs trust identity: deepsearch.app | application/mcp-server-card+json |
| DeepSearch REST APInot yet checked OpenAPI 3.1 contract for the public REST API: search, dossier, chat, reverse image, VIN, and async jobs. Bearer auth with a developer API key. endpoint: https://deepsearch.app/openapi.jsonidentifier: urn:air:deepsearch.app:api:deepsearchpublished to be found for: who is the person behind this email address · find the social profiles that belong to this username · verify a job candidate using public information · identify who called me from this phone number api openapi rest trust identity: deepsearch.app | application/vnd.oai.openapi+json;version=3.1 |
| DeepSearch people-search skillnot yet checked Research a real person's public online footprint with DeepSearch - resolve a name, phone number, email address, or username to ranked candidate people, build a fully sourced dossier, and ask follow-up questions grounded in it. Use when a task needs to ident... endpoint: https://deepsearch.app/.well-known/agent-skills/deepsearch-people-search/SKILL.mdidentifier: urn:air:deepsearch.app:skill:deepsearch-people-searchskill people-search how-to trust identity: deepsearch.app | application/ai-skill+md |
https://deepsearch.app/.well-known/ai-catalog.json, this publisher's own file.
Identifiers are reproduced exactly as published.
Note: this is the pre-v0.91 path. The specification renamed the manifest to /.well-known/ard.json, and most of the ecosystem still serves the older name.
None of these endpoints has been probed for reachability yet, so nothing here says whether they answer.
"Answers" and "no response" describe only whether an endpoint replied when last probed:
services go down and come back, and an entry is demoted rather than removed. None of this
is a trust, quality or safety rating.
https://neuronto.com/search, or connect an agent to https://neuronto.com/mcp.
If this is your domain, the free console shows what a registry
sees when it reads your manifest.