Handovers that lose detail
A haul truck fault mentioned at changeover never makes the written report.
For mine sites and operations teams
From the pit to the report, without the backlog
Shift handover reports, maintenance logs, geology summaries and incident write-ups. Turn the notes your crews already take into clear records the next shift can act on.
Clean handovers
every shift starts informed
Readable logs
maintenance history you can search
Faster write-ups
incident and geology drafts
The problem
What is slowing you down today
Maintenance logs in shorthand
Fitter notes are brief and inconsistent, so recurring failures go unnoticed.
Geology notes in drawers
Logging observations are rich but scattered, and hard to summarise for planning.
Capabilities
Everything you need, nothing you don't
Shift handover reports
Send the supervisor's notes and get production, equipment status, hazards and open actions in your template.
Maintenance log summaries
Condense work order history for a machine into recurring issues and likely causes to investigate.
Geology summaries
Turn drill core logging notes into a readable interval summary for the planning team.
Incident report drafts
Structure the facts into what happened, immediate actions and follow-ups for a supervisor to verify.
Steady through the night shift
Fail-over moves requests to another eligible model if one is busy.
Cost per site
Tokens and price on every call, ready to log against the site that sent it.
Use cases
What teams run on it
01
Shift changeover reports
Consistent handovers across crews and rosters.
02
Fleet maintenance digests
A weekly summary of what keeps breaking and why.
03
Drill program updates
Readable summaries of logging notes for geologists and planners.
04
Incident and near-miss drafts
Structured first drafts for safety teams to complete.
How it works
From sign-up to production
- 1
Try last shift's notes
Paste them into the playground and see the handover report.
- 2
Connect site systems
Send notes from your maintenance or reporting tools with an API key.
- 3
Roll out across sites
Give each site its own key and keep an eye on usage in the dashboard.
Control
Built so you stay in charge
Keys you control
API keys are shown once at creation and stored only as a hash. Revoke any key instantly from Settings.
Spend you can see
Every request carries its own receipt: tokens in, tokens out, latency and price. Nothing is billed that you cannot trace.
Limits you set
Per-account rate limits and a free monthly allowance keep experiments safe before they become production.
Data you decide on
You choose exactly what you send. Repeat prompts can be served from your cache, and cache hits are never billed.
For developers
One endpoint. Every model.
Send a prompt and a capability, or name a model. One bearer key, one small JSON body, and a full receipt on every response.
curl https://YOUR-DOMAIN/api/ainf/inference \
-H "Authorization: Bearer $AI_INFERENCE_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-1042" \
-d '{"prompt":"Summarise this ticket in one line","capability":"chat"}'Questions, answered
Does it work with patchy site connectivity?
It is a standard HTTPS endpoint. Requests need a connection, so many sites queue notes and send them when connected.
Can it follow our report template?
Include the template in the prompt and ask the model to fill it from the notes.
Is it a substitute for safety investigations?
No. It drafts from the facts you provide. Competent people must investigate, verify and sign off.
How do we budget?
Each response shows its price, and the dashboard tracks daily and month-to-date usage.
Every shift deserves a proper handover
Start with last night's notes. The free allowance has you covered.