Integration

Wiza integration

Wiza is a B2B contact data platform for sales and recruiting. Through this integration you can enrich one person from a LinkedIn profile URL, an email or a name plus company (work and personal emails, phone numbers, profile details), enrich a list of up to 2500 people, search prospects and companies with job, location, industry, size and funding filters, build prospect lists from those filters, enrich a company from its name, domain or LinkedIn id, look up accepted location and technology filter values, and read the remaining credits. Enrichment is asynchronous: start it, then read the reveal or list until its status is finished. Credits are spent only when data is found. The CSV export of list contacts and the webhook settings are not exposed. Authentication is a Wiza API key sent as Authorization: Bearer <key>.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Wiza.Built from the 13 Wiza tools below, on the connection you add once.

What you can do with Wiza

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Company, 2 operations

  • enrich_companyEnrich companyPOSTEnrich a company from its name, domain, LinkedIn id or LinkedIn slug (at least one): industry, size, revenue, funding, location and more, returned at once. Costs 2 API credits when data is found.
  • search_companiesSearch companiesPOSTSearch companies by industry, location, size, revenue, growth, funding, technologies and more. Returns the total and up to size companies; each returned company costs 0.5 API credits, size 0 returns only the count.

Enrichment list, 2 operations

  • create_enrichment_listCreate enrichment listPOSTCreate a list of up to 2500 people to enrich in bulk (asynchronous). Returns the list with data.id and data.status; read get_list until it is finished, then list_list_contacts for the results.
  • get_listGet listGETRead a Wiza list by id: data.status, data.finished_at (set once it is finished), the number of people and the credits used. Use it to follow a list from create_enrichment_list or create_prospect_list.

Prospect list, 2 operations

  • continue_prospect_listContinue prospect listPOSTAdd more profiles to a prospect list from its original search, picking up where it stopped (asynchronous). Read get_list until it is finished.
  • create_prospect_listCreate prospect listPOSTCreate a list of the prospects matching filters (the filters of search_prospects) and enrich up to max_profiles of them (asynchronous). Read get_list until it is finished, then list_list_contacts.

Contact, 1 operation

  • list_list_contactsList list contactsGETList the enriched contacts of a finished Wiza list: name, title, emails with type and status, phones, LinkedIn URL and company details. Choose the segment: people (all), valid or risky.

Credit, 1 operation

  • get_creditsGet creditsGETRead the credits remaining on the Wiza account: email, phone, export and API credits (email and phone credits may read unlimited).

Individual reveal, 1 operation

  • get_individual_revealGet individual revealGETRead an individual reveal by id: data.status (queued, resolving, finished, failed), data.is_complete, and the person's emails, phones, title, location, company details and the credits it used.

Location, 1 operation

  • search_locationsSearch locationsGETFind the exact location values accepted by the location and company_location filters of search_prospects, search_companies and create_prospect_list. Returns each key with its boundary (bucket) to use as b.

Person, 1 operation

  • reveal_personReveal personPOSTEnrich one person from a LinkedIn profile URL, an email, or a full name plus company or domain. Returns emails, phones and company details. Waits for the job and returns the finished result; gives up after 10 minutes.

Prospect, 1 operation

  • search_prospectsSearch prospectsPOSTCount the prospects (people) matching filters such as job title, location, company, industry or size, and optionally return up to 30 profiles (size), billed in API credits. Build the list itself with create_prospect_list.

Technology, 1 operation

  • search_technologiesSearch technologiesGETFind the technology slugs accepted by the technologies filter of search_prospects, search_companies and create_prospect_list. Returns slug and name.

Use Wiza from Claude Code, Cursor or Codex

Connect Wiza in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Wiza operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Wiza

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Wiza once

    Add your Wiza connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Wiza integration FAQ

What can you do with the Wiza integration?

LiveContext exposes 13 operations on Wiza, covering company, enrichment list, prospect list and contact.

Popular integrations

Browse the whole catalog