Endpoint reference

7 pages here. The API has 25 data routes in its catalogue, and 18 of them already have a product page at /{platform}-api/{endpoint}. This family covers the ones that did not — writing a second page for a route that already has one produces two near-identical pages competing with each other, which helps nobody and is a measurable indexing problem. Those three numbers are counted from the catalogue when this page renders.

The archive endpoints (3) — the ones nobody else has

These answer questions about the past. Every competitor reads a platform live, so their yesterday does not exist: ask them what was trending on 18 September and there is no answer to give. We recorded every hour. These three pages get the longest prose in this family on purpose — it is the only content here that cannot be published by anyone else.

• archive/trends — the history of a niche, grouped by itemHourly readings the archive already recorded, replayed for any interval you ask for. The endpoint that answers questions about the past rather than about now. — 1 credit per call. A call that finds nothing is charged all the same.
• archive/movers — what gained traction, ranked by the gainCompares two archived windows and ranks by points gained, not by position. Charged only when it finds movement. — 10 credits per call. A call that finds nothing costs nothing.
• archive/coverage — which niches exist, and how deep each goesThe free, keyless endpoint that every other archive call should start from. Served at /api/v1/nichos. — 0 credits per call. A call that finds nothing is charged all the same.

The platform routes (4)

Four routes without a product page, each for a specific reason that its page explains: one whose path breaks the convention every other platform follows, two that read a document another route was already downloading and discarding, and one keyed by a URI instead of a handle.

• profile/history — the daily history of a profile we archivedDay-by-day readings of a profile already in the archive, for one platform. Served at /api/v1/{platform}/history. — 1 credit per call. A call that finds nothing costs nothing.
• youtube/channel — a public channel, with the subscriber countThe YouTube route, and the one whose path breaks the convention every other platform follows. — 1 credit per call. A call that finds nothing costs nothing.
• pinterest/boards — the public boards of an accountName, description, pin count and followers per board — read from a document the profile route was already downloading and discarding. — 1 credit per call. A call that finds nothing costs nothing.
• bluesky/post — one post by its AT Protocol URIA single Bluesky post with likes, reposts, replies and quotes. The first platform route not keyed by a handle. — 1 credit per call. A call that finds nothing costs nothing.

All 7, with path and cost

Costs come from the endpoint table — the same row the charging function reads — and not from anything written into these pages. A price change by UPDATE shows up here without a deploy.

Machine-readable

The full spec is at /openapi.json, with each operation carrying its own cost. The spec is filtered by what is switched on right now, so it — not this page — is the answer to whether you can call something today.