resolve_domain_batch

Pack: company-domain · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/resolve_domain_batch for the schema, then POST the same URL with its arguments for the data.

resolve_domain for up to 100 company rows in one call.

Tool description as the model sees it

Batch version of resolve_domain — resolve up to 100 company names in ONE call instead of looping single calls. Same per-source evidence shape as resolve_domain for every row, plus aggregate verified_count / not_found_count. A row that itself throws (e.g. empty name) is reported with error set rather than failing the whole batch.

Parameters

NameTypeRequiredDescription
rowsarraynoUp to 100 rows, each shaped like resolve_domain’s arguments: {name, city?, state?, country?}. _chApiKey/_serpApiKey/_serpProvider apply per row if you include them on that row.
argumentsunknownno
itemsobjectno

Example call

Arguments

{
  "rows": [
    {
      "name": "Apple Inc"
    },
    {
      "name": "Siemens AG",
      "country": "DE"
    }
  ]
}

curl

curl -X POST https://gateway.pipeworx.io/company-domain/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"resolve_domain_batch","arguments":{"rows":[{"name":"Apple Inc"},{"name":"Siemens AG","country":"DE"}]}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('resolve_domain_batch', {
  "rows": [
    {
      "name": "Apple Inc"
    },
    {
      "name": "Siemens AG",
      "country": "DE"
    }
  ]
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the company-domain pack
{
  "mcpServers": {
    "company-domain": {
      "url": "https://gateway.pipeworx.io/company-domain/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 9, 2026