Tokoro – open, signed event protocol with LLM crawler
Tokoro is an open-source, self-hosted event protocol designed to streamline event discovery across the web. It allows users to extract and curate events from various sources into a shared calendar that can be queried easily. The platform emphasizes user privacy and simplicity, requiring no accounts or personal information for access.
- ▪Tokoro enables users to harvest events from multiple sites and pool them into a geo-located calendar.
- ▪Events can be extracted and published quickly using a browser tool that interacts with a language model.
- ▪The platform operates without requiring user registration, relying instead on a local keypair for identity verification.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/robertoranon/tokoro |
| Publication time | Tue, 19 May 2026 10:47:46 +0000 |
| Retrieval time | 2026-05-19T10:49:57.509Z |
| Last seen | 2026-05-19T10:49:57.509Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | FGBBMMTX74Ar |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Tokoro Finding out what's on near you is weirdly broken: events are scattered across dozens of sites, buried in social feeds, or locked behind logins. There's no common layer you can just query. This is my attempt to build one — open source, self-hosted, LLM-powered. Live demo of my instance: https://tokoro-query.pages.dev/. If you want to test event extraction tools, contact me for an API key. Tokoro is a thin, collaborative event calendar layer on top of the web. Not a replacement for Eventbrite or Resident Advisor — instead, a way for curators to harvest events from those sites and pool them into a shared geo-located calendar anyone can query. Example: Imagine a loose network of jazz fans spread across a country.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.