Skip to content
unzoi docs
Search and navigation
Start here
REST API
MCP
Limits and plans
Agent clients
SDKs
Guides

Recipes / Build a crypto feed without the press releases

Build a crypto feed without the press releases

/stories in hybrid mode. This page is the operational half — what comes back, how it breaks, and what running it for real takes.

The request

GET /stories
  ?q=<asset or protocol>
  &mode=hybrid
  &from=<now - 24h>
  &limit=15

As a call you can paste:

curl -s -G "https://api.unzoi.com/stories" \
  -H "x-api-key: $UNZOI_KEY" \
  --data-urlencode "q=<asset or protocol>" \
  --data-urlencode "mode=hybrid" \
  --data-urlencode "from=<now - 24h>" \
  --data-urlencode "limit=15"

For an agent rather than a script, the same query is the list_stories MCP tool with these as its arguments.

Parameters used here

What comes back

Distinct events with outlet lists. Filtering to stories carried by several unrelated outlets removes most of the promotional noise with no model and no manual curation.

Field by field: the /stories response reference.

How this goes wrong

Ranking by recency alone. The most recent crypto items are disproportionately press releases, so a recency-ordered feed is close to an inverse quality ordering.

Adapting it

For a protocol rather than an asset, expect much lower volume and a higher proportion of technical commentary, so widen the window and lower the outlet-count filter. For regulatory crypto news, combine this with the regulatory recipe's longer window — enforcement actions follow the regulator's rhythm, not the market's.

Running it for real

Set the outlet-count threshold empirically by watching a week of output rather than picking a number; the right cutoff depends heavily on which assets you follow. Re-check it quarterly, because the ratio of promotional to genuine coverage moves with the market cycle and a threshold tuned in a quiet period will let far too much through in an active one.

Why this approach

The case for these parameters over the obvious alternatives — and when this recipe is the wrong tool entirely — is on the recipe's page on unzoi.com. It is kept there rather than repeated here, so the argument and the operations cannot drift apart.