The bot has a name because it introduces itself
The background fetch fleet got renamed from worker to bot, and that name rides along in the User-Agent on every outbound request it makes.
A background worker doesn't need a name anyone outside the company will ever see. A thing that shows up in someone else's server logs does.
The fleet that pulls IP blocks, weather station data, and geofeed downloads was just called "worker" internally, until it wasn't. It got renamed once, confirmed out loud a few messages later, and that was the whole naming process.
User-Agent: Parsebot/1.0 (+https://parseapi.com/bot; hello@parseapi.com)
The rename shows up on someone else's server, not just this one
Every outbound request the fleet makes, to a national weather service, a regional internet registry, a geofeed host, carries that exact string. Whoever runs the server on the other end sees "Parsebot" in their own logs. The rename never stayed an internal decision, it became the fleet's public identity the first time it made a request.
Try it
Check the User-Agent header on any request parseAPI's fleet sends upstream. Same name it picked for itself, still introducing itself.