Outdoor worlds are getting grounded
Google's Genie and Street View work make the category legible: agents can explore worlds anchored to real places.
Indoor captureExact-site world modelsHosted review
Outdoor worlds have Street View. Indoor robot sites need Blueprint.
Google's Street View-grounded Genie makes real-place world models easier to understand. Blueprint focuses on unscanned indoor spaces: capture, provenance, rights limits, and hosted review for the exact facility before field time.
Robot-team next step
Start here
Name one indoor site, robot task, and review path. Proof stays attached before access expands.
Capture first. Package next. Review before commitment.
Hosted Site-World Eval Preview
Choose a site task. Inspect the route.
A hosted evaluation would start from a site-specific task, then use the site package to inspect local context before live robot work. These grocery tasks drive sample camera paths only; they do not claim a real robot policy has completed the task.
Reference route
6F2FD31B...295CF3
Package/proof
scenes/9...peline
Preview state
Task-conditioned sample path
Generated online-order pick evaluation clipMuted
Active eval task
Pick an online order item
Navigate from aisle entry to a shelf face and inspect the target zone before a tote handoff.
Evaluation focus
Reachability, shelf visibility, aisle clearance
A self-hosted sample splat asset is attached here, so the preview can render in Blueprint's browser viewer instead of an iframe. It is sample/generated media, not customer proof.
Category signal
Real-place world models are no longer abstract.
The public category is moving from generated scenes toward places agents and robots can navigate. Blueprint's wedge is the indoor site layer that public maps do not solve.
Indoor spaces are still missing
Warehouses, stores, labs, hotels, back rooms, and service corridors are rights-sensitive, task-specific, and rarely captured at robot-evaluation depth.
Blueprint captures the indoor layer
Blueprint turns those unscanned spaces into capture-backed packages, hosted review paths, proof boundaries, and export decisions for robot teams.
Choose your path
World model
A capture-backed indoor environment for one real site and robot workflow.
Site package
The manifest, route, proof, rights notes, exports, and files tied to that site.
Hosted review
Blueprint runs the site model in a review room before your team takes files into its own stack.
Provenance
The record of where the capture came from, when it was captured, what route it covered, and what limits apply.
Commercial product
Blueprint sells indoor exact-site products, not generic demos.
Blueprint turns indoor capture into site-specific packages, hosted review paths, and buyer decisions tied to the same facility, route, and proof record.
01
Site Package Access
One real place, packaged with capture route, manifest, proof notes, rights limits, export scope, and geometry when available.
View package access02
Hosted Review
A hosted review path for task scenarios, observations, and buyer notes before export, travel, or integration work.
See hosted workflow03
Buyer Request Path
Structured intake turns a robot-team question into the next site, package scope, hosted evaluation, or capture run.
Start requestOutdoor validation
Street View-grounded world models validate real-place simulation; Blueprint focuses that demand indoors.
Indoor capture
A walkthrough or site record starts the product. Provenance, rights, and limits stay attached.
Site package
Blueprint packages the capture into a site-specific world model, buyer listing, and export scope.
Hosted decision
Use hosted review and proof before committing travel, rollout spend, or deeper integration.
For robot teams
Start with the exact site your robot needs to understand.
A buyer request should name the indoor place, workflow, and robot question. Blueprint then keeps the capture-backed proof, package scope, and hosted path together.
01
Capture the indoor site
Start from the facility, route, workflow, and public-facing or permissioned capture path with provenance and limits attached.
02
Ground the world model
Turn capture into a site package with manifest, route context, rights notes, freshness, exports, and hosted review context.
03
Decide before field time
Use hosted review, scenario replay, or package access to approve export, request recapture, or narrow the deployment question.
Proof boundary
The proof travels with the product.
A polished sample is useful only when it stays honest. Blueprint labels public examples, keeps approved proof attached to the exact site, and gates hosted access until the request is reviewed.
Samples and demo worlds are labeled inside the proof flow.
Approved listings keep capture basis, freshness, rights, restrictions, and package scope attached.
Hosted access and exports open after site-specific review confirms the path.
World-model catalog
Sample worlds show the package shape.
Browse public examples to inspect the proof format, then request the exact facility or route your team needs when it is not already listed.
Why capture matters
Indoor capture turns vague simulation demand into a buyer-ready package.
The useful details are local: aisle width, signage, occlusions, access boundaries, restricted areas, and the robot task a team is actually deciding on.
Example public capture
Cedar Market Aisle Loop
Austin, TX
Can a shelf-scanning AMR navigate produce, endcaps, and refrigeration lanes without treating this as a generic warehouse aisle?
Example public capture
Harbor Mall Common Corridor
Sacramento, CA
Is the corridor geometry useful for cleaning, patrol, or wayfinding robots before anyone builds a custom sim scene?
Example public capture
Northline Hotel Lobby Loop
Durham, NC
Can a delivery robot reason about lobby approach, elevator threshold, and concierge-adjacent transfer areas without entering private guest zones?
Example public capture
Atlas Retail Service Aisle
San Jose, CA
Does the real retail floor have enough aisle width, signage variation, and obstacle variety to justify a hosted policy comparison?
Request next
Three ways into the same product path.
Robot teams, site operators, and capturers enter from different sides. The package still resolves around one exact site and its proof.
Robot team
I need a real place my robot can train or evaluate against.
Request an exact-site package.
Name the facility, route, task, and robot setup. Blueprint routes you to a listing, new capture request, or hosted evaluation.
Site operator
I control or influence a facility.
Set site boundaries.
Define access rules, privacy constraints, restricted zones, and commercialization terms before a package is released.
Capturer
I can record real public-facing places.
Apply for capture access.
Capture work remains city- and approval-gated. Open the launch path before recording, routing, or expecting assignment payout.
Buyer answers
Short definitions for investors and robot teams comparing exact-site packages, hosted evaluation, provenance, rights, and sample boundaries.
What does Blueprint sell?
Blueprint sells capture-backed indoor world-model packages, hosted evaluation paths, and buyer review workflows for robot teams evaluating real operating environments.
Why does exact-site capture matter?
Street View can help ground outdoor worlds, but indoor operating spaces need lawful capture, provenance, freshness, occlusion detail, and rights boundaries attached to the package.
What proof is attached?
Public examples show the proof shape. Approved listings can attach capture provenance, site and capture ids, restrictions, freshness, package scope, and hosted-review notes when available.
What should a buyer request next?
Request one exact site, one robot task, and the review path you need: package access, hosted evaluation, new capture, or a proof packet for internal buyer review.
Start
Request one indoor exact-site world model.
Name the place, workflow, robot setup, and review path. Blueprint will route the request to a current listing, new capture, package access, or hosted evaluation without blurring sample proof into approved output.