Vector Works on Your Wells.
Vector reads your wells, runs RodSim, and drafts changes inside PetroBench, on the wells and sims your team already uses.
Built on Your Wells and RodSim
Vector runs inside PetroBench on the engine and workspace your team already uses.
Same Engine
Vector runs the RodSim math your engineers already trust. No second model of the well.
Same Workspace
Opens on the well already in PetroBench, next to the engineers working it.
Engineer Signoff
Drafts wait for engineer review. Nothing is applied on the well without approval.
Scoped Access. Write Guardrails. Full Audit Trail
Agents inherit your PetroBench roles. Every run is logged. Live-well writes stay behind guardrails.
Scoped Reads
Dyno cards, production, and RodSim history, only for wells inside your scopes.
Write Guardrails
Live-well changes stay gated for engineer review. Sims and reads run under your roles.
Audit Trail
Every run records inputs and outputs on the log, with who ran it and when.
Same SSO
SAML or OIDC through your IdP. Roles and regions match PetroBench.
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.
MCP
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 APIQuestions Teams Ask First
What production and engineering managers ask before a Vector pilot.
Yes. Vector calls the RodSim engine your engineers already run. The language model picks inputs and explains the card. Same inputs produce the same numbers as clicking Run in the workspace.
No. Sims and reads run under your access rules. Live-well writes stay behind write guardrails until an engineer approves. Every run lands on the audit trail.
Yes. Point those clients at the hosted MCP server. Same engine, wells, credential, and scopes as Vector. Vector is the chat surface inside PetroBench; MCP is for agents you already run elsewhere.
Inputs, well-state snapshot, and outputs. You can open the run later and see what was asked, what RodSim returned, and whether a write is still gated.
We cover pricing on a walkthrough once we understand your wells and how the team will use Vector with RodSim.
Ada pertanyaan lain? Hubungi Kami
Put Vector on Your Wells.
Book a walkthrough for Vector on your wells, or see how MCP connects the AI tools you already use.