Paste a link. Get clean event JSON.
The Knod Event Import API turns any event, topic or city page into structured data. Deterministic parsing, not guesswork, so the same page returns the same fields every time.
Open import.knod.aicurl -H "x-api-key: $KNOD_API_KEY" \ "https://import.knod.ai/api/scrape?url=https://lu.ma/sf"
Three ways to call it
One endpoint
GET /api/scrape?url=… returns a clean event object as JSON or CSV: name, date, location, description and cover image. Authenticate with your key in the x-api-key header.
A CLI
npx knod-events <url> runs the same import from your terminal. It executes on your own machine, which is how Meetup and Ticketmaster work, since those block datacenter IPs.
An MCP server
An import_event tool for Claude, Cursor and other agents, so an assistant can pull structured event data directly. Same API key as the CLI.
What it reads
- Luma, including topic pages, city pages and calendars
- Eventbrite
- Partiful
- Meetup and Ticketmaster, through the CLI
- Any page publishing schema.org Event data
How it works, and what it is not
It reads each page's structured data directly: JSON-LD, Luma's embedded event data, and Open Graph tags. That is deterministic, so results are fast and the same fields come back every time.
This is the event data layer. It imports and structures event information. It is a separate thing from Knod's connection matching, which runs inside the product and is not exposed through this API today.
Get an API key.
Create an account on import.knod.ai and your key is issued immediately.
Also from Knod, Inc.
CodeMend
Catches production errors, works out what broke, and hands you the fix. A separate product, built by the same company.