Integration

Crustdata integration

Crustdata is a B2B company and job data platform. Search companies by firmographic filters or a natural-language description (headcount, funding, revenue, hiring, location, industry), resolve a company from a name, domain or profile URL, autocomplete valid filter values, search indexed job postings with aggregations, run live web searches and fetch web pages, and read the account's credits, endpoint prices and usage. Not exposed: every person dataset (people search, enrichment, contact details, identify, verification), social post search, company enrichment (its field selection reaches founders, executives and reviewers), batch jobs (their results come as signed download links), watchers (they deliver records to a webhook, Slack or email), and the single usage-event route that echoes request bodies; academic author profiles in web search and the client IP of usage events are not returned. Billing: company search 0.03 credit per result plus premium groups, job search 0.03 per result, web search 1 per query, web fetch 1 per page; identify, autocomplete and account routes are free. Purchased credits last 12 months; per-endpoint rate limits apply (for example 15 to 45 requests per minute, HTTP 429 beyond). Authentication: an API key from the Crustdata dashboard, sent as a Bearer token; the x-api-version header (2025-11-01) is sent for you.

Connect Crustdata How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Crustdata

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

identify_companyIdentify companyPOSTMatches companies by name, website domain, profile URL or Crustdata company id (send exactly one list) and returns ranked matches with crustdata_company_id and basic info. Free.
search_companiesSearch companiesPOSTSearches companies by filters, a natural-language query or both; cursor paging. Bills 0.03 credit per result plus, per result, each premium group filtered on or returned (taxonomy 0.1, most others 0.2, technographics filter 1).

Company field value, 1 operation

autocomplete_company_fieldAutocomplete company fieldPOSTSuggests values, with document counts, for a company search field (for example taxonomy.professional_network_industry), to build valid search_companies filters. Free.

Credit balance, 1 operation

get_account_creditsGet account creditsGETReturns the remaining credit balance and the recurring credit grant (size, frequency, next refresh), with wallet and top-up detail when enabled. Free.

Endpoint permission, 1 operation

list_endpoint_permissionsList endpoint permissionsGETLists every Crustdata endpoint with its access status for this account, enabled and disabled response fields, rate limit and credit prices (base, premium fields, filters and modes). Free. Filter by path or category.

Job field value, 1 operation

autocomplete_job_fieldAutocomplete job fieldPOSTSuggests values for one search_jobs field (for example title, category or a technology name) from partial text, to build valid filters. Free.

Job posting, 1 operation

search_jobsSearch jobsPOSTSearches indexed job postings by filters (title, category, company, location, technologies, dates) with cursor paging, sorting and aggregations; each result includes the hiring company. Bills 0.03 credit per result.

Usage error, 1 operation

list_usage_errorsList usage errorsGETGroups the team's failed requests over a window (default the last 7 days), most frequent first, with endpoint, masked error message, kind, status and count. Free.

Usage event, 1 operation

list_usage_eventsList usage eventsGETLists the team's API requests one by one, newest first, with endpoint, status, result count and credits charged per component. Cursor paging (pass next_cursor). Free. Client IP and user agent are not returned.

Usage summary, 1 operation

get_usage_summaryGet usage summaryGETAdds up the team's API usage over a window (default the last 7 days): requests, credits, errors and results, optionally split by day, product, endpoint, charge component, API key, surface, platform or status class. Free.

Web page, 1 operation

fetch_web_pagesFetch web pagesPOSTFetches up to 10 public web pages by URL and returns, for each, its title and full HTML content. Bills 1 credit per page.

Web result, 1 operation

search_webSearch webPOSTRuns a live web search and returns results from the web, news, scholarly articles or an AI overview, with title, URL and snippet. Bills 1 credit per query.

Use Crustdata from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Crustdata once
Add your Crustdata 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.