#assetflow
Live, measured metrics for the hashtag #assetflow from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #assetflow
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 12:45 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 12:45 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 12:45 UTCEverything below is measured over the latest 16 public posts (spanning ~276 hours).
Posting hours (UTC) — busiest: 15:00
Languages: English (16)
Avg boosts / post: 3.1
Used together with
Top of the latest posts
1/ I have been thinking about payments on the Fediverse (for a while). If you want to send an asset to a Fediverse ID such as: ＠joeblow＠example·com Or, and asset flow address such as: %joeblow＠example·com (Assuming we use the "%" character
3/ So, if you wanted an alternative to acct URIs that include a path, what are our options. The closest thing I can remember to an acct URI with a path is: tag URIs (IETF RFC-4151) https://datatracker.ietf.org/doc/html/rfc4151 (Tag URIs hav
2/ What happens if you want to send it to a sub- asset flow destination. The exact notation for it is yet to be decided, but, what if the Fediverse'ish ID is somethinglike: ＠joeblow＠example·com/prd123 Or, the asset flow address is something
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/assetflow