Content & Documents · Integration
OpenSpace
Add OpenSpace to your product for your customers, and give your AI agents governed access to it.
Embed an OpenSpace integration so your product can show what a job site actually looked like instead of asking people to describe it. OpenSpace is 360 degree reality capture for construction: a walk of the site is mapped automatically onto the floor plan, and the record that builds up is a set of dated captures per project, alongside field notes that carry photos, comments, assignees and due dates. Each customer authorises their own OpenSpace account, so access runs under their grant and their existing project permissions apply rather than being widened by your integration. fastn owns the auth, token refresh, pagination, rate limits and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own OpenSpace account so projects, captures and floor plans are reachable inside your product with no per-customer code.
Pull the capture for a given floor and date so your product can show site conditions next to the record it belongs to.
Read field notes and their photos per tenant so issues raised on site appear in your product rather than only in the capture tool.
Support customers whose project, level and plan structures all differ as configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the most recent capture for an area and reports what it shows, reading only that tenant's projects.
An agent pulls the field notes raised on a level this week and summarises the open ones, with every read audited.
An agent answers which floor plan a capture is tied to without anyone opening the console.
Example prompt
Show me the latest capture for level 3 and list the field notes still open there.
Set up OpenSpace in 4 steps
- 01Enable the OpenSpace connector in your fastn dashboard.
- 02Have each customer authorise their own OpenSpace account so reads run under their credentials and project permissions.
- 03Map the project, capture, floor plan and field note fields your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the OpenSpace integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an OpenSpace integration without building it. Your customers connect their own OpenSpace account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an OpenSpace update is not your on-call problem.
- One integration serves your product and your agents. The same governed OpenSpace connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Autodesk BIM 360
BluebeamWorks well with
NearmapOften used alongside
Tools the same teams tend to run next to OpenSpace, across other categories.
Shopify
Stripe
Jira
AsanaOpenSpace integration FAQ
How do I add an OpenSpace integration to my product?
Enable the OpenSpace connector in your fastn dashboard, then let each customer authenticate their own OpenSpace account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no OpenSpace client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own OpenSpace account?
Yes. Every connection is scoped to the individual customer, so each authorises their own OpenSpace account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this OpenSpace integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds the most recent capture for an area and reports what it shows, reading only that tenant's projects.
Who maintains the OpenSpace integration?
fastn does. When OpenSpace changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the OpenSpace integration run under?
Each customer's own OpenSpace grant. Where OpenSpace holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in OpenSpace automatically?
Where OpenSpace supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the OpenSpace integration?
A common starting point: let each customer connect their own OpenSpace account so projects, captures and floor plans are reachable inside your product with no per-customer code. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the OpenSpace integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding OpenSpace does not change your per-connector cost. You can start free with 3 connected accounts.
Add OpenSpace to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.