#dxp
Live, measured metrics for the hashtag #dxp from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dxp
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-10-30 13:54 UTC1 uses by 1 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-10-30 13:54 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-10-30 13:54 UTCEverything below is measured over the latest 40 public posts (spanning ~29375 hours).
Posting hours (UTC) — busiest: 13:00
Languages: English (31) · German (7) · Japanese (2)
Avg boosts / post: 1
Top of the latest posts
The missing luggage finally arrived. We will soon set up the LZ-Beam See ya #v6d #hamr #dxp #dxped #dxpedition
📣Just Blogged: #SitecoreAI APIs Explained. Confused about #REST vs #GraphQL vs #MCP vs Edge Admin? Here's how to pick the right one for your #architecture : 🔗 https://www.amitk.net/blog/sitecoreai-api-guide-rest-graphql-mcp-edge-admin/ #D
Today we had a visit from the Youtuber Kuya Novo. He looked at our starion and we talked about life on the island See ya #v6d #hamr #dxp #dxped #dxpedition
#dxp across platforms
every network with a public tag surfaceFollow #dxp straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/dxp