Documentation

Connect to AlpineDataWorks in minutes.

Pick REST, MCP, or keyless discovery. Every intelligence object ships with a score, drivers, confidence, source lineage, and a freshness contract.

Request API key MCP quickstart Try keyless

+ MCP on every object: REST; + MCP on every object
data sources: 2,000+; data sources
on every object: REST + MCP; on every object
discovery endpoints: Keyless; discovery endpoints

Fastest path

Start with a key, then copy one call.

No card

REST quickstart copy-ready

curl https://api.alpinedataworks.com/v1/intelligence/ADW-002 \
  -H "Authorization: Bearer YOUR_API_KEY"

1. Sign up

2. Copy key

3. Call object

Choose a connection path

Three clean ways in

Use the same catalog whether you are building an app, wiring an agent, or evaluating the payload shape first.

1 Most popular

REST API + a free account

For apps, scripts, and dashboards.

Mode Bearer API key

Endpoint /v1/intelligence/{id}

Request API key, generate an API key, and call any intelligence object over plain HTTPS. Every object ships a score, drivers, confidence, and a freshness contract.

1 Sign up — instant, no card. You start with 1,000 free credits.
2 Your API key is waiting in your hub — copy it (rotate anytime).
3 Send it as a Bearer token (see below) and call any object.

Request API key →

2 For agents

MCP server

For Claude, IDEs, and AI agents.

Mode MCP discovery

Endpoint /mcp

Point any MCP-compatible agent at our server and it discovers every tool with zero setup — discovery is keyless. Add your API key when you are ready to pull billable data.

1 Add the MCP server URL to your agent.
2 Discovery (catalog, schemas) works with no key.
3 Drop in your API key to run billable pulls.

MCP quickstart →

3 No signup

Try it keyless

For evaluating before you commit.

Mode Open discovery

Endpoint /catalog.json

Browse the full catalog and pull sample payloads with no account. Discovery endpoints and the live playground are open so you can see the shape of the data first.

1 Open the catalog or the live playground.
2 Read /catalog.json, /openapi.json, /llms.txt.
3 Sign up when you want live, billable data.

Open the playground →

Two ways to pay

Once you have an account, pick whichever fits your usage. You can switch anytime.

Pay-as-you-go credits

Buy a credit pack — or name your own amount from $25 — and spend whenever. Credits never expire. Best if your usage is bursty or you're just starting out.

• $25 steps, no upper limit
• 12 credits per $1 at $25–99; up to 15 per $1 at $500+
• No subscription, no expiry

Buy credits →

Monthly subscription

A plan for steady usage — higher rate limits, larger batch sizes, and bonus credits on every top-up. Best if you call the API regularly.

• Gold · +30% credits on top-ups
• Platinum · +50% credits on top-ups
• Plans available · cancel anytime — no contracts

See pricing →

Quick reference

Authentication

Send your API key as a bearer token on every request.

Authorization: Bearer YOUR_API_KEY

Call an intelligence object (REST)

Every object is available at /v1/intelligence/<id>.

curl https://api.alpinedataworks.com/v1/intelligence/ADW-002 \
  -H "Authorization: Bearer YOUR_API_KEY"

Connect an agent (MCP)

Add the server to your MCP client. Discovery is keyless; add your key for billable pulls.

{
  "mcpServers": {
    "alpinedataworks": {
      "url": "https://api.alpinedataworks.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Discovery endpoints (no key)

https://alpinedataworks.com/catalog.json Full catalog
https://api.alpinedataworks.com/openapi.json OpenAPI spec
https://api.alpinedataworks.com/.well-known/mcp.json MCP manifest
https://api.alpinedataworks.com/llms.txt LLM-readable index

Map & package data

Pull county-grain data by geography

Every data package — the same layers behind the Data Viewer map — downloads over one REST endpoint. Filter to exactly the geography you need, in JSON or CSV.

GET /v1/packages/{id}/download copy-ready

# One county — Cook County, IL (FIPS 17031)
curl "https://api.alpinedataworks.com/v1/packages/{id}/download?counties=17031&format=csv" \
  -H "Authorization: Bearer YOUR_API_KEY"

# A whole state
curl "https://api.alpinedataworks.com/v1/packages/{id}/download?states=IL&format=csv" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Specific ZIP codes
curl "https://api.alpinedataworks.com/v1/packages/{id}/download?zips=60540,60563&format=json" \
  -H "Authorization: Bearer YOUR_API_KEY"

# No geography filter — all 3,143 US counties
curl "https://api.alpinedataworks.com/v1/packages/{id}/download?format=json" \
  -H "Authorization: Bearer YOUR_API_KEY"

Geography parameters

?counties=17031 county FIPS, comma-separated
?states=IL two-letter state codes
?zips=60540,60563 specific ZIP codes
no filter all 3,143 US counties
&format=json|csv pick your output

Volume-billed

You pay for what you pull. One county is roughly the base credit cost — perfect for prototyping — while an all-US, multi-dataset pull bills for the real volume it returns. Scope your geography first, then scale up.