Case study · 2026 · Backblaze Generative Media
Spatialize
Venue access information is often wrong, and a chatbot will turn it into a confident yes. Spatialize turns a floor plan into a validated 3D twin, checks a route against one person's clear width, and keeps every access claim sourced in Sanity. Agents ask and propose through 14 WebMCP tools, but verdicts are computed and only people publish.
- Result
- Winner, Feedback Prize Proof ↗
- Built
- 2026, for Backblaze Generative Media
- Stack
- React 19 + Three.js · FastAPI · Sanity (Content Lake + Context) · WebMCP · Backblaze B2 · OpenAI Responses API · Gemini vision
- Links
- Code ↗
The problem
Disabled visitors rehearse a route before entering an unfamiliar building, but the data is usually a flat PDF that goes stale. In Euan's Guide's 2024 survey (n=6,665), 77% of disabled respondents found venue-published access information misleading. A single accessible yes or no is wrong for somebody, because the threshold depends on the person.
How it works
- 01Extract the plan. Gemini vision proposes rooms, doors and a route graph from the floor plan.
- 02Gate the geometry. A deterministic topology validator, Zod in browser and Pydantic on server, checks it.
- 03Compute the verdict. Route check against one clear width returns CLEAR, BLOCKED or UNKNOWN.
- 04Read the evidence. Sourced claims live in Sanity; an agent explains them but can't overrule.
- 05A person decides. Agent and voice proposals wait in review; declined reports stay as disputes.
Key decisions
Verdicts are computed, never written
CLEAR, BLOCKED and UNKNOWN come from geometry and structured evidence. The evidence agent receives the verdict as authoritative, and its prose is shown separately so it can never replace it.
The server applies every change
A review found that a client-built scene let a 'rename this room' proposal smuggle in a wider door. Now a proposal is a few fields: the backend applies it to its own copy, re-validates it, and computes the access impact itself.
UNKNOWN beats a wrong CLEAR
A low-confidence or disputed doorway on the route makes the answer UNKNOWN. Auditing the tools against 181 rules in Chrome's WebMCP guides found one stamping a 0.9 m default as a visitor's measurement; unmeasured widths now answer UNKNOWN.
Decline, never delete
A venue can decline a visitor's report but cannot erase it. The dispute stays on record, and the next agent to ask hears both sides.
Results
- 20 / 20right tool picked by gemini-3.6-flash from the tool contract alone (args 12/12)
- 24 / 24evidence-agent runs that read the knowledge base and stated the computed verdict
- 13 / 13journey checks through Chrome's own WebMCP host, on the deployed app
- 109 + 65frontend and backend tests, plus 5 Chrome journeys
What's not done yet
This is rehearsal guidance, not live navigation, and CLEAR is a screening result, not an accessibility certificate: turning space, slope, headroom and thresholds are not in the data. Widths come from the floor plan, checked for consistency, not measured on site. The demo venue is fictional, the reviewer role is a shared token, and multi-page PDFs use page 1 only.
Next case studyQuaestor →An on-chain spend governor for AI agents: capped budgets, receipts and a kill switch.