#archivebot
Live, measured metrics for the hashtag #archivebot from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #archivebot
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-27 17:22 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-27 17:22 UTCNo related tags with measured usage found for #archivebot.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 17:22 UTCEverything below is measured over the latest 5 public posts (spanning ~166 hours).
Posting hours (UTC)
Languages: English (5)
Avg boosts / post: 0.8
Used together with
Top of the latest posts
I donʼt know whoʼs running the #ArchiveTeam #ArchiveBot, but you just donʼt load someoneʼs server like that. Loads multiples greater than Googlebot and Baidu. Not the first dodgy scraper found on Github, and I canʼt trust that people arenʼt
Not the first time the #ArchiveTeam #ArchiveBot has been accused of excessive traffic. https://utcc.utoronto.ca/~cks/space/blog/web/WebScrapingItsNotJustLoad?showcomments
@jackyan For ArchiveBot, visit http://archivebot.com and look for your site on the left. On the right of the same line will be a string of gibberish. Take it to #archivebot on Hackint IRC, post "!status <id>" and wait. The bot will quickly
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/archivebot