Integration

BigDataCorp integration

BigDataCorp's Plataforma de Dados returns Brazilian data on people (by CPF), companies (by CNPJ), addresses, products (by EAN), lawsuits, vehicles, live official sources (on-demand certificates) and partner datasets: each query names the datasets it wants and each dataset is billed per query. It also runs batch jobs over files, asynchronous queries delivered to a webhook, monitoring subscriptions that push changes, saved views, query logs, usage statistics and free price estimates. Data on people is personal data under LGPD: the account holder is responsible for having a legal basis for each query. Token management (generate, disable, list token ids) and monitoring user configuration (webhook credentials) are not exposed. Authentication: the AccessToken (JWT) and TokenId headers, generated in BDC Center; tokens expire and must be renewed.

Connect BigDataCorp How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with BigDataCorp

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 job, 8 operations

cancel_batch_jobCancel batch jobPOSTCancels a batch job that is processing. A cancelled job cannot be resumed; use pause_batch_job to stop it temporarily.
create_batch_jobCreate batch jobPOSTDefines a batch job that queries every line of an input file (people, companies or validations) and returns its JobId. Nothing runs or is billed until start_batch_job, unless AutomaticallyStartQuerying is true.
get_batch_jobGet batch jobPOSTReturns a batch job's progress by JobId: CurrentJobStatus (pending, loading, loaded, querying, parallel_limit_reached, paused, queried, parsing, done, cancelled), percent complete, errors, elapsed and estimated time, estimated cost and output file.
list_batch_jobsList batch jobsPOSTLists the batch jobs of the token's user that are running (status, progress, record and error counts, queried API and datasets); set ShowHistoricalJobs to include finished ones. Paged with PageNumber and PageSize.
pause_batch_jobPause batch jobPOSTPauses a batch job that is querying (CurrentJobStatus querying) until resume_batch_job or cancel_batch_job.
restart_batch_jobRestart batch jobPOSTRestarts a batch job from the beginning: every result obtained so far is deleted and every query runs, and is billed, again.
resume_batch_jobResume batch jobPOSTResumes a paused batch job (CurrentJobStatus paused) from where it stopped.
start_batch_jobStart batch jobPOSTStarts querying a loaded batch job (CurrentJobStatus loaded): every record is queried and billed. Not needed when the job was created with AutomaticallyStartQuerying true.

Monitoring, 6 operations

create_monitoringCreate monitoringPOSTSubscribes a previous query (by QueryId) to monitoring: BigDataCorp re-checks its datasets (every 15 days by default) and sends each changed dataset to SubscriptionHooks. Returns the SubscriptionId. Watched fields that change often can raise costs.
disable_monitoringDisable monitoringPOSTTurns off monitoring subscriptions by SubscriptionIds, else by QueryIds, else by the exact Api, Datasets and Parameters used at subscription. Returns Unsubscribed per subscription.
get_monitoringGet monitoringPOSTReturns an active monitoring of the domain by SubscriptionId, or by Api, Datasets and Parameters: original QueryId, API, locale, parameters, datasets, creation date and last change found.
list_monitoringList monitoringPOSTLists the active monitoring subscriptions of the domain, oldest first: SubscriptionId, original QueryId, API, locale, parameters, and datasets. Page with Cursor and PageSize.
test_monitoringTest monitoringPOSTSimulates a monitoring alert from an active monitoring or a recent query and sends it through the chosen channel (email, webhook or file) to check the integration. Free, up to 500 calls per month.
update_monitoringUpdate monitoringPOSTChanges the watched fields or the delivery mechanism of an active monitoring, found by SubscriptionId or QueryId, and returns its details. Send Datasets, SubscriptionHooks or both; leave out what should stay as it is.

View, 4 operations

create_viewCreate viewPOSTCreates a view: a named, saved set of datasets (with modifiers) for one API, usable in place of Datasets in batch jobs and monitoring. The name must be unique in the company.
delete_viewDelete viewPOSTDeletes a view. Every query that still uses it fails from then on.
list_viewsList viewsPOSTLists the views the token may use, in the domain scope (private to the company) by default or the global scope (views made by BigDataCorp), optionally filtered by name, API or datasets.
update_viewUpdate viewPOSTChanges the datasets or the API of a view. The change applies at once to every user of the view from their next query.

Async query, 2 operations

