Blueprint support
Help Center
Find the right route for world-model packages, hosted evaluation, capture provenance, billing, access, and runtime issues.
Support packet
Browse by topic
The support map.
Support is organized around the real paths buyers, capturers, and operators use: packages, hosted sessions, provenance, billing, and access.
Getting Started
Choose the right Blueprint path before a team opens a request, package, or hosted evaluation.
World Model Packages
Understand exact-site packages, included artifacts, licensing, and how package proof should be read.
Hosted Evaluation
Start, inspect, share, and troubleshoot hosted sessions without separating runtime behavior from capture evidence.
Capture Provenance
Rules for lawful capture, privacy, operator context, and what counts as evidence inside Blueprint.
Billing And Access
Access, seats, licensing, checkout, invoices, and procurement paths for buyer teams.
Troubleshooting
Resolve access, browser, package, and support-routing issues while preserving the evidence trail.
Popular articles.
Start here when the blocker is access, package scope, hosted evaluation, or what to send support.
Getting Started
Choose the right support path
Where to go when you need a package, hosted review, capture access, or human reply.
Read articleWorld Model Packages
Package access vs hosted evaluation
When to use each buyer path.
Read articleWorld Model Packages
How to read package provenance
What the evidence labels mean.
Read articleHosted Evaluation
Report a hosted runtime issue
What to send if the hosted view behaves incorrectly.
Read articleTroubleshooting
What to send support
The minimum packet that gets a useful reply.
Read article
Still need help?
Route the blocker with evidence.
Support works fastest when the request includes the exact page, package, session, or request id plus the outcome you expected.