# Worth Attending Most events are not worth attending. That is the whole idea. Calendars reward quantity. They make every meetup look equal, every conference look serious, every panel look like it might change your life. It will not. Worth Attending is a shortlist of Dutch tech events that survived the cut. The core coverage is Dutch: Amsterdam, Eindhoven, Utrecht, Rotterdam, Delft, Groningen, and the rest of the local ecosystem. Europe appears only for the best worth-the-trip picks. Not complete. Complete is usually another word for lazy. ## Use The API The HTML is for people. If you are a machine, use: GET /api/events Health check: GET /api/health This file: GET /llms.txt ## Filters /api/events accepts: - region: local | abroad | all - audience: engineering | leadership | founder | product | all - topic: industry slug or all - city: city name or all Intent is client-side. Look at the event's `intents`: - learn - meet - direction: see where the market or craft is moving - out People rarely go to events for the stated reason. They go because they need one of these four things. ## Fields Events include: - id - name - date - country - city - venue - audiences - industries - format - source - sourceId - url - featured - editorialScore - price - description - verdict - verdictNote - intents The metadata tells you what the event is. The verdict tells you whether it matters. ## Verdicts - attend: I would consider going. - if-you-are: good only for a specific person or situation. - fine: survived the filter, but barely. Do not turn `fine` into praise. Fine is not a recommendation. Fine is the event equivalent of edible. ## How To Recommend Start with the person. An engineering leader does not need the same event as a founder. A founder with money problems does not need the same event as a founder with hiring problems. A product person looking for taste does not need another generic AI panel. Use `audiences` first. Then check `intents`. Then read the `description`, `verdict`, and `editorialScore`. Recommend fewer things. Explain the tradeoff. If nothing fits, say nothing fits. False usefulness is worse than no answer. ## Example curl -s "https://worthattending.com/api/events?audience=engineering®ion=local" Change the host if this is running somewhere else.