Radiation monitor
Your Geiger counter's readings show on Almighty's Radiation layer as a contributor counter, in microsieverts an hour (µSv/h), next to Safecast's.
1. Register in the Almighty app
There is no sign-up on this website. Open Almighty (the iPhone and iPad app, the Android app or the web app) and go to Settings → Contribute → Join Almighty Contribute. Sign in with Apple or with a code sent to your email (not as a guest), choose a display name and accept the contributor terms.
Then tap Add a station, choose Radiation monitor, give it a name
and set its place on the map. The app shows the station's key, which starts
alm_st_. Copy it straight away: it is shown once only. If you
lose it, make a new key in the app (the old one stops working).
Everyone else sees your station's place rounded to about 1 km, never the exact spot. What it sends is shared under CC BY 4.0 and credited "Data © Almighty contributors (CC BY 4.0)".
2a. A GQ GMC counter with Wi-Fi (GMC-320+, GMC-500, GMC-600, GMC-800)
These counters upload to gmcmap.com with a "user account ID" and a "counter ID". Point them at Almighty instead, with your station key in place of the counter ID. In the counter's menu, Server (or on the GQ software's Wi-Fi settings):
| Website | api.almighty.live |
|---|---|
| URL | v1/contribute/radiation/gmc |
| User ID | 0 (anything) |
| Counter ID | your station key, alm_st_… |
| Period | 1 minute or longer |
The counter then calls, for example,
http://api.almighty.live/v1/contribute/radiation/gmc?AID=0&GID=alm_st_…&CPM=15&ACPM=13.2&uSV=0.075
and Almighty answers OK.ERR0, as gmcmap does.
If the Counter ID field is too short for the key (some firmware versions take
only a few characters), put the key in the URL instead:
v1/contribute/radiation/gmc/alm_st_…, and leave the IDs as they are. If that doesn't
fit either, the counter can't be connected directly: send its readings from a computer with the
JSON below.
These counters can only use plain http, so the key travels unencrypted on the internet. It only lets someone send readings as your station; if you think it leaked, make a new key in the app.
2b. Any other counter: a Safecast-style JSON request
Send an HTTP POST with the key in the X-Station-Key header. The body
is one measurement, or a list of up to 60, in the shape Safecast's API uses. unit
is cpm (counts a minute) or usv (µSv/h). Any latitude and longitude in
the body are ignored: the station's place is the one set in the app.
curl -X POST http://api.almighty.live/v1/contribute/radiation \
-H "X-Station-Key: alm_st_…" \
-H "Content-Type: application/json" \
-d '{"captured_at": "2026-10-20T10:00:00Z", "value": 15, "unit": "cpm"}'
3. Checks on your readings
- Counts must be between 0 and 100,000 a minute, and dose rates between 0 and 1,000 µSv/h. Anything else is refused.
- When only counts are sent, the dose rate is worked out with GQ's usual factor for the M4011 / SBM-20 tubes in GMC counters (0.0065 µSv/h per count a minute) and the card says so. A reading whose µSv/h and counts disagree by more than three times that factor is kept but marked, and lowers the station's quality score.
- The map shows the level as Almighty's Radiation layer does: normal background is usually 0.05–0.2 µSv/h.
Limits
- One reading a minute per station is kept; more often gets 429 for the extra ones.
- Requests are small: at most 8 KB each (32 KB for a list of measurements).
- On a very busy day Almighty may stop taking new readings of this kind until midnight (UTC): your device gets an answer of 429 and can simply carry on; nothing is wrong with it.
- A station that sends nothing for two hours shows as offline in the app, and you can get a notification about it (Settings → Contribute → Notifications).
Help
Questions, or something not working? Email bonnyjames0@gmail.com with your station's name (never its key). See also Contribute to Almighty and Open data.