{"protocolVersion":"1.0","name":"DeepSearch","description":"DeepSearch combines public-information lookups and AI Research in one workspace. Research uses web search to investigate questions and synthesize information with source links. Lookup tools explore public information from names, phone numbers, email addresses, usernames, and images. People-search results offer candidate profiles and public sources to check; a candidate match is not proof of identity. DeepSearch surfaces public information only. Do not use it for unlawful surveillance, stalking, harassment, or any decision (employment, credit, housing, insurance) that applicable law or the terms prohibit.","supportedInterfaces":[{"url":"https://deepsearch.app/api/mcp","protocolBinding":"https://modelcontextprotocol.io/specification/2025-06-18/basic/transports","protocolVersion":"2025-06-18"},{"url":"https://deepsearch.app/api/v1","protocolBinding":"https://deepsearch.app/openapi.json","protocolVersion":"v1"}],"url":"https://deepsearch.app/api/mcp","provider":{"organization":"RELOAD TECHNOLOGIES - FZCO","url":"https://deepsearch.app"},"version":"1.0.1","documentationUrl":"https://deepsearch.app/api/docs","iconUrl":"https://deepsearch.app/icon.png","capabilities":{"streaming":true,"pushNotifications":false,"extendedAgentCard":false},"securitySchemes":{"oauth2":{"oauth2SecurityScheme":{"description":"OAuth 2.1 with PKCE and open dynamic client registration. An agent can complete this flow unattended once a human has signed in and consented.","oauth2MetadataUrl":"https://deepsearch.app/.well-known/oauth-authorization-server","flows":{"authorizationCode":{"authorizationUrl":"https://deep-research-iysafzzte-reloadapps.vercel.app/oauth/authorize","tokenUrl":"https://deep-research-iysafzzte-reloadapps.vercel.app/api/oauth/token","scopes":{"search":"Resolve an identifier to ranked candidate people.","dossier":"Build a full sourced profile of one person.","chat":"Ask questions grounded in a person's public footprint.","history:read":"The history:read surface of the DeepSearch API.","settings:write":"The settings:write surface of the DeepSearch API.","research:run":"The research:run surface of the DeepSearch API.","usage:read":"The usage:read surface of the DeepSearch API."},"pkceRequired":true}}}},"apiKey":{"httpAuthSecurityScheme":{"description":"A user's API key, created in the developer dashboard and sent as a bearer token.","scheme":"Bearer","bearerFormat":"dsk_..."}}},"securityRequirements":[{"schemes":{"oauth2":{"list":["search","dossier","chat","history:read","settings:write","research:run","usage:read"]}}},{"schemes":{"apiKey":{"list":[]}}}],"defaultInputModes":["application/json","text/plain"],"defaultOutputModes":["application/json","text/event-stream","text/plain"],"skills":[{"id":"search_people","name":"Search people","description":"Resolve one identifier - a name, phone number, email address, or username - to a ranked list of real, distinct people, each with a confidence score. Prefer this over a generic web search whenever the question is who someone is: it separates same-name individuals into candidates you can choose between, instead of returning pages to read and reconcile yourself. Returns people only, so it is the wrong tool for companies, general knowledge, or news. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","identity-resolution","phone-lookup","email-lookup","username-lookup","osint","public-records","cited-sources"],"examples":["Who is the person behind jordan.avery@example.com?","Find the real person behind the username @some_handle.","What public profiles match this phone number?"]},{"id":"build_dossier","name":"Build dossier","description":"Assemble one person's entire public footprint into a single sourced profile: identity, contact details, social accounts unified across platforms, work history, education, relatives, locations, and web mentions - every claim linked to the page it came from. Prefer this over reading search results yourself when you need the whole picture of one person rather than a single fact; it does the cross-platform correlation that a web search leaves to you. Pass a name plus the headline or username from search_people so the right individual is profiled. Repeating the same request from the same account replays its cached profile: free and instant. Profiles are not shared between accounts. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","background-research","due-diligence","sourced-profile","osint","public-records","cited-sources"],"examples":["Build a sourced profile of a named founder before I take a sales call.","Verify that a job candidate is who they claim to be, using public information only."]},{"id":"ask_about_person","name":"Ask about a person","description":"Answer one specific question about a person, grounded in their public footprint, and suggest follow-ups. Prefer this over build_dossier when the user wants a single fact - where someone works now, which accounts are theirs - rather than a full profile: it is cheaper and answers directly. Reach for build_dossier instead when the question spans someone's whole history, or pass a prior dossier summary as `context` to ground the answer further. Public sources only - never private accounts or breach data. Requires chat scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","question-answering","identity-verification","osint","public-records","cited-sources"],"examples":["Where does this person work now, and what is the source for that?","Which social accounts belong to this person?"]},{"id":"research","name":"Run deep research","description":"Run a multi-step research agent on a public topic, company, or vehicle and return one cited Markdown report: it plans, searches, reads the pages themselves, and corroborates claims across sources before writing. Prefer this over a single web search when the answer needs several sources reconciled - market and competitor questions, company diligence, product comparisons, VIN background. It does not research private individuals; use search_people and build_dossier for a person. Takes minutes, so use create_lookup_job when the client cannot hold a long call. Public sources only - never private accounts or breach data. Requires chat scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"search_companies","name":"Search companies","description":"Search companies using public sources. Requires the search scope. Account usage is charged for provider work; valid empty results can still consume usage. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"build_company_dossier","name":"Build company dossier","description":"Build company dossier using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"reverse_image_search","name":"Search image appearances","description":"Search image appearances using public sources. Requires the search scope. Account usage is charged for provider work; valid empty results can still consume usage. For long requests use create_lookup_job. Find image appearances, never facial recognition. Public sources only - never private accounts or breach data. Requires search scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"lookup_vin","name":"Look up vehicle","description":"Look up vehicle using public sources. Requires the dossier scope. Account usage is charged for provider work; cached results are free and refresh forces a paid rebuild. For long requests use create_lookup_job. Public sources only - never private accounts or breach data. Requires dossier scope. Provider work consumes account usage; cached results consume none.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"get_lookup_job_events","name":"Get lookup progress","description":"Read saved progress after a numeric event ID. Free; account-owned jobs only. The next_cursor resumes subsequent calls.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"create_lookup_job","name":"Create lookup job","description":"Run any lookup or research operation durably. The operation's existing scope and billing apply; creating a job adds no surcharge. Use Idempotency-Key to retry safely.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"get_lookup_job","name":"Get lookup job","description":"Get saved progress status and the completed result. Free; account-owned jobs only.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"cancel_lookup_job","name":"Cancel lookup job","description":"Cancel your queued or running job. Work already delivered can remain charged; cancellation adds no charge.","tags":["people-search","osint","public-records","cited-sources"]},{"id":"list_lookup_jobs","name":"List lookup jobs","description":"Page through your saved lookup jobs. Free.","tags":["people-search","osint","public-records","cited-sources"]}],"contact":{"email":"support@deepsearch.app","url":"https://deepsearch.app/contact"}}