#ap_c2s
Live, measured metrics for the hashtag #ap_c2s from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ap_c2s
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-28 12:52 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-28 12:52 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 12:52 UTCEverything below is measured over the latest 2 public posts (spanning ~4.9 hours).
Posting hours (UTC)
Languages: English (2)
Avg boosts / post: 0.5
Used together with
Top of the latest posts
I guess I was a bit confused. After thinking about it again, I realised that webfinger is not the solution for C2S. In the meantime, I've seen discussions about oaut2 problems with #activitypub and @AndStatus #andstatus. #ap_c2s
#andstatus & #webfinger Hi there how does AndStatus implementing the webfinger? If that is the webfinger address: http://192.168.178.25:8082/.well-known/webfinger?resource=acct:a087558a-f6cf-416a-aade-8b6c74142daf isn't the the user a087558
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/ap_c2s