Technical proof tied to real delivery.
Generate a demo key, inspect sample datasets, read the docs, and verify how Roam packages data before you scope a live program.
Available today
Demo keys, sample-data listing, readiness scoring, llms.txt, sitemap, and MCP discovery routes are live.
Boundary
The demo surface is for evaluation. It is not an open production API or unrestricted portal.
Best next step
Validate payload shape and packet structure first, then move to scoped program review.
First successful call
Under five minutes to a working response.
- 1Generate a short-lived demo key from the sandbox.
- 2List sample datasets through the demo API.
- 3Validate formats, manifests, and downstream integration patterns.
- 4Route into a live program once the delivery contract is proven.
Developer docs
Quickstart
Generate a demo key, list datasets, inspect response shapes, and understand the evaluation boundary quickly.
Format Reference
Reference current delivery families, output caveats, and interoperability expectations.
Integration Guide
Reference patterns for evaluation, GIS intake, and secure downstream delivery without overstating the public demo surface.
Machine-readable discovery
`llms.txt`, sitemap, robots, and MCP discovery help buyers and tools navigate the public docs and demo routes. They support discovery and documentation, not a full public production platform.
Role-based pathways
Different reviewers need different answers.
Developer
Get a demo key and verify the delivery contract quickly.
Start with a demo key, inspect sample datasets, and validate that Roam can hand data to your pipeline without format ambiguity.
- Generate a short-lived demo key
- List sample datasets through the API
- Review delivery and integration patterns
GIS Analyst
Verify formats, metadata, and geospatial compatibility.
Inspect sample manifests, supported coordinate systems, and format references for downstream GIS, mapping, and infrastructure workflows.
- Check supported point cloud and GIS formats
- Review metadata and manifest expectations
- Confirm sample dataset structure before procurement
IT & Security
Assess current safeguards before approving a program.
Review diligence materials, privacy commitments, delivery controls, and data-handling boundaries before the program enters procurement.
- Review public diligence materials and evidence-backed statements
- Understand retention, deletion, and transfer posture
- Use invite-only portal access where evaluation credentials are configured
Executive
Pressure-test the business case before launch approval.
Model the operational value of reducing capture turnaround, rework, and manual conversion overhead with a structured ROI baseline.
- Estimate avoided rework and field remobilization
- Quantify time-to-dataset improvements
- Align procurement with a concrete implementation path
From evaluation to scoping
Need technical proof before procurement?
Use the sandbox, docs, and sample data to validate the contract first, then move into a live capture program once the handoff model is clear.
Raise NDA, security, privacy, and delivery constraints in the first conversation instead of after procurement restarts the process.
Need immediate scheduling? Use the programs inbox.