API plan

The verified regulatory record, inside your AI workspace.

Vellum Search speaks MCP — the open protocol your agents already use. Connect it once and Claude, Cursor, or any MCP-capable workspace can search the record and cite real sources, with your entitlements enforced server-side.

Endpoint

https://search.vellumintel.com/mcp

Authentication: your API key as a bearer token. Keys are created in your account on the API plan.

One command

claude mcp add --transport http vellum https://search.vellumintel.com/mcp \
  --header "Authorization: Bearer vk_YOUR_KEY"

That's the whole integration in Claude Code. Other MCP clients take the JSON below.

Claude Desktop / other MCP clients

{
  "mcpServers": {
    "vellum": {
      "type": "http",
      "url": "https://search.vellumintel.com/mcp",
      "headers": { "Authorization": "Bearer vk_YOUR_KEY" }
    }
  }
}

Let your agent do it

Paste this into Claude Code, Cursor, or any AI coding agent. It performs the whole integration — registration, verification, wiring — on its own. Swap in your key first.

Integrate Vellum Search (verified EU/UK regulatory records) into this project.

1. Register the MCP server: endpoint https://search.vellumintel.com/mcp, transport HTTP,
   header "Authorization: Bearer <MY_VELLUM_API_KEY>". In Claude Code that is:
   claude mcp add --transport http vellum https://search.vellumintel.com/mcp --header "Authorization: Bearer <MY_VELLUM_API_KEY>"
   For other clients, add the equivalent entry to the MCP config file.
2. Verify the connection: call the search_records tool with query "age assurance" and
   confirm results return titles, publication dates and canonical source URLs.
3. Wherever this project answers regulatory questions, route them through search_records
   first; fetch full detail with get_record. Always cite title, date and canonical URL.
   If Vellum returns zero records for a query, report that honestly instead of
   substituting web search — absence from the verified record is itself information.
4. REST fallback if MCP is unavailable: GET https://search.vellumintel.com/v1/search?q=...
   with the same Authorization header.

Tools

Tool	What it does
search_records	Natural-language search over your entitled catalogue. Filters: jurisdiction, ecosystem, limit. Returns titles, snippets, dates, provenance.
get_record	Fetch one record by id — full detail with source link, authority tier and evidence grade.

REST, if you prefer

curl -H "Authorization: Bearer vk_YOUR_KEY" \
  "https://search.vellumintel.com/v1/search?q=age+assurance&limit=5"

Same key, same entitlements, JSON out. Every response carries data_as_of and a build id, so you always know what you queried.