Agriculture AI agent · Chemical application
Chemical-Application Assistant (Label & Bulletin Checks)
Check a proposed application against the current label, the bulletin for that field and the farm's own records, then draft the record — the certified applicator decides whether to spray.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Decision to spray
- Applicator only
- After launch
- Agent Care
What this agent does
Checks the plan, does not clear it
In
- 01
Take the proposed application from the prescription or work order — product, crop, field, rate, timing and equipment.
- 02
Retrieve the registered label, any supplemental or state labelling, and the bulletin for that field and month.
Reason
- 03
Check the proposal against the label — crop and site, growth stage, rate, timing, tank mix and adjuvant.
- 04
Check re-entry and pre-harvest intervals against the planned field work, the harvest date and the crop that follows.
- 05
Check certification, restricted-use status, buffers, bulletin limits and the forecast against the label and the permit.
Decide
- 06
Separate what the label prohibits outright from what it leaves to the applicator's judgement, and say which is which.
- 07
Route what the label does not settle — thin tank-mix data, an ambiguous stage call — to the agronomist or applicator.
Out
- 08
Draft the application record with the label version, the bulletin, the conditions and the clause behind every flag.
- 09
Re-check what can change after the plan is set — weather, harvest date, bulletin — and flag it before spraying.
Product statement
The agent checks and records. The decision to apply, the rate and the legal responsibility stay with the certified applicator.
Example workflow
One spray plan, end to end
- 1Application proposedPrescription, work order or spray plan — product, crop, field, rate, timing and equipment
- 2Label and bulletin retrievedThe registered label, supplemental and state labelling, and the bulletin for that field and month
- 3Restrictions checkedCrop and site, growth stage, rate, timing, tank mix, adjuvant, re-entry, pre-harvest and the following crop
- 4Conditions and permissions checkedCertification, restricted-use status, buffers, sensitive neighbours and the forecast against the label
No human action required
Stages 1 to 4 run without a person in the loop — retrieval and checking finish before the applicator is asked to read anything. A restriction the label states outright is raised the moment it is found.
Reaches the applicator with the check attached.
Goes to a person before the tank is filled.
Certified applicator
Reads the restriction found, the label clause it came from and the bulletin, then decides whether the application goes ahead.
Apply · Change the plan · Ask the agronomist
Decided — handed back
- 6Record draftedWritten to the farm record only where write access and policy allow; nothing is filed without a person
- 7Outcome evaluatedRestriction recall, bulletin currency, interval conflicts, record completeness and false blocks by crop
Corrections
A flag the applicator rejects is recorded with the reason and counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Authorising an application to go ahead.
- Setting, raising or adjusting an application rate.
- Clearing a crop or site the label omits.
- Deciding a restricted-use product may be applied.
Automation boundary
Agent acts unaided
- ✓Retrieve the label, the supplemental labelling and the bulletin for that field and month.
- ✓Check the proposed application against every restriction those documents carry.
- ✓Check re-entry and pre-harvest intervals against planned field work and the harvest date.
- ✓Draft the application record and flag a changed condition before the sprayer runs.
Write actions run only inside the approval boundaries agreed in implementation. The record is drafted; a person files it.
- Waiving a re-entry or pre-harvest interval.
- Shortening a buffer or a bulletin restriction.
- Approving a tank mix the label does not cover.
- Changing label sources, block rules or thresholds.
Example output
One proposed application, annotated
Everything the agent returns is attached to the plan and to the clause it came from.
Check output · single proposed application
Illustrative example- Proposed
- Post-emergence herbicide, one block
- Crop and stage
- Soybean, beginning flowering
- Field, date
- Field 7, tomorrow 06:00
- Check result
- Growth-stage restriction
- Confidence
- 96%
- Decision
- The applicator's, not the agent's
As received
The application as the work order states it, with the field and the intended date.
Evidence used
- Label clause and version
- Bulletin for this field
- Growth-stage record
Why it stopped here
The label carries this crop but bars application after flowering begins, and the crop is past it.
What the score decides
Confidence decides how hard the applicator re-reads the clause, not what is lawful.
Action
ApplyChange the planAsk the agronomistValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every proposed application
From the prescription, work order or spray plan
Apply the label that governs it
Use the registered label, the supplemental and state labelling, the bulletin for that field and month, and the farm's own field record.
Do the reading before the tank is filled
Label, bulletin, intervals, certification and conditions are checked while the work order is written, not after the sprayer has run.
Put the hard cases in front of a person
A thin tank mix, an ambiguous stage call or a bulletin that changed reaches the applicator while the plan can still be changed.
Build an evidence trail
Retain the label version read, the bulletin obtained, the conditions at the time, the clause behind each flag and what the applicator decided — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Farm records & prescriptions
- Operations Center
- FieldView
- Trimble Ag
- prescriptions
Label & bulletin sources
- Registered labels
- supplemental labelling
- Bulletins Live! Two
- state restrictions
Weather & conditions
- Forecast
- in-field stations
- Wind and inversion data
Agent
Chemical-application checking
- Retrieves the label
- Checks the plan
- Drafts the record
Machines & product
- Spray controllers
- as-applied data
- Product inventory
- certification records
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six layers between the model and the sprayer
Each control wraps the one inside it. A check clears every layer before an applicator reads it, and the decision to apply sits outside all six.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Decide whether the plan may stand
- L3
- Decides whether the sources are current
- L4 – L5
- Keep the decision with a person and the record intact
- L6
- Pulls automation back when signals degrade
How Nestack evaluates it
Evaluate the whole check — not only the flag the applicator reads.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the check the applicator opens
- E1Final-output evaluationDid the check find every restriction the label and the bulletin carry?
- E2Step-level evaluationDid it read the right label version, the right clause and the right field record?
- E3Tool evaluationDid it query the bulletin for the right field boundary and month?
- E4Interval-conflict detectionWere re-entry, pre-harvest and following-crop conflicts caught before the plan was set?
- E5Slice evaluationHow does restriction recall change across crops and product types?
- E6Business outcomeHow many checks were wrong, and how many blocked a lawful application?
Floor — the application that does or does not happen
Failure modes
Where each failure originates in the agent
Seven failure modes plotted against the five stages of the agent lifecycle.
Agent lifecycle
Direction of processing →
01 · Retrieval
2 modes
- CA-01
Stale label version
A restriction that changed since the cached label is missed.
- CA-02
Bulletin not re-pulled
The field's limitation area changed after the plan was drawn.
Stage gathers
The label, the bulletin, the field record and the conditions
02 · Checking
2 modes
- CA-03
Rate read for the wrong crop
The rate is read from the wrong crop's row.
- CA-04
Interval fixed to a moved date
Harvest or field work moves after the check.
Stage tests
The proposal against every restriction those sources carry
03 · Record / write
1 mode
- CA-05
Record missing a required field
The record lacks a field the state requires.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- CA-06
Conditions cleared on a forecast
Wind or inversion differed from the forecast.
Stage returns
The flags and the clauses the applicator reads
05 · Change / Version
1 mode
- CA-07
Silent source regression
A feed or parser change moves what is checked, unnoticed.
Stage tracks
Model, prompt, label-source and bulletin-feed changes
- Sev-1 · a prohibited use is not flagged
- Sev-2 · the plan or the record is wrong
- Sev-3 · checking degrades, more to review
Affected slices
Label complexity is not spread evenly across crops
A missed-restriction rate that reads acceptably across the whole spray programme can sit almost entirely in the crops and mixes whose labels carry the most conditions. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Minor and specialty crops | 4.7% | 3.6× | Review | |
| Tank mixes, three or more | 3.4% | 2.6× | Review | |
| Fields inside a bulletin area | 2.5% | 1.9× | Watch | |
| Broadacre single-product applications | 0.8% | 0.6× | Normal |
Bar: missed-restriction rate lift vs. broadacre baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
A miss is closed out in the field before it is closed out in the agent
An application cannot be taken back. Once the sprayer has run, the work is containment, notification and the record — the loop decides the next field.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Missed restrictions, interval conflicts and false blocks break out by crop and by product.
- 02
Diagnose
Which was it — the label version, the bulletin pulled, the clause parsed or the field record?
- 03
Improve
The source, parser or block rule changes only on agronomy sign-off, tied to a version and a date.
- 04
Verify
The check is proved on held-out applications from that cohort, the missed ones included.
- 05
Learn
The application is replayed on every release, and the clause it broke joins the check set.
Learn → Detect
The return edge. A label or bulletin change is a source change — it lands in the check set before the next spray window, not after it.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, checking logic, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Workflow discovery and automation-boundary definition.Week 1
- 02Label, supplemental and bulletin sources.Week 1, Week 2
- 03Crop, product and prescription data mapping.Week 1, Week 2
- 04Field geometry and bulletin retrieval.Week 2
- 05Label-restriction parsing and check logic.Week 2, Week 3
- 06Re-entry and pre-harvest interval checks.Week 3
- 07Certification and restricted-use status checks.Week 3, Week 4
- 08Weather, drift and buffer condition checks.Week 4
- 09Restriction-recall and false-block tests.Week 4, Week 5
- 10Application-record drafting for the state.Week 5
- 11Farm-system and sprayer integration.Week 5, Week 6
- 12Observability, deployment and Agent Care handover.Week 6
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel
Final scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
| Capability✓ in scope · — not at this tier | PilotOne crop and product set | ProductionProduction farm-system integration | AdvancedMulti-state / contractor fleets |
|---|---|---|---|
| Introduced at Pilot | |||
| Label-restriction checking | ✓ | ✓ | ✓ |
| Bulletin retrieval for the field and date | ✓ | ✓ | ✓ |
| Re-entry and pre-harvest interval checks | ✓ | ✓ | ✓ |
| Application decision left with the applicator | ✓ | ✓ | ✓ |
| Baseline evaluation | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Certification and restricted-use checks | — | ✓ | ✓ |
| Weather, drift and buffer checks | — | ✓ | ✓ |
| Application-record drafting | — | ✓ | ✓ |
| Observability and evaluation | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-state and state-specific labelling | — | — | ✓ |
| Contractor fleets and enterprise controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on label and bulletin sources, farm-system integrations, crop and product range, record requirements, approval controls and deployment requirements.
- Separate from build
- Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bring
We build with it
01Your crop, product and prescription list
→Crop, product and prescription data mapping
Week 102The label sources you already work from
→Label, supplemental and bulletin source assessment
Week 103Field boundaries and the geometry you trust
→Field geometry and bulletin retrieval by date
Week 204Your applicators, their categories and certification records
→Certification and restricted-use status checks
Week 305Applications that went wrong, including the near misses
→Evaluation suite, regression cases and failure-mode testing
Week 406What your state and your auditors require in the record
→Application-record drafting to that requirement
Week 507Named certified applicators and an agronomist to review
→Review workflow, then supervised checks and validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the recall evaluation and the first supervised checks.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Workflow discovery, label sources and the automation boundary
W2Field geometry, bulletin retrieval and the first product set
W3Restriction parsing, interval checks and certification checks
W4Restriction-recall evaluation, false-block and drift-condition testing
W5Farm-system integration, record drafting and supervised checks
W6Applicators work from live checks, then Agent Care starts
- Reading the band
- Restriction recall is tested in week 4, before a check reaches an applicator in week 5. Nothing informs a spray decision until it has.
- At the end of W6
- Checks have run alongside your existing process and been read by the applicators who spray from them, then Agent Care takes over monitoring.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Agriculture AI agent
Build a checking agent around your spray programme.
Show us a season of applications, the label sources you work from and how a spray plan reaches an applicator today. We'll run those plans back through the check and show you which ones the label, the bulletin or an interval would have stopped.
- Typical delivery
- 4–6 weeks
- Deployment
- Your farm and spray stack
- Decision to spray
- Certified applicator, always
- After launch
- Agent Care available
Nestack Agents · Chemical-application checking
AGT-AGR-02 · Agent Care available after launch