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.
Chat on the Well You Already Use
Engineers already run sims and read dyno cards in PetroBench. Vector puts that same work in chat, with write guardrails on every change.
Ask on the open well
Vector starts on the well already in your workspace. No paste. No new tab.
Run the same sims and cards
RodSim math and dyno cards you already trust. Chat does not invent a second model.
Draft changes for review
SPM and string drafts wait for engineer signoff. Every run lands on the audit trail.
One Engine. Three Ways to Run It
Call it over REST, hand it to any MCP client, or use Vector inside PetroBench. Same token, scopes, and permissions on all three.
Query It Over REST.
Versioned REST for wells, simulations, and equipment. OpenAPI 3.1 and scoped tokens.
Expose Hosted MCP Tools.
Hosted MCP. Claude, Cursor, or any MCP client, one scope-gated tool surface.
Work With Vector in PetroBench.
Vector is the in-product agent on the same engine, opens on the well in your workspace.
From Your Data to a Decision.
Connect sources once. Describe the problem. Physics runs. Engineers review the result.
Draft Overrides Behind Guardrails
Drift triggers a fresh pass through the loop. Sims and reads run under your scopes. Live-well writes stay behind write guardrails, nothing writes without approval, and every run lands on the audit trail.
- 01 WatchLive cards stream from your wells continuously.
- 02 DetectCard-shape anomaly trips a webhook automatically.
- 03 ReasonAgent decides the right intervention to make.
- 04 Draft OverrideAgent proposes SPM or string changes behind guardrails.
- 05 Write GuardrailsLive-well writes stay gated. Every run lands on the audit trail.
Every Capability, Ready to Run
Simulations, design search, and reports, available over REST, MCP, and Vector from day one.
Run Any Simulation
Full rod-pump dynamics for any well, on demand. Surface and downhole cards returned with diagnostics in one call.
Search Rod-String Designs
Search every candidate configuration against your constraints and get a ranked set of designs back.
Pull Live Well Data
Deviation, completion, fluid PVT, and historical card data, fetched from PetroBench well records and normalized.
Inspect Card Drift
Compare results against baseline envelopes in the workspace. Flag drift for engineer review.
Compare Scenarios
Side-by-side scenario comparison with deltas, fillage curves, and gearbox load under your weighting.
Generate Engineering Reports
Render a PDF or Markdown report in engineering-grade format. Share with your team or export from the platform.
Same engine from chat or click
Run a sim, draft a change, and keep the record on the well.
Ask Vector, or click Run in the workspace. Both hit the same RodSim engine on the well you have open.
Drafts sit behind write guardrails. Nothing hits the live well until an engineer signs off.
Inputs and outputs land on the well record. Open the run later and see what RodSim returned.
Built for the People Who Touch the Well
Engineers run it. Ops shares the same context. IT keeps identity and audit where they already live.
Stay on the well you already have open.
Vector sits next to RodSim and your dyno cards. No new tool to learn.
Questions Engineers Ask First
Answers to the things every team asks before turning Vector loose on real wells.
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.
Vector lives inside PetroBench. Chat opens on the well they already have open, same wells, dyno cards, and RodSim. Nothing extra to install.
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.
The same wells the engineer can already open. Vector inherits PetroBench roles and regions. It does not get a wider view than the signed-in user.
SSO through your IdP (SAML or OIDC), role-based access per team and region, and a full audit log. Live-well writes stay behind guardrails. Well access usually mirrors what you already have in PetroBench.
Yes. Start with a scoped pilot on access you already have. Widen regions once write-guardrail review is in place and the team is reading the audit trail.
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.
It stays queued. Nothing is applied on the well until an engineer signs off. The draft remains on the well record so the next reviewer opens the same proposed taper, SPM, or pump change.