For RMS, CAD and fire-service software
A firefighter taps a mic in your incident form and talks. Seconds later the form is filled, ready for review. You add the button. We build everything behind it, in your stack.
The demo takes under a minute, no sign-up. Sandbox API keys the same day.
What was the incident number assigned by dispatch?
55 s narrationFilled in 12 s
NERIS replaced NFIRS. Every department that had a reporting routine needs a new one.
Of departments that report a type are volunteer or combination. The people with the least patience for a form.
Fire departments in the federal directory, each addressable by its NERIS id on day one.
In the big records systems, voice is a paid add-on. Where it exists it is priced separately, and a department that has not bought it has nothing to talk to. If that line on your price list is empty today, this fills it.
Counts of fire departments in the country, from the NERIS public directory as of October 8, 2026, not customer counts.
What you build
You ship
In your incident form. A menu item or a shortcut works too.
Your server. Or, with no server tier, a key pinned to that install.
One message from the hosted mic, or one HTTP call if you record yourself.
We ship
The whole pipeline our own app runs, as one call.
Written in your language against your field list, with tests, sent as a patch.
Desktop, iOS, Android or web, adapted to how your app opens a window.
What the narration missed comes back named, with the question to ask.
A better model ships on our side. Your build does not change.
Two ways in
Shortest
One page of ours in a webview or an iframe. Recording, upload and the waiting screen happen inside it. It hands you the draft.
const widget = FireMic.mount(el, { sessionToken, onDraft: (n) => fillIncidentForm(n.neris, n.transcript, n.gaps), });Embedding guide
Most control
Record however you already do and post it once. Back comes the transcript, the draft in the shape NERIS accepts, and what is still missing.
curl https://app.fire-mic.com/v1/narrations \ -H "Authorization: Bearer $FIREMIC_KEY" \ -d '{ "department": "FD34007744", "audio": { "mime": "audio/mp4", "data": "<base64>" } }'API reference
Round trip for a one-minute narration is 10 to 15 seconds, measured against production on 23 September 2026.
Our offer
The plan we run for a new partner. It needs an engineer for a few hours and one department willing to pilot.
Thirty minutes. Send us a field list or a sample export.
Mapping and host code, in your language, as a patch on a branch you name.
Your engineer merges. We narrate real calls together and compare field by field.
Live key, outcome reporting on, and we watch the first narrations with you.
Or ask for a sandbox key and start on your own.
This API has no submit route. Your validation and your audit trail stay in front of every filing.
No FireMic accounts and no FireMic sign-in. The department is identified by its NERIS id.
Never shared with another partner. Never used to train anything outside FireMic. Retention is a setting you choose.
FAQ
No. There is no submit route on this API and it cannot reach ours. You stay the submitter, with your certification and your validation in front of every filing.
A button that opens our mic with a session token, and a handler for the draft it sends back. Or one HTTPS call if you record natively. The mapping from our draft to your fields is code we offer to write for you.
Yes. The mic is built for WebView2, and a key pinned to one department lets that install mint its own sessions. A key from one station cannot act for another. We offer to prove it in your client with your engineer before a pilot.
It scores 96 out of 100 on our benchmark: 15 test narrations, each run twice and scored on incident type, NERIS codes, key fields, times, the narrative and the actions taken (October 2026). Our own app files with it, and we re-run the benchmark before any model change. For a partner, we offer a per-department accuracy report built from the outcome data you send back, denominator attached.
Yes. A sandbox key is issued the same day you ask and runs against the same production pipeline. Live keys follow the agreement.
The pilot is free. After it, you pick one of two models: a fixed amount for each department that uses it, or one licence fee for your whole base. Both are billed quarterly or yearly, and either way you set your own price. If neither fits how you sell, we'll work out terms that suit you. After the first call, you get your figures in writing within two business days. The sandbox is free, so you can find out whether it works before anyone talks price.
Software vendors
A field list or a sample export is enough to start.
Talk to Mic
Collingswood firefighter and our founder
