The Proof · April 2026
Three audiences. One thesis: the music a venue plays is the structured signal AI assistants will use to decide what to recommend, and you can watch that signal being read, live, on a real venue’s dashboard.
For investors
AI answer engines now mediate hospitality intent. The race is no longer who ranks on a SERP, it’s who is cited when ChatGPT, Claude, or Perplexity answers “a quiet café with warm acoustic music near me.” The signal those engines need to make that decision is structured atmospheric data. The signal venues already produce, but never publish in machine-readable form, is the music they play. PlaceProfile bridges those two facts. A pasted Spotify playlist is converted, track by track, into measurable atmospheric data, Spotify audio features per track plus AcousticBrainz mood classifiers, and the venue is published as a ~93 KB JSON-LD @graph at a stable URL.
“PlaceProfile converts the music a venue already plays, pasted as a Spotify playlist URL, into a structured JSON-LD@graphpublished at/v/{slug}.”
Telemetry closes the loop. A canonical taxonomy of 44 bot signatures across a five-tier ladder (MAXIMUM / HIGH / MEDIUM / ALLOW / BLOCK) records every AI crawl that hits a venue’s endpoint, and renders the result on a public dashboard the venue can show a sceptical board member without a login.
If you want to test the thesis, the data is one click away, read the v1.1 white paper, then watch a real venue’s dashboard.
For founders
Every track on a venue’s playlist carries 12 Spotify audio features (tempo, energy, valence, acousticness, danceability, and the rest) and resolves against 6 AcousticBrainz mood classifiers (happy, relaxed, acoustic, aggressive, party, sad). Aggregated across the playlist, those 18 dimensions are the venue’s atmospheric fingerprint. Published as JSON-LD on a stable URL, the fingerprint becomes retrievable: an intent query like “celebratory restaurant for Saturday night” resolves to a vector that ranks the JSON-LD payload, and the cited URL is the venue’s page. No content calendar. No SEO arms race. The structured payload is the surface the AI ecosystem reads.
“End-to-end latency from a bot crawling the edge to a row appearing on the venue’s dashboard is targeted at ≤30 seconds. During the 2026-04-25-0346 milestone audit, a single test crawl was measured at ≤2 seconds.”
Read the v1.1 white paper for the full mechanism. Watch the live dashboard for the proof.
For hospitality operators
The dashboard answers that question directly. Five widgets, StatCardRow, TrendChart, PlatformBreakdown, RecentVisitsLog, EntityTraversal, show every AI bot crawl of your venue’s /v/{slug} page, classified against the 44-signature taxonomy and ranked by tier. MAXIMUM-tier engines (ChatGPT, Claude, Perplexity-tier) are the ones whose citations actually move bookings. HIGH and MEDIUM-tier crawlers index, summarise, and feed downstream answer engines. The dashboard separates them so the operator sees, in real time, which surface of the AI ecosystem has noticed the venue.
“PerplexityBot is well-behaved, well-attested, and HIGH tier, but a citation from it is qualitatively different from a citation from ChatGPT, which is also well-behaved and well-attested but MAXIMUM tier.”
The free trial gives you the dashboard against your own venue. Before then, read someone else’s.
Live, read-only, real data
Café Noir is a real café in Gothenburg. Its playlist resolved through PlaceProfile’s pipeline, its JSON-LD was published at /v/cafe-noir-gothenburg-se, and every AI bot that reads that endpoint shows up on the public dashboard below. No simulation. No seeded numbers. Whatever you see is what bots actually did.
placeprofile.net/app/venue/cafe-noir-gothenburg-se/dashboard · public, no sign-in
Companion white paper · v1.1 · 2026-04-25
The technical companion to this page, What the Bots Will See: How AI Crawlers Will Read Music to Decide Which Hospitality Venues to Cite (v1.1, 2026-04-25), explains the telemetry layer, the bot-tier taxonomy, and why the music-derived layer of a venue’s JSON-LD is what makes the difference between being indexed and being cited.
“We are deliberately not publishing a specific bot-tier distribution snapshot in this paper. ... PlaceProfile’s hard rule is no mock data anywhere, including in marketing material.”
The structural prediction is qualitative, not quantitative: as a venue’s /v/{slug} profile is read by the AI ecosystem, the dashboard’s PlatformBreakdown will accumulate crawls weighted toward the MAXIMUM tier, the AI answer engines themselves. If that holds for your venue during the trial, the dashboard is doing its job. If it doesn’t, the dashboard tells you that too, and that’s data worth having before you commit.