Integration

ApexVerify integration

ApexVerify checks B2B contact data. Verify one email address or phone number in real time (deliverability, quality, role, disposable and catch-all flags for emails; line type, live network status, porting and operator for phones), or verify a whole list as a batch: upload a text file with one entry per line, set the verification parameters, prepare it to see the credit cost, launch it, poll its status and download the results as an XLSX spreadsheet. Read the account's remaining email and phone credits. The JSON batch export (an object keyed by each email or phone) and the file format normalization route are not exposed. Rate limit: 180 requests per minute. Authentication is an API key sent in the X-API-Key header.

Connect ApexVerify How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with ApexVerify

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.

Batch, 7 operations

delete_batchDelete batchDELETEDeletes a batch before or after verification, but not while verification is in progress.
get_batch_statusGet batch statusGETReturns a batch's status (parsing_content, ready_for_verification, verification_ongoing, verification_done or internal_error) with its parsing summary and cost once ready, and stats once done. Poll it after launch_batch_verification.
launch_batch_verificationLaunch batch verificationPOSTStarts verifying a batch whose status is ready_for_verification and charges its net cost in credits (402 if insufficient). Returns status: ok, not_ready_for_verification, verification_already_ongoing, verification_already_done or error.
list_batchesList batchesGETLists the account's batches with their batch_uuid, name, description, status and creation date. status is one of parsing_content, ready_for_verification, verification_ongoing, verification_done or internal_error.
prepare_batchPrepare batchPATCHParses the uploaded file with the current parameters and calculates the cost; can be repeated after update_batch_parameters. Returns status ok, parse_error or error; then poll get_batch_status until ready_for_verification.
update_batch_parametersUpdate batch parametersPUTSets a batch's verification parameters before launch; can be called repeatedly. type and target_country are required. Call prepare_batch afterwards to recalculate the content summary and cost.
upload_batchUpload batchPOSTUploads a UTF-8 .txt file with one email or phone per line (no header, no commas) and creates a batch. Returns status (ok, parse_error or error) and the batch_uuid; then call update_batch_parameters or prepare_batch.

Credit, 1 operation

get_account_creditsGet account creditsGETReturns the account's remaining credits, separately for email verifications (email_credit) and phone verifications (phone_credit).

Detail, 1 operation

get_batch_detailsGet batch detailsGETReturns everything about a batch: name, description, status, parameters, and, depending on the status, the parsing summary (found_content), the credit cost (found_cost) and the aggregate results (stats).

Export, 1 operation

export_batch_resultsExport batch resultsGETDownloads the results of a batch whose status is verification_done as an XLSX spreadsheet file: one row per verified entry with every result field, and a summary statistics sheet.

Unit, 1 operation

verify_contactVerify contactPOSTVerifies one email address or phone number in real time (up to about 5 seconds) and consumes verification credits (402 when they run out). Returns status (ok, empty, parse_error or error) and, when ok, verification_result.

Use ApexVerify from Claude Code, Cursor or Codex

Connect ApexVerify in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its ApexVerify 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 ApexVerify

Create your workspace
Sign up free. Nothing to install.
Connect ApexVerify once
Add your ApexVerify connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.