1. Create your free account
Open API keys in your dashboard. Create a read-only key to try company search.
Create free accountFind companies, trace ownership and read saved reports from Claude, ChatGPT and your AI agents. Connect Zavia, ask a question, get the underlying evidence.
Open API keys in your dashboard. Create a read-only key to try company search.
Create free accountChoose your client below. Copy the server URL and follow its authentication steps.
See setup stepsAsk “Check my Zavia usage”, then search by company name and country. Searches share your API/MCP allowance.
Copy an example promptClaude, ChatGPT, Gemini CLI, Microsoft Copilot Studio and Cursor.
In Claude, open Customize → Connectors → Add custom connector. Name it Zavia and paste the server URL below.
Choose “No sign in” under Authentication. In Request headers, add Authorization with the value Bearer YOUR_ZAVIA_API_KEY. Use a read-only key to test the connection.
Add and enable the connector in your conversation. Ask “Check my Zavia usage” to verify access without running an investigation.
https://connect.zavia.ai/mcpAuthorization: Bearer YOUR_ZAVIA_API_KEYCreate your key in Dashboard → API keys. Enter it in your client’s credential settings, never in a chat message. Workspace administrators may need to allow custom connectors.
Use a ChatGPT account with access to this Zavia Site. This managed connection is separate from the self-service API-key endpoint.
Open ChatGPT Plugins, choose Add custom MCP server, and paste the managed URL below. Select OAuth, complete sign-in, then review and install the discovered tools.
Enable Zavia in your conversation and ask “Check my Zavia usage”. If you need workspace access, contact us using the link below.
https://zavia-homepage-redesign.sens663.chatgpt.site/mcpChatGPT cannot send your Zavia API key as a custom header. The managed URL uses sign-in and Site access permissions. Creating a free Zavia account does not automatically grant access to this connection.
Request ChatGPT accessCreate a Zavia API key, then open your user configuration at ~/.gemini/settings.json.
Merge the configuration below into the file. Replace YOUR_ZAVIA_API_KEY locally with your key. Keep this file out of version control.
Restart Gemini CLI and run /mcp to check the connection. Ask “Check my Zavia usage”. This setup is for Gemini CLI, not the consumer Gemini chat app.
https://connect.zavia.ai/mcp{
"mcpServers": {
"zavia": {
"httpUrl": "https://connect.zavia.ai/mcp",
"headers": {
"Authorization": "Bearer YOUR_ZAVIA_API_KEY"
}
}
}
}Create your key in Dashboard → API keys. Enter it in your client’s credential settings, never in a chat message. Workspace administrators may need to allow custom connectors.
Open your agent in Copilot Studio. Go to Tools → Add a tool → New tool → Model Context Protocol.
Name the server Zavia and paste the URL below. Choose API key authentication, Type: Header, and header name: Authorization.
Create a connection with Bearer YOUR_ZAVIA_API_KEY as the credential value. Add the server to your agent and test “Check my Zavia usage”. This uses Copilot Studio; it is not a paste-in connection for consumer Copilot chat.
https://connect.zavia.ai/mcpAuthorization: Bearer YOUR_ZAVIA_API_KEYCreate your key in Dashboard → API keys. Enter it in your client’s credential settings, never in a chat message. Workspace administrators may need to allow custom connectors.
Set ZAVIA_API_KEY in the environment used to launch Cursor.
Merge the JSON below into .cursor/mcp.json in your project. The key is read from the environment rather than committed in the file.
Open Cursor’s MCP settings, enable Zavia and check its tools. Ask the agent “Check my Zavia usage”.
https://connect.zavia.ai/mcp{
"mcpServers": {
"zavia": {
"url": "https://connect.zavia.ai/mcp",
"headers": {
"Authorization": "Bearer ${env:ZAVIA_API_KEY}"
}
}
}
}Create your key in Dashboard → API keys. Enter it in your client’s credential settings, never in a chat message. Workspace administrators may need to allow custom connectors.
These are the tools exposed by the Zavia MCP server today.
zavia_search_companiesMatching legal entities and company IDs. Search by name, registration number or VAT number, with a country.
zavia_investigate_companyShareholders, ownership chains, calculated interests and available UBO evidence for your confirmed company. A new report requires paid credit and an investigation-enabled key.
zavia_list_investigationsRecent ownership reports saved in your workspace, so your agent can pick up existing research.
zavia_get_investigationThe saved report’s ownership paths, sources, dates, calculations and evidence gaps. No additional report credit.
zavia_get_usageRemaining search and report allowances, reset times and request limits. Use this to test your connection without searching.
Available ownership fields vary by company and jurisdiction. The server returns gaps when evidence is missing. Financials, sanctions screening and monitoring are not separate tools in this MCP connection.
Find Global Data Intelligence Limited in the United Kingdom. Show the matching company IDs and registration details. Ask me to confirm the company before investigating ownership.Investigate ownership of the company I selected. Find beneficial owners above 25%, show the ownership paths, and include source dates and any missing evidence.List my saved Zavia investigations. Open the report I select and summarise its shareholders, ownership calculations and unresolved branches.A free Zavia account includes API-key creation and three company searches per day shared across API and MCP. Usage checks and reading saved reports do not consume a new report credit. New ownership investigations require paid credit.
Yes. Every client using that key shares the same workspace and allowance. You can create separate keys for different clients, with up to five active keys. The data request limit is one request per second per workspace.
ChatGPT uses the separate managed sign-in connection shown in its setup tab. It requires access to this Zavia Site and permission to connect custom MCP servers in ChatGPT. The self-service API-key endpoint does not provide OAuth.
The tool returns a run ID and retry delay. The agent should resume that same run after the delay, using the same inputs. This avoids starting a duplicate investigation.
Create your account, get your key, and try three company searches per day.