Integration

Data Axle Platform integration

Data Axle Platform gives access to Data Axle's US business (places) and consumer (people) databases. Search records by text query, filters or ids, scan through every record matching a filter, match your own records to Data Axle (single records or asynchronous batches of up to 1,000), read incremental changes, and list file deliveries of your subscriptions and lookup tables (such as category codes). The fields returned depend on the packages your account licenses. The insights endpoint (it needs a body on a GET request), the query-string form of matching (use match_record) and data submissions (corrections sent to Data Axle) are not exposed. Authentication is a token from the Account Settings tokens page, sent in the X-AUTH-TOKEN header.

Connect Data Axle Platform How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Data Axle Platform.Built from the 17 Data Axle Platform tools below, on the connection you add once.

What you can do with Data Axle Platform

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.

Delivery, 5 operations

get_deliveryGet deliveryGETRetrieve file metadata and signed download URLs for a specific delivery.
list_deliveriesList deliveriesGETReturn up to 30 deliveries ordered with the newest deliveries first.
list_subscription_deliveriesList subscription deliveriesGETReturn deliveries associated with the given subscription.
list_typed_deliveriesList typed deliveriesGETReturn only deliveries for the given file delivery type.
list_typed_subscription_deliveriesList typed subscription deliveriesGETReturn only snapshot or incremental deliveries for the given subscription.

Batch, 3 operations

add_to_match_batchAdd to match batchPUTAdd match requests to an existing batch. Up to 1,000 match requests can be added per request.
create_match_batchCreate match batchPOSTStart a batch matching operation. The initial request can include up to 1,000 match requests. Batch operations allow processing of large volumes of match requests asynchronously.
get_match_batch_resultsGet match batch resultsGETRetrieve completed match results from a batch. Matches that are still pending will not appear in the results. Use the `since` parameter to scroll through results.

Scan, 2 operations

create_scanCreate scanPOSTStarts a scan over every record matching a filter and returns a scroll id. Fetch the records with get_scan_page (or only ids with get_scan_ids_page).
get_scan_pageGet scan pageGETGets the next page (up to 200) of records from a scan started with create_scan. Call again with the same scroll id until the list comes back empty.

Search, 2 operations

search_recordsSearch recordsGETSearches Data Axle places or people by free-text query or by ids, with paging (limit up to 400, offset up to 4000). For filter, sort or scoring use search_records_advanced.
search_records_advancedSearch records advancedPOSTSearches Data Axle places or people with a JSON body: free-text query, ids, a filter DSL object, sort and field boosts. Returns the matching records and the total count.

Change, 1 operation

list_changesList changesGETRetrieve a batch of incremental changes to records. Use the next_token for pagination. Records are limited to subscribed fields. Requires fields or packages parameter.

Download, 1 operation

download_lookup_tableDownload lookup tableGETDownload the full contents of a lookup table. Supports conditional requests using the `If-None-Match` header.

Id, 1 operation

get_scan_ids_pageGet scan ids pageGETGets the next page (up to 200) of record ids from a scan started with create_scan. Call again with the same scroll id until the list comes back empty.

Lookup, 1 operation

search_lookup_tableSearch lookup tableGETSearch a lookup table by label or value.

Match, 1 operation

match_recordMatch recordPOSTMatches one of your records (name, address, phone...) to the Data Axle database and returns the best matching record with its match score and the fields you ask for.

Use Data Axle Platform from Claude Code, Cursor or Codex

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

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