AI energy procurement, approved first
flintspark supports energy procurement teams with fuel buying decisions. Flint, flintspark's agent, reads EIA prices and forecasts, applies a lock-or-spot rule you can read, and drafts a buying request with its reasons. By default a person approves the request before it is submitted.
What sources are read?
In the demo, Flint reads the US Energy Information Administration's public pages: the weekly retail diesel price for the East, Gulf and West Coast, and the Short-Term Energy Outlook's next-year forecast.
Flint tries an official API first where one exists, then a direct page address, then recorded browser actions. The filmed run used the pages. Flint reads each value from the same place every run, and a person confirms those places when the skill is taught.
Sources · read every run
- Prices
- Weekly regional diesel, East · Gulf · West
- Forecast
- Short-Term Energy Outlook, next year
- From
- eia.gov, public pages
Prices were read live for the demo on 10 Nov 2026.
How is a lock-or-spot call made?
By a rule written in words, not a black box. Flint compares next year's forecast with each region's price this week, and writes a reason for the region from those two numbers.
The rule is learned from a demonstration. Where several rules fit, Flint asks which one was meant, and a person reviews the rule before the skill is trusted. See the fuel procurement use case for the rule and its reasons.
Rule · in words reviewed by a person
For each region, compare next year's forecast with this week's price.
Reason for the Gulf Coast: forecast 4.49 against this week's 5.741, so spot.
Who approves the plan?
A person, by default. Submitting a binding request cannot be undone, so Flint stops and shows the person the exact request. They can approve it, reject it or take over.
Each approval is a signed, single-use grant for that exact request. A workflow owner can switch on trust mode for a workflow; that switch is logged. How people stay in control.
Approval · your turn
Submit a binding request for the three regions?
Each region has a decision, a price and a written reason.
What audit evidence is kept?
Every run records its steps, what Flint looked at, the rule that fired, the decision and the evidence. Run records are kept for 90 days by default.
The approval itself goes into a separate, hash-chained audit log, so a later edit to it is detectable. Run records are not in that log.
flintspark's audit log is not a validated GxP or 21 CFR Part 11 audit trail.
What is kept
- Steps, prices read, rule, decisionrun record90 days
- The evidence for each reasonrun record90 days
- The approvalhash-chained audit logchained
What does Flint do, and what stays with your team?
Flint does the reading, the rule and the drafting. Your team keeps the decision.
| Step | What Flint does | What stays with your team |
|---|---|---|
| Read the prices and the forecast | Reads this week's regional diesel prices and the next-year forecast from the EIA pages, the same way every run. | Chooses which regions, contracts and suppliers matter. |
| Apply the rule | Applies the taught rule and shows it in words, with a written reason for each region. | Reviews and corrects the rule before it is trusted, and owns the buying policy. |
| Draft the request | Fills the supplier's request form with the decision, the price and the reason for each region. | Decides whether to lock or buy spot. The decision is theirs. |
| Submit | Stops before the binding submit and shows the exact request. | Approves, rejects or takes over, by default. |
| Keep the record | Records the run's steps, what it read, the rule that fired and the decision. | Owns the contract, the supplier relationship and any compliance duties. |
What is the status today?
The demo is built and has been run end to end. It is an early demo: the supplier is fictional and served locally, and the figures come from one demo run on 10 Nov 2026, not from a customer.
flintspark runs on one operator's machine today. It holds no certifications and is not a validated GxP system. Single sign-on and a credential vault are on the roadmap.
Early demo, fictional data
Read what was real and what was recorded, or how Flint learns a workflow.
Questions about this page
Which data does flintspark read for energy procurement?
In the demo, Flint, flintspark's agent, reads the weekly regional diesel prices and the next-year forecast from the US Energy Information Administration (EIA), on its public pages. It reads them from the same place every run, and a person confirms those places when the skill is taught.
Does flintspark place fuel orders on its own?
No. By default Flint stops before the binding submit and a person approves it. In the demo the supplier is fictional and served locally, so no real order was placed. The decision to lock or buy spot stays with your team.
Can I see the rule that picks lock or spot?
Yes. The rule is written in words and a person reviews it before the skill is trusted. Where several rules fit the demonstration, Flint asks which one was meant. Each region's recommendation also carries a written reason.
See Flint run
Bring one workflow you'd rather not do by hand. We'll show Flint learning one like it, and stopping before anything it can't undo.
We reply from hello@flintspark.ai.