You run a community paper, a student newsletter or a group’s page. You want to show what’s on in Geneva, Lausanne, Nyon or just across the border, without retyping the agenda every Thursday. Here are three ways, using what already exists. No account, no sign-up.
The technical detail, the preview buttons and the code to copy are on the API page and the widget page. This piece is the gesture, and what not to conclude from it.
Five picks for Thursday’s email
The request /api/v1/events?when=weekend&limit=5&lang=en returns at most five Friday-to-Sunday events, as JSON. In the email, one line each: the day, the title, the venue, a link to the page. The link already carries utm_source=api. Add the name in source_links: that is the original listing, not ours.
A fictional example, not a real date to publish: “Sat 7 Nov · Nuit fictive du Démo · Salle Fictive · page · source: Fictional listing”. If the list comes back empty, say so and link to the weekend. If the request fails, do not invent five events to fill the gap.
A box on the site
For an agenda that updates itself, paste an iframe. City, genre or free picks: the builder shows the render and gives the code. Outgoing links use utm_source=widget, and the “via GeNEVERsleep” line stays. If nothing is announced, the box says so and points at the full agenda. If it does not load, a plain link to Geneva or Lausanne is enough.
A venue can use the same idea for its own dates, from its venue page. It is not only for organisers.
Ask an assistant
The server https://geneversleep.ch/mcp answers assistants (Claude, Cursor, and the others listed on the API page), read-only, with no key. A question like “what’s on tonight in Geneva?” uses the events_tonight tool. A useful answer is a list with links. The assistant can be wrong: the linked page is what counts. If it finds nothing, the honest line is “nothing in this filter”, not an imagined event.
What this does not prove
A response arriving does not mean someone installed the tool, or that an outside site is showing it. This cannot count people, or real embeds elsewhere. An optional label (label=…) counts only if we wrote it down on our side first: it is not verified, and it is not a name. Thursday’s email is not API activity.
The counters are described on the privacy page. They total requests, not people. An optional label, written down in advance, is not a verified identity. A click toward a ticket is not a sale. No cookie, no IP address. If the storage is not attached, nothing is written.
Rights
This is not “all the events”, and naming GeNEVERsleep is not a licence. Resident Advisor, Ticketcorner and Eventfrog are not in the API. Shotgun, La Décadanse and PETZI are not settled: a link to them is not permission to republish their listing. The checklist is on the API page. The examples in this article are fictional.
The events named above are fictional. For a real date, open the linked page.