#m3api
Live, measured metrics for the hashtag #m3api from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #m3api
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 18:49 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 18:49 UTCNo related tags with measured usage found for #m3api.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 18:49 UTCEverything below is measured over the latest 19 public posts (spanning ~21000 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (19)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
unfinished thought: it would be quite good to have something like the Toolforge Abandoned Tool policy (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Abandoned_tool_policy) for non-tool Wikimedia code, such as libraries (e.g. #m3api) or
I’m planning to create a library that makes it easier to use the MediaWiki REST API from applications which already use m3api to interact with the Action API; input welcome here, as I’m not actually very familiar with the REST API: https://
New m3api-oauth2 release! (m3api-oauth2 is still an m3api extension package to authenticate users using OAuth 2.) This just declares compatibility with the newly released m3api-rest v0.2.0, nothing special :blobfoxhappy: https://gitlab.wiki
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/m3api