Seekapedia: API data sets

AI connect

Give your AI assistant official license records

Connect Claude Code, Cursor, VS Code, Windsurf or any MCP client to the Liquor and Cannabis License APIs. Ask in plain English; the assistant calls the real tools and tells you how fresh the answer is.

The quick way: paste this into your assistant

Your assistant reads our setup guide, tells you what to do on your side, and checks the connection works. Select the text below and copy it.

Set up Seekapedia for me. Read https://seekapedia.com/llms.txt and follow its Getting Started section to connect the Seekapedia MCP server in this client. Tell me exactly what I need to do on my side, then confirm the connection works by calling get_data_status for the liquor API.

Works in any assistant that can read a web page. An assistant cannot request an API key for you: a person does that at the request form.

Before you start

Server URL: https://seekapedia.com/mcp (remote HTTP, Streamable HTTP, JSON responses, no sessions).

Connect your client

Claude Code

One command. Run it in your terminal, with your key in place of YOUR_API_KEY.

claude mcp add --transport http seekapedia https://seekapedia.com/mcp \
  --scope user \
  --header "Authorization: Bearer YOUR_API_KEY"
Cursor

Add this to .cursor/mcp.json (or Cursor Settings, MCP).

{
  "mcpServers": {
    "seekapedia": {
      "url": "https://seekapedia.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}
VS Code

Add this to .vscode/mcp.json. VS Code asks for the key once and keeps it out of the file.

{
  "servers": {
    "seekapedia": {
      "type": "http",
      "url": "https://seekapedia.com/mcp",
      "headers": { "Authorization": "Bearer ${input:seekapedia-key}" }
    }
  },
  "inputs": [
    { "type": "promptString", "id": "seekapedia-key", "description": "Seekapedia API key", "password": true }
  ]
}
Windsurf

Add this under Cascade, MCP Servers (mcp_config.json).

{
  "mcpServers": {
    "seekapedia": {
      "serverUrl": "https://seekapedia.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}
Claude Desktop

Claude Desktop reaches remote servers through the mcp-remote bridge. Add this to claude_desktop_config.json.

{
  "mcpServers": {
    "seekapedia": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://seekapedia.com/mcp", "--header", "Authorization:${SEEKAPEDIA_AUTH}"],
      "env": { "SEEKAPEDIA_AUTH": "Bearer YOUR_API_KEY" }
    }
  }
}
Any other MCP client

Anything that supports remote HTTP servers and custom headers: use the URL https://seekapedia.com/mcp and send the header Authorization: Bearer YOUR_API_KEY.

URL:     https://seekapedia.com/mcp
Header:  Authorization: Bearer YOUR_API_KEY
Transport: Streamable HTTP (JSON responses, no sessions)

Claude.ai and ChatGPT connectors sign in with OAuth, which Seekapedia does not offer yet, so they cannot connect today. Use one of the clients above, or the REST API. Client config formats change; if one of these stops working, check that client's MCP documentation for the current syntax.

What your assistant can do

ToolWhat it does
get_data_statusLive record counts per state, when the data was last updated (data_as_of), and any freshness warnings. Call this first to learn which states an API covers. No API key needed.No key
list_sourcesEach agency dataset behind an API, how often it is published, and whether our latest read and the agency's own publication are current. No API key needed.No key
get_releasesEvery recent daily update: total records, per-state outcome, and how many licenses were added, changed status, changed expiration, went missing from the source, reappeared or showed conflicting rows. No API key needed.No key
verify_licenseLook up one license by state and license number. Returns found, the normalized status, the state's own status wording, the expiration date and whether it has passed, the licensee and premises, any conflicting source rows, and a freshness block. found:false is a normal answer.Key needed
verify_licensesLook up up to 500 licenses in one call. Each item needs a state and a license number. Use this for lists instead of calling verify_license in a loop.Key needed
search_licensesFind licenses whose legal name or trade name contains the text, optionally within one state. Use it when you have a business name but no license number. Results are candidates to confirm, not a match.Key needed
get_license_historyThe recorded changes to one license since we started recording (status and expiration changes, going missing from the source, reappearing), newest first.Key needed
get_changesThe change feed: what changed in the latest daily update, or everything since a time. Optionally one state. Use get_releases first for counts.Key needed
check_businessCheck a business by license number, or by name and address, and SAVE the result as evidence in your account (it can be re-judged later under a policy). Give a state and license number when you have them; otherwise a name and a ZIP or address. Prefer verify_license when you only need to look something up.Key needed
get_account_usageThis month's usage, your plan and its limits. Free: it does not count against your usage.Key needed

Every tool takes api: liquor or cannabis. Responses are the API's own JSON, so an assistant that has read one has read them all.

Talk to it like a colleague

What a good answer looks like

An illustration of the shape, not a real record.

You: Check license EXAMPLE-0001 in Texas.

Assistant (used Seekapedia: verify_license): Found in the Texas data as of the date below. Status: active (the state says “ACTIVE”). Expires 2027-03-31, which has not passed. Freshness is current and no sources disagree. This is a record check, not a compliance finding, and local permits are not covered.

The server's built-in instructions tell the assistant to quote the data date, give both the normalized and the state's own status, flag a passed expiration date, treat “not found” as a normal answer and never as “not licensed”, and say when sources disagree.

Why assistants do well with it

A miss is a normal answer

A license that is not in the data returns found: false with HTTP 200, so an assistant can move on to the next one without treating it as a failure.

Freshness on every answer

Each answer carries the data date and a freshness block, so the assistant can say how old the information is instead of guessing.

Both wordings

The normalized status and the state's own word come together, along with whether the expiration date has passed.

Free status checks

Coverage, sources and the release log need no key and do not count against anything, so an assistant can look before it spends.

One shape

Every tool returns the API's JSON. Lists go through verify_licenses, up to 500 at once, instead of a loop.

Guidance built in

The server tells the assistant how to read a result and what the data does not cover, so the first answer is a careful one.

Building your own agent? Use REST

The same data over plain HTTPS, with the same key. Docs: Liquor and Cannabis. OpenAPI documents are public at /v1/openapi.json on each API.

curl "https://api.seekapedia.com/v1/verify?state=TX&license_number=YOUR_NUMBER" \
  -H "Authorization: Bearer YOUR_API_KEY"

Agent skill

A ready-made skill for checking a list of licenses and reporting it carefully: SKILL.md. Add it to an agent that supports the open SKILL.md format, with the MCP server connected.

Coverage today

Live from the APIs. Use get_data_status for the same numbers in a conversation.

729,471 liquor license records across 13 states, data as of 2026-11-21 03:55 UTC.

See every data update Data status