Wiza integration for AI agents.
Wiza integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Wiza tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Wiza actions, managed and audited.
Your user connects Wiza once; your agent can then use Wiza to enrich contacts, reveal emails and phone numbers, manage lists, prospect searches, and API credits — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Wiza access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Wiza tools.
10 tools are generated from the published Wiza catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 10 tools. All published catalog entries are included in this page's server-rendered HTML.
- Get Individual Reveal
- Get the individual reveal by id.
- Individual Reveals
- Get List
- Get the list with the given id
- Lists
- Get List Contacts
- > Get contacts for a list. By default a json response is returned. To get a csv response, append `.csv` to the url path.
- Lists
- Get Credits
- Get the number of credits remaining in your account.
- Credits
- Company Enrichment
- > Enrich company data instantly. You can provide a company name, company domain, LinkedIn ID, or LinkedIn slug to get comprehensive company information. This endpoint returns company data immediately, including industry, size, revenue, funding information, location, and more. The enrichment costs 2 API credits per successful request. Credits are only charged when company data is successfully found and returned. Rate limits apply: 30 requests per minute, 43,200 requests per day.
- Company Enrichment
- Start Individual Reveal
- > Start an individual reveal. An individual reveal is a single contact enrichment. You can provide a name, company, and domain, or an email, or a LinkedIn profile URL. > Either `company` (company name) or `domain` is required when using contact details. Once the reveal is completed, an update will be posted to the webhook URL as configured in your [ account settings ]( http://wiza.co/app/settings/api ). The payload will be the same as the response of the Get Individual Reveal endpoint. If you wish to do added authentication, the headers in the webhook request will include `x-auth-key` which will be a SHA256 hash of your api key. You can get the status of the individual reveal by calling the `GET /api/individual_reveals/:id` endpoint.
- Individual Reveals
- Create List
- > Create a list of people to enrich. Once the list is completed, an update will be posted to the webhook URL as configured in your [ account settings ]( http://wiza.co/app/settings/api ). The payload will be the same as the response of this endpoint. If you wish to do added authentication, the headers in the webhook request will include `x-auth-key` which will be a SHA256 hash of your api key. You can get the status of the list by calling the `GET /api/lists/:id` endpoint. And you can get the contacts by calling the `GET /api/lists/:id/contacts` endpoint. **Note:** Please check the status of the list as it may fail sometimes due to LinkedIn rate limiting.
- Lists
- Continue prospect search
- Continue with your previous search
- Prospect Lists
- Create prospect list
- Create a list of prospects that match your filters
- Prospect Lists
- Prospect search
- Find the number of prospects that match your search filters
- Prospect
Wiza integration, answered
- How do AI agents use Wiza through Open Connector?
- Your user connects Wiza once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Wiza tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Wiza MCP server?
- Yes. Open Connector can serve Wiza as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Wiza actions with credentials injected server-side.
- Where do Wiza credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Wiza — keep the keys.
Open source, self-hostable, with Wiza credentials that never leave your infrastructure. Run it from source today.