#openapispec
Live, measured metrics for the hashtag #openapispec from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #openapispec
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 09:24 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 09:24 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-27 09:24 UTCEverything below is measured over the latest 4 public posts (spanning ~18596 hours).
Posting hours (UTC)
Languages: English (3) · Dutch (1)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
🏗️ Als jullie een API bouwen, beginnen jullie dan met het definiëren van een openapi.yaml (Open API Spec, kortweg OAS) of start je direct met programmeren? Dat laatste is natuurlijk aantrekkelijk, maar niet altijd slim. Hoe je OAS-first we
Generate #REST #API Clients from #OpenAPISpec they said, it will be fun they said! Haven't opened the one for the #GitHub clients in a few months and was greeted by this pull 😎 .
@fran Head about @AsyncAPISpec before, but just now realized it is pretty compatible with #openapispec 😍
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/openapispec