Sourced research in the AI tools you use.
MCP
Connect your assistant
Let ChatGPT, Claude or your editor search people and companies, then build a sourced report for the match you choose.
Learn moreCLI
Work from your terminal
Run a lookup with one command. Send structured JSON to your scripts and CI.
Learn moreSkills
Repeat a careful workflow
Give your agent instructions that compare candidates, keep identities apart and cite every source.
Learn more
Assistants
- ChatGPTLook people and companies up from a ChatGPT conversation.
- ClaudeAdd DeepSearch as a custom connector and research from any chat.
- PerplexityBring sourced lookups into Perplexity with a remote connector.
- GrokAdd DeepSearch as a custom connector in Grok.
- Le ChatConnect DeepSearch to Mistral's Le Chat as a custom MCP connector.
Developer tools
- Claude CodeGive Claude Code sourced lookups and the DeepSearch skills.
- CodexLet your coding agent research people and companies with sources.
- CursorKeep public-source research one prompt away in Cursor Agent.
- GitHub CopilotAdd DeepSearch tools to Copilot Chat in VS Code.
- Gemini CLIResearch from the Gemini command line with cited answers.
Your account. Your permissions.
Every connection runs on your DeepSearch account, with the access you approve. Pick a way in and try the same lookup.
Use DeepSearch to find public profiles for Ada Lovelace. Show me the distinct candidates first, then build a sourced report for the one I choose.Connected on your terms.
Choose your connection
Sign in with OAuth from an assistant or editor, or create an API key for the terminal.
Look before you spend
Searches return distinct candidates. A full report runs only for the one you choose, and cached reports replay for free.
Keep the receipts
Every fact in a report links to the public page it came from, so you can check it instead of trusting it.
Common questions
Which connection should I use?
Use MCP when your assistant or editor supports it: ChatGPT, Claude, Cursor, Codex and many others do. Use the CLI for terminals, scripts and CI. Skills add a careful research workflow on top of the MCP connection.
Do I need a DeepSearch account?
Yes. Lookups run on your DeepSearch account and draw on its included usage and any extra credits. An agent cannot pay or subscribe for you. To test an integration first, the public sandbox key dsk_test_deepsearch returns fixed sample results without an account.
What does a lookup cost?
Each surface shares your account's included usage. Searching returns candidates first, so a full report only runs for the person or company you choose. Replaying a cached report is free, and reading or cancelling a job costs nothing.
What can DeepSearch see?
Public sources only: profiles, registries, the open web and similar public records. DeepSearch never reaches into private accounts, messages or breach data.
Is the person I look up notified?
No. Lookups read public sources and nothing is sent to the person, number, email or account you search. Anyone can remove themselves from DeepSearch results for free.
Can I use results to decide on a job, a lease or credit?
No. DeepSearch is not a consumer reporting agency, and its results must not be used for employment, housing, credit or insurance decisions.
Is there a local server?
No. DeepSearch runs as one hosted MCP server at https://deepsearch.app/api/mcp. Any client that can reach that address over HTTPS can connect, on your computer or in the cloud.
How do I revoke access?
Every assistant you connect appears under Connected apps in your developer settings, where you can disconnect it. API keys are revoked from the same page. Signing an app back in creates a new connection.