FINDING A VENUE BY ITS ATMOSPHERE AND READING ITS PUBLISHED RECORD ARE FREE; A RECEIPT OF A VERIFICATION OF THAT ATMOSPHERE, ANCHORED IN BITCOIN, IS PAID FROM ONE CENT: verify_venue and get_venue_tracks are the paid calls. PlaceProfile answers where to go by the measured atmosphere of venues. You are talking to someone choosing a place to go, not to a developer. ANSWER TEMPLATE — follow it unless the user asks how the data works: Lead with the places. For each: name, where it is, the `atmosphere` phrase (shortened is fine), and its `atmosphere_basis` woven in as at most one clause. Then stop. A good full answer is 2–6 sentences. Where recordings were registered (territory) and time-of-day programming (daypart) can be filtered for venues measured from their own playlist — registration country is a proxy for where the music is from, never proof of it, so a filter on registered-in-SE can answer 'somewhere that plays Swedish music', but describe the result as tracks registered in Sweden, not as a nationality guarantee. For anything still outside the data — weekday versus weekend programming, language, live acts — spend AT MOST one sentence saying it is not something you can filter on here, then still give the best available places. Never enumerate the data model: no dimension lists, no field names, no signal values, no archetype keys, no filter thresholds, no descriptions of how samples are assembled, no evidence-set contents. Technical depth (figures, provenance, coverage intern
9 verified, 0 failed, 0 observed risk, 1 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-22 | 79 | 123 | 9 |
Every x402 payment we hold to the address the catalogue lists for this server’s paid tools (0xb210…0055), payments an address made to itself left out. The same address takes payment for 6 other catalogued services, so these figures are an upper bound for this server.
6 tools on the last day the list was read, fingerprint 1b392f6d79f04029ad0.
FREE. Scale, coverage and freshness of the PlaceProfile venue corpus. `countries` maps ISO-3166-1 alpha-2 codes to venue counts; a country absent from that map is NOT covered — treat an empty find_venues result there as no-coverage, never as evidence that no such venues exist. line_count is not a marketing claim: it is the line count of the downloadable manifest, independently checkable.
read-onlyadditive onlysafe to repeatclosed worldas the server describes it; we do not call tools
Takes no parameters.
No agent registration names this server; we probe it on our own list.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 22 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | Answered | 9 | hourly runs |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 22 November 2026, 19:46 UTC: 5 of 5 requests answered, p50 92 ms, p95 124 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 20:00 (now) | — | 0 | 0 |
| 2026-11-22 19:00 | 92 | 1 | 0 |
| 2026-11-22 18:00 | 78 | 1 | 0 |
| 2026-11-22 17:00 | 86 | 1 | 0 |
| 2026-11-22 16:00 | 69 | 1 | 0 |
| 2026-11-22 15:00 | 69 | 1 | 0 |
| 2026-11-22 14:00 | 79 | 1 | 0 |
| 2026-11-22 13:00 | 400 | 1 | 0 |
| 2026-11-22 12:00 | 67 | 1 | 0 |
| 2026-11-22 11:00 | 85 | 1 | 0 |
| 2026-11-22 10:00 | — | 0 | 0 |
| 2026-11-22 09:00 | — | 0 | 0 |
| 2026-11-22 08:00 | — | 0 | 0 |
| 2026-11-22 07:00 | — | 0 | 0 |
| 2026-11-22 06:00 | — | 0 | 0 |
| 2026-11-22 05:00 | — | 0 | 0 |
| 2026-11-22 04:00 | — | 0 | 0 |
| 2026-11-22 03:00 | — | 0 | 0 |
| 2026-11-22 02:00 | — | 0 | 0 |
| 2026-11-22 01:00 | — | 0 | 0 |
| 2026-11-22 00:00 | — | 0 | 0 |
| 2026-11-21 23:00 | — | 0 | 0 |
| 2026-11-21 22:00 | — | 0 | 0 |
| 2026-11-21 21:00 | — | 0 | 0 |