get_async_query_statusGet async query statusPOSTReturns the delivery status of an asynchronous query by its QueryId: HookMetadata.Status (RegistrationFailed, Registered, Dispatched, DispatchmentFailed, Posted, PostFailed), stage timings, the webhook's HTTP answer and the delivery history.
submit_async_querySubmit async queryPOSTSubmits any dataset query asynchronously: answers at once with a QueryId, then BigDataCorp POSTs the full result to the Hooks URL. Track delivery with get_async_query_status. The result has the shape of the synchronous query.

Address, 1 operation

query_addressesQuery addressesPOSTReturns location data for a Brazilian zipcode or area from the BigDataCorp Addresses API: environmental areas, biomes, indigenous lands, crime statistics, company statistics, address risk. One object per requested dataset; billed per dataset.

Async dispatch stats, 1 operation

get_async_dispatch_statsGet async dispatch statsPOSTReturns asynchronous delivery statistics for the token's user (or the whole domain): average dispatch time overall and per dataset, pending hooks, and hooks delivered or failed in the last hour.

Company, 1 operation

query_companiesQuery companiesPOSTLooks up Brazilian companies (by CNPJ or alternative keys) in the BigDataCorp Companies API and returns one Result per matched company with one object per requested dataset (RegistrationData, KycData, Relationships...). Billed per dataset.

Lawsuit, 1 operation

query_lawsuitsQuery lawsuitsPOSTReturns a Brazilian court lawsuit by process number from the BigDataCorp Lawsuits API (basic_data: court, subject, status, value, parties, updates, decisions) or a CADE process (cade_processes_data). Billed per dataset.

Modeling data, 1 operation

query_modeling_dataQuery modeling dataPOSTReturns the unified modeling dataset of a person (unified_modeling_data_person) or a company (unified_modeling_data_company) from BigDataCorp: one row of demographic, contact, financial, lawsuit and collection indicators. Billed per query.

Monitoring delivery, 1 operation

list_monitoring_deliveriesList monitoring deliveriesPOSTLists past monitoring deliveries, paged: delivery date, documents monitored and triggered, and per API and dataset the triggered count and percentage.

Official record, 1 operation

query_ondemand_sourcesQuery ondemand sourcesPOSTQueries official Brazilian sources at request time through the BigDataCorp On-demand API: Receita Federal status, PGFN, FGTS, IBAMA, CNJ and CGU certificates, criminal records, SINTEGRA, DETRAN. Billed per dataset.

Partner dataset, 1 operation

query_partner_datasetsQuery partner datasetsPOSTQueries third-party partner datasets resold through the BigDataCorp Data Marketplace: credit scores and risk (Boa Vista, QUOD, Quantum, Murabei), phone intelligence (Telesign, Blu365), beneficial owners. Billed per dataset.

Person, 1 operation

query_peopleQuery peoplePOSTLooks up Brazilian people (by CPF or alternative keys) in the BigDataCorp People API and returns one Result per matched person with one object per requested dataset (BasicData, ExtendedEmails, Processes, KycData...). Billed per dataset.

Price, 1 operation

get_price_estimateGet price estimatePOSTReturns the price of a query before running it: the datasets found for the account in that API, the computed price, and which requested datasets or APIs were not found (with the API where a dataset really lives). Free.

Product, 1 operation

query_productsQuery productsPOSTReturns product data for an EAN barcode from the BigDataCorp Products API: technical sheet, images, ratings and reviews, current prices across e-commerce sites, related products. One object per requested dataset; billed per dataset.

Query log, 1 operation

search_query_logsSearch query logsPOSTSearches the audit log of queries made on the account (kept at least 3 months): pass QueryId, q or Tags. Each record has the date, user, IP, API, datasets, parameters and the stored result. Use Cursor to page with q.

Query result diff, 1 operation

compare_query_resultsCompare query resultsPOSTCompares two results of the enrichment APIs: the oldest and newest result of a monitoring (SubscriptionId), or two queries (QueryId1 and QueryId2). Returns DiffDetails per dataset.

Usage, 1 operation

get_usage_statisticsGet usage statisticsPOSTReturns the account's usage for a period (current month by default): total, successful and failed requests, charged and free queries, estimated price, the monthly limit and per-dataset detail. The end date itself is excluded.

Vehicle, 1 operation

query_vehiclesQuery vehiclesPOSTReturns the history of a Brazilian license plate from the BigDataCorp Vehicles API (license_plates): vehicles linked to the plate, owners count, alerts and restrictions. Billed per query.

Use BigDataCorp from Claude Code, Cursor or Codex

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

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