All capabilities

Tag taxonomy

The vocabulary every other endpoint filters by — projects, chains, categories and people, with keyword rules and parent relationships.

17,500+tags

Two-thirds carry a parent, giving the taxonomy real hierarchy rather than a flat list. Each tag matches content through its keywords, which is the mechanism — and the failure mode, below.

What's in a record

Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.

  • id
  • name
  • slug
  • keywords
  • parents
{ "id": 136, "name": "bitcoin", "slug": "bitcoin", "keywords": [ { "id": 211, "name": "Bitcoin", "is_excluded": false, "ignore_trending": false, "match_type": "phrase", "case_sensitive": false, "required_terms": [] } ], "parents": [] }

Get it

A curl that runs against the live API right now, plus the MCP tool names for the same data.

curl https://api.alphaday.com/tags/?search=arbitrum

MCP tools

get_tagsget_tags_detail

What it's for

Three concrete questions this capability answers that a general crypto API does not.

  • Resolving a user's input to something the API accepts: every ?tags= filter on every other endpoint takes a slug from here, so autocomplete against this beats guessing.
  • Understanding why a query matched: keywords carries the actual rule — match_type, case_sensitive, required_terms, is_excluded — so a surprising result is explainable rather than mysterious.
  • Walking a hierarchy: 11,781 of 17,582 tags carry parents, so a chain rolls up its protocols and a category rolls up its projects without a mapping table of your own.

Known limits

Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.

914 tags have no keywords, and match nothing.

Walked all 17,582 tags on 20 Sep 2026: 914 (5.2%) carry an empty keywords array. A tag matches content only through its keywords, so these return zero results on every endpoint — not because the project has no coverage, but because nothing connects the tag to it. Check a tag returns results before building a scheduled job on it.

516 names are shared by more than one tag.

1,033 tags collide on 516 lowercased names. When a name is duplicated, one of the pair is often the keyword-less one — so picking a tag by name rather than slug can silently select the version that matches nothing.

Most tags carry one or two keywords.

The distribution over the full corpus: 9,297 tags have exactly one keyword, 6,982 have two, 381 have three or more. A single-keyword tag is as narrow as that one term, which is why an obvious project name can still under-match.

Figures and payloads verified against the live API on 2026-09-18. The API needs no key and no signup — see the full endpoint reference and the MCP server.