Facilities AI agent · Chemical inventory
Safety Documentation AI Agent
Itemise every container against the datasheet library that 29 CFR 1910.1200(e)(1)(i) requires, apply the part 370 threshold tests at each location, and hold the return an owner or operator signs.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- One signature
- Two deadlines
- After launch
- Agent Care
What this agent does
Keeps the inventory, never signs the return
In
- 01
A chemical arrives, and § 370.10(a) keys the reporting duty to the OSHA datasheet.
- 02
A datasheet is revised, and § 1910.1200(e)(1)(i) wants the chemical list current.
Reason
- 03
A supplier label arrives revised, and 91 FR 1695 sets the employer date at 20 November 2026.
- 04
A quantity crosses the reporting threshold, and § 370.20 opens both duties.
- 05
A calendar year shuts, and § 370.45(a) sets 1 March for the year before it.
Decide
- 06
A return is assembled, and § 370.42(a) adds a penalty-of-law certification.
- 07
An extremely hazardous substance lands, and § 355.20 allows sixty days to notify.
Out
- 08
A release trips a reportable quantity, and § 355.43 says immediately.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent maintains the inventory and tracks the clocks. The owner or operator, or an officially designated representative, certifies under § 370.42(a).
Example workflow
One chemical, container to certification
- 1Container evidence receivedSafety data sheets, purchase records, store logs or stock feeds
- 2Chemical context assembledThe chemical, the location it is stored at, the threshold it answers to and the amount held
- 3Threshold evidence draftedThe chemical, the tests it was read against, the amounts and completeness
- 4Controls appliedDatasheet checks, threshold checks, storage-location checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the safety lane opens at the completeness gate.
Goes to the certifying officer to approve.
Adds a safety manager read first.
Safety review
The chemical is held with its datasheet, its amounts and the store it sits in.
Certify · Append evidence · Send to safety review
Certified — by the owner or operator
- 6Inventory and store records updatedOnly where write access and records policy allow it
- 7Outcome evaluatedThreshold accuracy, datasheet coverage, reviewer corrections and what the read found
Corrections
Each safety correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Certifying the Tier II return under § 370.42(a).
- Deciding a chemical sits below the reporting threshold.
- Making the § 355.43 release notification.
- Naming the officially designated representative.
Automation boundary
Agent acts unaided
- ✓Maintain the container inventory against the current.
- ✓Apply the § 370.10 threshold tests separately at each.
- ✓Track the 1 March return and the 20 November programme date together.
- ✓Assemble the return, its page count and the pages awaiting signature.
Nothing is certified or notified except by a named person, inside the agreed boundaries.
- Judging whether a mixture is one chemical or many.
- Telling a fire department the inventory is complete.
- Setting the hazard class a supplier has assigned.
- Changes to the inventory, the labels or the datasheets.
Example output
One chemical, annotated
Our EHS incident recordkeeping agent certifies what happened to people; this one certifies what is held in the building.
Inventory line · single chemical
Illustrative example- Chemical
- Above threshold, § 370.10(a)(2)
- Recorded as
- Read against the datasheet and the store log
- Test
- Above the reporting threshold
- Evidence of record
- Safety data sheet, 3 August 2026
- Confidence
- Held uncertified
- Held for
- The owner or operator, by name
As received
Taken from the safety data sheet and the store log — it reaches as far as those sources do.
What the record holds
- Safety data sheet
- Container record
- Storage location
Why no certification here
Whether a threshold is crossed is a § 370.10 judgement, not a model output.
What the score decides
Below the configured threshold a line picks up a safety read before the officer sees it.
Action
CertifyAppend evidenceSend to safety reviewValue
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 chemical
From the store that holds it
Where the evidence is used
A chemical inventory is not an emissions programme: this page records what sits in the building, while Title V permit reporting stays with the manufacturing environmental agent.
One list, two regulators
40 CFR 370.10(a) makes the OSHA datasheet duty the applicability test for part 370, so a single chemical list answers to both.
What was checked, and not found
The employee-count criterion at § 372.22(b) was never read verbatim, whether § 370.41 carries a certification of its own stayed unresolved, the exact last-amended date of part 355 could not be pinned, the Federal Register page of the 2023 chemicals-of-special-concern rule was not located, no state fee schedule reached primary text, the claim that every state collects Tier II rather than Tier I remains unconfirmed, and the extremely hazardous substance list, its planning quantities and the reportable quantities behind § 355.33 were not retrieved.
Build an evidence trail
The chemical, the quantity held and the officer who certified stay on the return.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Chemical and datasheet sources
- SDS library
- supplier feeds
- Product identifiers and labels
Container and storage records
- Store logs
- stock records
- Quantities held by location
Sites and storage locations
- Property system
- site roster
- Storage conditions and coordinates
Agent
Chemical inventory reporting
- Reads the datasheets
- Assembles the return
- Holds for the officer
Filing and case systems
- State portal
- ticketing
- Return, receipt and retention records
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six nets between the model and the officer
Six nets hung in sequence, the finest last. Whatever passes every one is drawn in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a line may stand
- L3
- Puts the certification in a person's hands
- L4 – L5
- Keep the chemical and the quantity behind it
- L6
- Holds the return uncertified when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the inventory line that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the return a fire officer reads
- E1Final-output evaluationDid the line record what the store actually holds?
- E2Step-level evaluationDid the agent read the right datasheet, the right threshold and the live stock?
- E3Tool evaluationDid it read and write the correct container record and the correct return?
- E4Confidence calibrationDo low-confidence lines actually attract more safety corrections?
- E5Slice evaluationHow does performance change across specific hazard classes?
- E6Business outcomeHow many lines needed a correction before the officer certified?
Floor — the inventory the operator answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each pinned at the stage where it first shows.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- KI-03
Stale stock read
The amount read is not the one now in the store.
Stage gathers
The chemicals, the sheets, the amounts and the sites
02 · Reasoning
2 modes
- KI-04
Threshold called on old stock
A quantity is judged against a superseded log.
- KI-06
Mixture read as one chemical
A blend is carried forward as a single entry.
Stage proposes
The chemicals, their thresholds and completeness
03 · Tool / write
2 modes
- KI-02
Thin line passed forward
A line moves on without the safety read.
- KI-05
Bound to the wrong store
A container is filed against the wrong location.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- KI-01
Certified, evidence unrecorded
The record shows a signature but not what backed it.
Stage returns
The return an officer signs and a fire crew reads
05 · Change / Version
1 mode
- KI-07
Silent threshold regression
A configuration change moves the threshold, not the line.
Stage tracks
Model, prompt, threshold rules and return fields
- Sev-1 · a chemical missing from the return
- Sev-2 · wrong amount reaches the return
- Sev-3 · source degrades, line held uncertified
Affected slices
Flammable liquid stores absorb the corrections
A class-level inventory-completeness figure can read clean while flammable liquid stores carry most of the rework. Nestack reports the correction rate by hazard class, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Flammable liquid stores | 9.8% | 3.6× | Review | |
| Corrosive chemical stores | 7.0% | 2.6× | Review | |
| Compressed gas stores | 4.4% | 1.6× | Watch | |
| Cleaning and janitorial stores | 1.7% | 0.6× | Normal |
Bar: correction-rate lift vs. cleaning and janitorial store baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What an uncounted drum costs
A cycle ends when the unlisted container is a standing case. That suite is what the next return assembled is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on flammable liquid stores.
- 02
Diagnose
The container in the yard that reached a threshold nobody had counted to is read back until one cause remains.
- 03
Improve
Changes leave numbered, and the chemicals that forced them travel attached.
- 04
Verify
One chemical case still failing is enough to stop the whole release.
- 05
Learn
The case is kept, and the inventory rules are rewritten alongside it.
Learn → Detect
The return edge. The next filing is measured against a suite one case longer.
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, inventory assembly, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Threshold-determination and automation-boundary work.Week 1
- 02Datasheet, container and site sources.Week 1, Week 2
- 03Chemical-to-datasheet and threshold-rule mapping.Week 1, Week 2
- 04Container and datasheet ingestion.Week 2
- 05Chemical, location and record binding.Week 2, Week 3
- 06Completeness scoring and review routing.Week 3
- 07Officer certification workflow.Week 3, Week 4
- 08Chemical-register system integration.Week 5
- 09Threshold and datasheet cases.Week 4, Week 5
- 10Guardrails and certification controls.Week 4
- 11Inventory-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation 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 site, one reporting year | ProductionProduction inventory workflow | AdvancedMultiple sites / entities |
|---|---|---|---|
| Introduced at Pilot | |||
| Inventory assembly to your thresholds | ✓ | ✓ | ✓ |
| Certifying officer release | ✓ | ✓ | ✓ |
| Container-inventory baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by hazard class | — | ✓ | ✓ |
| Certification workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Datasheet-library integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-site chemical stores | — | — | ✓ |
| Cross-year evidence packs | — | — | ✓ |
| Large chemical registers | — | — | ✓ |
| Multi-deadline threshold controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, register size, 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 storage locations and what each one holds
→Site mapping and container capture
Week 102Representative datasheets, labels and stock records
→Record binding, threshold logic and the inventory baseline
Week 203Your written programme under § 1910.1200(e)(1)
→Threshold mapping, datasheet binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→Datasheet, container and site-source assessment, then integration setup
Week 205Returns you would not want inspected
→Threshold cases and the evaluation suite
Week 406What no chemical inventory may guarantee
→Completeness scoring, review routing, guardrails and release controls
Week 307An owner or operator who may sign under § 370.42(a)
→Certification workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bars are drawn to the weeks the work genuinely needs, which is why the fifth carries a pair.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Inventory workflow discovery, threshold mapping and the automation boundary
W2Source integration and the container-inventory baseline
W3Chemical assembly, threshold logic and release controls
W4Evaluation suite, threshold cases and failure-mode testing
W5Datasheet-library integration, pilot lines and targeted corrections
W6One reporting year run under the site certifying officer, then Agent Care handover
- Reading the band
- Each bar covers only the weeks its own work is named for. Two of them sit inside week five, because the work does.
- At the end of W6
- When the inventory record validates, Agent Care picks the agent up.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Facilities AI agent
Build an inventory agent around the drum that crossed a threshold nobody counted to.
Show us one storage location and the datasheets behind it. Not a permit programme. A container inventory certified under penalty of law by the owner or operator under 40 CFR 370.42(a), beside a written hazard communication programme that nobody signs at all.
- Typical delivery
- 4–6 weeks
- Deployment
- Your storage locations
- One signature
- Two deadlines
- After launch
- Agent Care available
Nestack Agents · Chemical inventory
AGT-AF-04 · Agent Care available after launch