Connect Your Stack to the Rod-Lift Engine
Data lakes, identity, REST, MCP, and Vector under the same credentials and permissions. Build on the systems IT already runs.
Databricks 
WellView 
AWS 
MCP 
SAML 
Okta 
Azure 
Snowflake Lakes, identity, and agent surfaces, same credentials and permissions
Four Paths Into the Same Engine
Data platforms feed wells. Your IdP owns access. REST and MCP expose the engine. Vector chats on the same credential. Pick the path that matches who is integrating.
Lakes and Well Systems
Pull wells, dyno cards, surveys, and production into a simulation. Bulk import covers legacy desktop formats.
See data connectorsSSO and SCIM
Federate through the IdP you already run. SCIM provisions and deprovisions, no second directory.
See identity
REST, MCP, and Vector
Same Bearer token, scopes, and permissions on every surface. Engineer signoff on well writes.
See surfacesClaude, Cursor, MCP clients
Point your AI program at one hosted MCP endpoint. Scoped tools under the same credentials and permissions.
See AI clientsDeep docs live on the MCP and REST pages and Trust docs . This page is the enterprise map.
Connectors for the Lakes. Import for Desktop Tools
Pull wells, surveys, and production from Snowflake, Databricks, Azure, AWS, and WellView into a simulation in one fetch. Bulk import covers common RodStar and SRod formats when wells are still on the desktop.
Snowflake Databricks Azure AWS WellView Enterprise connectors
Snowflake, Databricks, Azure, AWS, and WellView. Pull into PetroBench well records under the same org scopes your engineers already work inside.
RSDX RodStar design 
RSVX RodStar vertical 
INP6E SRod input 
XLSX Spreadsheet Legacy bulk import
Bring RodStar and SRod designs into PetroBench without rebuilding well setups by hand. Common desktop formats land in the same workspace as lake-fed wells.
Your IdP Stays the Source of Truth
Engineers sign in with credentials IT already manages. SCIM provisions and deprovisions users, no second user directory to maintain.
- Microsoft Entra ID Azure AD
- Okta Workforce Identity
- SAML / OIDC Any compliant IdP
Single sign-on
SAML 2.0 and OpenID Connect through the IdP you already run.
SCIM provisioning
New hires get accounts automatically. Deprovision revokes access.
No parallel directory
IT keeps one source of truth. PetroBench consumes it.
Mint Once. Call REST, MCP, or Vector
The same scoped Bearer token on every surface. Point your AI stack at MCP, your pipelines at REST, and keep engineer signoff on live-well writes.
Explore MCP
Bearer pb_svc_org_8f2a9c… -
wells:read -
simulations:read -
organization:read
Granted on this token
Built for the AI Program Already Underway
If leadership is funding agents, PetroBench already exposes rod-lift wells over MCP and REST. IT keeps the scopes. Engineers keep signoff on writes.
MCP for the agent stack
Point Claude, Cursor, or your internal agents at app.petrobench.com/mcp. Same wells and RodSim tools under org scopes.
REST when you build your own
app.petrobench.com/api/v1 for pipelines and internal apps. One Bearer token, same permissions as the UI.
Vector in the product
In-product chat on the open well. Live-well writes stay behind engineer signoff and the audit log.
From Your Data to a Decision
Connect sources once. Run RodSim on the well record. Engineers review designs before anything writes back.
Connect Your Stack on One Pilot Well
Start with a well from your lake or a legacy file. Same credentials on REST, MCP, and Vector.