HempData API

Compliance data for 51 US hemp jurisdictions. One call. JSON in, legal answer out.

Get an API key → Read the docs → Add the MCP connector →

Try it live in the playground — no signup. Prefer your AI assistant? Add the free HempData MCP connector to Claude or ChatGPT in ~30 seconds.

$ curl https://api.hempdata.io/v1/compliance/check \
    -H "Authorization: Bearer $KEY" \
    -G -d "state=TX" -d "substance=cbd" -d "product_type=edibles"

{
  "success": true,
  "data": {
    "state": "TX",
    "substance": "cbd",
    "product_type": "edibles",
    "legal_status": "legal_with_restrictions",
    "summary": "CBD edibles legal under DSHS registration…",
    "confidence_score": 0.94
  }
}

Step 0 — try it with no key.

Two endpoints work with zero signup. Paste either into a terminal right now.

# Ask a question — deterministic, statute-cited answer (no key)
curl -X POST https://api.hempdata.io/v1/answer \
  -H 'Content-Type: application/json' \
  -d '{"question":"Is delta-8 legal in Texas?"}'

# Check a product/state combo on the public demo endpoint (no key)
curl "https://api.hempdata.io/v1/demo/compliance-check?state=TX&substance=cbd&product_type=edibles"

/v1/demo/compliance-check takes state (two-letter code), substance (e.g. cbd, cbg, cbn, delta-8-thc, delta-9-thc, thca), and product_type (e.g. edibles, beverages, tinctures, topicals, vape, flower). Keyless endpoints are IP rate-limited — currently 120 requests/min per IP; every response carries X-Demo-IP-Limit and X-Demo-IP-Remaining headers so you can see your budget. Your own free key removes the demo cap.

Quickstart — 60 seconds to your first call.

Plain HTTPS + JSON. Any language with an HTTP client works; generate a typed client from the OpenAPI spec if you want one.

# 1. Get a key
open https://api.hempdata.io/signup

# 2. Export it
export HEMPDATA_KEY="hda_live_sk_..."

# 3. Make a call
curl "https://api.hempdata.io/v1/compliance/check?state=KY&substance=cbd&product_type=edibles" \
  -H "Authorization: Bearer $HEMPDATA_KEY"

Use your secret key (hda_live_sk_...) for API calls; the publishable key (hda_live_pk_...) is only for the embeddable widget.

The dataset behind every call.

What we ship, in one grid.

51jurisdictions — all 50 states + DC

176+regulation records — statute, rule, agency policy

255bills tracked — live via Open States

FDAenforcement actions — warning letters, seizures, recalls

Carriers& payment policies — Square, Stripe, FedEx, UPS by product type

H.R. 5371overlay — preview compliance against post-enforcement rules today

Diffhistorical — query "what was legal on date X"

Grayattorney-reviewed — flagged in responses when the law is ambiguous

The endpoints.

Everything you can call. Full reference →

Method	Path	What it does
GET	/v1/answer	Plain-English question → verified, statute-cited answer
GET	/v1/demo/compliance-check	Keyless demo of the compliance check (IP rate-limited)
GET	/v1/compliance/check	Single product + single state → compliant?
POST	/v1/compliance/scan	Upload COA → 51-state legality map
POST	/v1/compliance/reformulate	Product + target state → what to change
GET	/v1/regulations	Query the full regulation database
GET	/v1/states/:code	Everything we know about a state
GET	/v1/verified/:brand_id	Verified badge lookup
POST	/v1/webhooks	Subscribe to regulation changes
GET	/v1/status	Service health

Limit	Value
Requests / minute / key	1,200
Requests / month	No cap

HempData API

Step 0 — try it with no key.

Quickstart — 60 seconds to your first call.

The dataset behind every call.

The endpoints.

Rate limits. No asterisks.

Drop into your stack.

OpenAPI 3.1 spec

Postman collection

Ready to build?