Connect Your Stack to the Engine
Lake connectors, legacy import, identity, REST, and MCP, same credentials when AI is on the roadmap.
Four Paths Into the Same Engine
Data platforms feed wells. Your IdP owns access. REST, MCP, and Vector share one credential.
Lakes and Well Systems
Pull wells, surveys, and production into a simulation. Bulk import covers desktop formats.
- Snowflake
- Databricks
- WellView
SSO and SCIM
Federate through the IdP you already run. SCIM provisions and deprovisions users.
- Entra ID
- Okta
- SAML
REST, MCP, and Vector
Same token, scopes, and permissions on every surface. Engineers sign off on well writes.
- REST
- MCP
- Vector
Claude, ChatGPT, Gemini
Point your AI program at one hosted MCP endpoint with scoped tools.
- Claude
- ChatGPT
- Gemini
Connectors for the Lakes. Import for Desktop Tools
Pull wells, surveys, and production in one fetch. Bulk import covers RodStar and SRod files still on the desktop.
Enterprise Connectors
Pull from your lakes into well records under the org scopes your engineers already use.
- Snowflake
- Databricks
- Azure
- AWS
- WellView
Legacy Bulk Import
Bring RodStar and SRod designs in without rebuilding well setups by hand.
- RSDX
- RSVX
- INP6E
- XLSX
One Well Record
Lake-fed and imported wells land in the same workspace, ready to simulate.
- Surveys
- Rod strings
- Production
From Your Data to a Decision
Connect sources once. Run RodSim on the well record. Engineers review designs before anything writes back.
One Engine. Three Surfaces
One credential and one set of scopes. Pick the surface that fits how your team works.
Vector
Ask on the open well. Vector runs RodSim and drafts changes for engineer review.
Explore VectorMCP
Claude, ChatGPT, and Gemini call hosted tools on the same wells.
Explore MCPREST API
Scripts and services read wells and run sims over versioned HTTP.
Explore the APIConnect Your Stack on One Pilot Well
Start with a well from your lake or a legacy file. Same credentials on REST, MCP, and Vector.