The same knowledge base, as an API and an MCP server.

Everything the Skills know is available programmatically. One REST endpoint returns evidence-graded records with their sources; one MCP server exposes the Skills themselves to Claude, Cursor and any MCP client. This page is the technical one. If you want to see what the knowledge base does for a business, start with the Skills.

Try a query Full documentation

LIVE DEMO

Ask any cannabis question.

See what your platform could return. Evidence-graded, cited, and ready for production.

Try these examples

Public demo is limited to 5 queries/day. 5 remaining today. Get full access →

cannavec-api-response

{ }

Query the knowledge base to see results

Reference

Two ways in.

REST API

POST /api/v1/search with a Bearer key. Namespaces: cannabis, cannabis_products, cannabis_faq.

curl -X POST https://cannavec.ai/api/v1/search \
  -H "Authorization: Bearer ck_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "query": "CBD for anxiety", "namespace": "cannabis", "top_k": 5 }'

Auth: API key, ck_live_…, shown once, created in the dashboard.
Response: Ranked records with evidence grade, jurisdiction and sources, plus timing and grade counts.
Limits: Per-plan rate limits and monthly allowances. Enterprise keys are unmetered.

MCP server

Every MCP-eligible Skill as a tool inside Claude, Cursor or any MCP client. Sign in with Google once; the connector handles the rest.

{
  "mcpServers": {
    "cannavec": { "url": "https://cannavec.ai/api/mcp" }
  }
}

Tools: search_cannabis_kb, regulatory_check, coa, search_cannabis_products, search_strain_fingerprints and the research tools.
Auth: OAuth 2.1 with PKCE. No key to paste.
Access: Included on paid plans from £49 a month.

MCP setup guide

What this is forThe API returns knowledge; it does not make clinical decisions. Build it into a product for licensed businesses and the professionals in them, and keep the evidence grade and sources visible to the end user.