All capabilities

News summary

An AI briefing written over the whole news corpus, optionally focused on a project — prose, not rows.

1 callone briefing

Returns a single object, not a list: { tags, summary, updated_at }. Pass ?tags= to focus it on a project; omit it for the market-wide brief.

What's in a record

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

  • tags
  • summary
  • updated_at
{ "tags": ["bitcoin"], "summary": "The US House Committee advances a Bitcoin reserve bill on a party line split. H100 CEO increases shares as Bitcoin treasury holds 3506 BTC. Bitcoin remains resilient amid broader market softness.", "updated_at": "2026-09-20T06:16:31.794075+00:00" }

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/items/news/summary/?tags=bitcoin

MCP tools

get_news_summary

What it's for

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

  • The cheapest possible "what happened" call: one request returns written prose an agent can relay directly, with no summarisation step and no token cost on your side.
  • Project briefings on demand: ?tags=ethereum narrows the briefing to that project rather than returning a filtered article list to summarise yourself.
  • A grounded opening paragraph for a digest, with the headline feed underneath it as the evidence — which is what /cookbook/weekly-ecosystem-digest builds.

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.

It is a singleton, not a collection.

No total, no results, no pagination. Anything written to consume the other endpoints' {count, next, results} envelope will fail here.

updated_at is the server's schedule, not yours.

The briefing is recomputed server-side on its own cadence, so two calls minutes apart usually return identical text. Treat it as a cached artifact and show its timestamp rather than implying it was written for this request.

tags is null when unfocused.

Called without a tag, the response carries tags: null rather than an empty array. Destructuring it as an array will throw.

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.