Describe the work in plain language. One model, no setup, nothing wired to your systems yet.
add
add
add
add
add
add
add
add
add
add
add
add
add
add
add
deployed
deployed
deployed
draft
needs access
needs access
needs access
needs access
needs access
read only
needs access
Open one to read it here. Attaching registers it as a source that needs access.
Day to day, western Canada
Available on this trial
In training
montney-34bQ4Full-basin model. Needs a dedicated edge cluster.
cardium-visionQ4Log suites, scanned tickets and well file imagery.
frame-12027Field capture from smart glasses. Hands stay on the tools.
enter sends · shift + enter for a new line
Untitled agent
0 of 8 defined
Describe the work and this spec writes itself. Nothing here is connected to your systems.
01Trigger / schedulejust written
Not defined — what starts a run
02Data sources + accessjust written
No systems named yet
03Steps and toolsjust written
No work described yet
04Approval gatesjust written
No human in the loop yet
05Output formatjust written
No deliverable defined
06Guardrails and limitsjust written
No limits set
07Confidence thresholdjust written
No threshold set
08Notifiesjust written
Nobody is told yet
Execution path
1
Trigger / schedule
Not defined — what starts a run
2
Steps and tools
No work described yet
3
Approval gates
No human in the loop yet
4
Output format
No deliverable defined
Requirements
Data sources + access
No systems named yet
Guardrails and limits
No limits set
Confidence threshold
No threshold set
Notifies
Nobody is told yet
define 3 sections to test
This sandbox
Untitled agent
Not started
0 of 8 defined
Nothing is saved yet. This is a scratch workspace — a session ends when you close it. Deploying is how a draft leaves the sandbox.
Live in the fleet · read only
Runs / 30 days
2,847
94% autonomous
Interventions
171
6% of runs
Hours recovered
412
vs. manual baseline
Value recovered
$1.2M
trailing 30 days
Run history
Timestamp
Input
Confidence
Outcome
Intervention
14 Aug 09:42:11
Invoice 44821 · Nabors Drilling
0.96
Coded
—
14 Aug 09:41:03
Invoice 44820 · Secure Energy
0.93
Coded
—
14 Aug 09:38:57
Invoice 44819 · vendor unmatched
0.58
Held
cost controller
14 Aug 09:36:22
Invoice 44818 · Trican Well Service
0.91
Coded
—
14 Aug 09:33:40
Invoice 44817 · duplicate suspected
0.47
Rejected
cost controller
14 Aug 09:30:12
Invoice 44816 · CNRL rebill
0.89
Coded
—
Runs / 30 days
318
40% autonomous
Interventions
191
60% of runs
Hours recovered
96
vs. manual baseline
Value recovered
$284K
trailing 30 days
Run history
Timestamp
Input
Confidence
Outcome
Intervention
12 Aug 06:15:04
Package 2291 · 100/06-18-062-05W5
0.88
Assembled
—
12 Aug 06:12:41
Package 2290 · 100/14-22-063-05W5
0.71
Held
regulatory lead
11 Aug 06:14:52
Package 2289 · 102/03-14-063-05W5
0.90
Assembled
—
11 Aug 06:11:20
Package 2288 · survey date missing
0.49
Held
regulatory lead
10 Aug 06:16:33
Package 2287 · 100/07-11-063-05W5
0.86
Assembled
—
10 Aug 06:13:07
Package 2286 · licence mismatch
0.44
Rejected
regulatory lead
Runs / 30 days
6,104
88% autonomous
Interventions
733
12% of runs
Hours recovered
208
vs. manual baseline
Value recovered
$612K
trailing 30 days
Run history
Timestamp
Input
Confidence
Outcome
Intervention
14 Aug 11:02:18
Expense 77412 · fuel, Kaybob
0.97
Approved
—
14 Aug 11:01:55
Expense 77411 · meals, 4 crew
0.93
Approved
—
14 Aug 10:59:31
Expense 77410 · no receipt attached
0.55
Held
cost controller
14 Aug 10:57:44
Expense 77409 · lodging, 3 nights
0.90
Approved
—
14 Aug 10:55:02
Expense 77408 · over per-diem cap
0.61
Held
cost controller
14 Aug 10:52:39
Expense 77407 · duplicate suspected
0.38
Rejected
cost controller
Nothing connects in a trial sandbox
Access requests are drafted here and sent to whoever owns the system. An engineer grants them on your side of the firewall.
OT
OpenTicket
Field tickets and vendor records
Not connected
your engineer grants this
WV
WellView
Well files, daily operations, completions
Not connected
your engineer grants this
AR
Aries
Reserves and economics
Not connected
your engineer grants this
AER
AER Portal
Regulatory submissions and directives
Approval required
signing authority approves
SP
SharePoint
Procedures, AFEs, historical filings
Not connected
your engineer grants this
SB
Sandbox corpus
24 synthetic records for dry runs
Available
in use
Untitled agent
Not run yet
Loading synthetic records
queued
Running the steps
queued
Scoring confidence
queued
Routing what it could not place
queued
Sample output · synthetic records
Record
Confidence
Disposition
Ticket 8841 · Nabors · rig move
0.94
Coded
Ticket 8842 · Secure Energy · disposal
0.91
Coded
Ticket 8847 · unnamed vendor
0.62
Held
Ticket 8851 · Trican · frac water
0.88
Coded
Ticket 8852 · split across 2 AFEs
0.44
Held
Ticket 8860 · date outside AFE window
0.51
Held
Three records were held rather than guessed: one unnamed vendor, one split across two AFEs, one dated outside its AFE window. That is the behaviour you want. An agent that codes all twenty-four is an agent that is wrong three times a month.
5 blockers before deploy
An agent does not leave the sandbox until every source it reads is granted and every gate has a named approver.
Untitled agent
Describe the work and this spec writes itself. Nothing here is connected to your systems.
!Trigger definedmissing
!Every source grantedmissing
!Approval gate has a named approvermissing
!Confidence threshold setmissing
!Dry run passedmissing
Starting autonomy
Acts alone above the confidence threshold, holds the rest
35%
resolve the blockers above
read only
Signal is recording
0:09 of 30:00 · 0 events
clicks, typed text and window contents · nothing leaves this machine
Reading 12 events into a skill
naming the inputs, then the steps
Signal wrote a skill
Morning volume roll-up
Recorded 11 Aug · 4:12 · ProdView, Excel, SCADA, Outlook.
Skill file
# Morning volume roll-up
Recorded 11 Aug 2026 · 4 min 12 s · 12 events
Systems: ProdView (read), Excel (write), SCADA historian (read), Outlook (send)
## When
Every weekday by 07:00, before the field call.
## Inputs
- area — default Kaybob 03-14
- production day — default yesterday
## Steps
1. Open ProdView and filter daily volumes to the area and production day.
2. Export the filtered result.
3. Write the rows into the morning roll-up workbook below the header.
4. Compare inlet volume against the SCADA trend for the same day.
5. Write one line on anything outside tolerance.
6. Send the workbook to the field superintendent with that line in the body.
It would not replay your clicks
Read ProdView through its API, not the export dialog
All 412 wells instead of the 42 rows you filtered.
Pull inlet tags straight from the historian
Variance for every site in one call, not one trend at a time.
Build the workbook from data rather than paste
No clipboard step, no stale rows carried forward.
Leave the send manual
Draft is written and held. A person still presses send.
saving fills the spec and attaches the skill
Usage
questions and sessions are account totals · the rest is this session
The cap is on the trial, not the platform. A deployed fleet runs on your own hardware with no token ceiling.
Default model
Operator
Send run telemetry to AptureOff
nothing in the trial sends telemetry, so there is nothing to switch on
Invites land in their own sandbox — nothing you build here is shared.
invites land in their own sandbox
Trial sandbox
Move off the sandbox
The trial runs one model against canned data. Both plans run your data on your side of the fence, and the agents you built here carry over.