# Intentface Events > Upcoming tech and AI events (conferences, meetups, hackathons, workshops, demo days) across Europe, the Nordics, North America and Asia. Scraped from public calendars and official sites, classified by topic, event type and audience, and updated roughly weekly. Only upcoming events are searchable. ## For agents - MCP server (Streamable HTTP): https://events.intentface.com/api/mcp Tools: `search_events`, `get_event`, `list_vocabulary`. Claude Code: `claude mcp add --transport http intentface-events https://events.intentface.com/api/mcp` Claude apps: Settings, Connectors, Add custom connector, paste the URL. - JSON API: https://events.intentface.com/api/events (below). No key needed. Prefer structured filters for anything the vocabulary covers and put the rest in `about`, which is matched by meaning and keywords. It only orders the filtered events and never removes any. "AI events in Finland for designers about agentic experience" is: https://events.intentface.com/api/events?topic=ai&country=FI&audience=designers&about=agentic+experience+design The same search in plain language, parsed like the site's search bar: https://events.intentface.com/api/events?q=ai+meetups+in+helsinki+next+month ## GET /api/events Filters AND across kinds and OR within a kind. List filters take repeated or comma-separated values. - `topic`: `ai` (AI), `genai` (GenAI & LLMs), `ml-research` (ML research), `robotics` (Robotics), `software` (Software engineering), `web` (Web), `mobile` (Mobile), `data` (Data), `cloud` (Cloud & DevOps), `security` (Security), `startups` (Startups & VC), `hardware` (Hardware & deep tech), `saas` (SaaS), `product` (Product & design), `web3` (Web3), `quantum` (Quantum), `climate` (Climate tech). `ai` includes `genai` and `ml-research`. - `audience`: `developers` (Software engineers), `ai-engineers` (AI & ML engineers), `data` (Data professionals), `researchers` (Researchers), `tech-leaders` (CTOs & tech leads), `executives` (CEOs & executives), `founders` (Founders), `investors` (Investors), `product` (Product managers), `designers` (Designers), `marketers` (Marketing & sales), `students` (Students & newcomers) - `type`: `conference` (Conference), `summit` (Summit), `meetup` (Meetup), `hackathon` (Hackathon), `workshop` (Workshop), `demo_day` (Demo day), `webinar` (Webinar), `talk` (Talk) - `country`: ISO 3166 alpha-2 (`FI`, `US`, `DE`) - `city`: city name, matches within 45 km (see the vocabulary endpoint for names and counts) - `region`: `europe` (Europe), `nordics` (Nordics), `baltics` (Baltics), `dach` (DACH), `benelux` (Benelux), `north-america` (North America), `asia` (Asia), `middle-east` (Middle East), `latam` (Latin America) - `from`, `to`: `YYYY-MM-DD`, events overlapping the range - `mode`: `online` or `in_person` (both include hybrid) - `free`: `true` for events marked free - `about`: plain words, ranked by meaning (and keywords). With filters it only orders their results, matches first - `q`: alternative to the filters, a plain-language query parsed like the site's search bar ("ai meetups in helsinki next month"). Words in double quotes are an exact phrase matched against title, organizer and summary, never turned into filters: `q="AI Summit" in new york`. Relative dates ("today", "this weekend", "next month") count from the current date in UTC, and weeks start on Monday. `filters` in the response shows the dates used (`date:2026-10-01..2026-10-31`) - `limit` (default 25, max 100), `offset` Response: `{ total, offset, order, matched?, filters, unmatched?, notes, events }`. `total` counts every event the filters allow. With filters and free text, the first `matched` of them (before paging) match the text, best first, and the rest follow by date; with free text alone only matches are returned. `unmatched` is text that matched none of the filtered events. `notes` names any value that was not understood. Each event has `slug`, `title`, `summary`, `start`/`end` (ISO; a UTC instant, or a date when `allDay`), `timezone`, `mode`, `venue`, `city`, `country`, `organizer`, `price` (`free`, `paid`, or `unknown` when the source does not say), `type`, `topics`, `audiences`, `url` (the organizer's page, for registration) and `page` (the event on this site). ## Other endpoints - https://events.intentface.com/api/events/{slug}: one event with full description, address, status and sources - https://events.intentface.com/api/events/vocabulary: every accepted filter value, plus countries and cities with event counts - https://events.intentface.com/data/events.json: every upcoming event in one file (about 1 MB) - https://events.intentface.com/e/{slug}: event pages with schema.org Event JSON-LD - https://events.intentface.com/e/{slug}.md and https://events.intentface.com/index.md: the event pages and the homepage as Markdown (also served for `Accept: text/markdown`) - https://events.intentface.com/sitemap.xml