Activity

Over time

Rounds created, payloads sealed into them, batches opened, and API calls, per day. Quiet days are drawn as quiet days rather than skipped, so the line never implies work that did not happen.

API calls

Requests to the public API at /v1, counted by family, split by whether they created something or read something.

The network's own plumbing is not in here. Operator nodes poll /v0 for work and post shares to it continuously, which at one point was twenty two thousand of the twenty two thousand four hundred calls on this page. That number was real and told you nothing, and it buried the two dozen that were somebody building something. The dashboard's own polling is excluded for the same reason.

Agent skill installs

Counted by the last line of the installer, after the files have landed. It sends no identifier, so read it as a floor on real installs rather than a headcount: anyone can call that endpoint, and nobody is being followed to find out whether they were the same person twice.

How fast a batch opens

Percentiles rather than an average. One slow batch drags an average somewhere no batch ever was, and the number worth knowing is the one most opens beat. The distribution underneath says whether that average would have been hiding two different behaviours.

What is being built

Pass a tag when you create a round or an auction. It is how you query your own later, and it puts your app on the board.

body: JSON.stringify({ opens_in: 3600, tag: 'my-app' })

What this page does not count

There are no accounts on this network, which is the point of it, so there is no user count to show. Nothing here observes a reader: no visitor count, no session, no cookie, no stored address. The numbers above are work the coordinator performed and had to record in order to perform it.

There is no map, and that is deliberate. Placing a caller means resolving their address against a geolocation database, which would have this coordinator handling visitor addresses in order to draw a picture. On a product whose whole claim is that it cannot read what you send it, that is not a trade worth making. A panel was built on the one signal that needed no address, the serving edge, and it turned out to report where this server runs rather than where anybody is, so it was removed rather than left up looking like a finding.

Two consequences worth stating plainly. Skill installs are a floor, for the reason given above. And sealed payload counts exclude the decoys every batch is padded with, so a quiet round does not appear busy.

Paid calls are the exception to all of it: an x402 payment settles on chain, so that number is not a floor or an estimate, it is a count of transactions anyone can check. See metered calls.