Posts from 133 project and protocol blogs in one feed — engineering write-ups, governance updates, announcements.
133 blogs behind the corpus. The record shape is identical to news (id, hash, title, url, image, author, published_at, source) but the corpus is project-authored, not media-authored — title points at engineering deep-dives, not press releases.
Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.
A curl that runs against the live API right now, plus the MCP tool names for the same data.
MCP tools
get_blogsget_blogs_detailget_trending_blogsThree concrete questions this capability answers that a general crypto API does not.
?tags=arbitrum returns 273 posts, and ?sources=kyberswap_blog returns the 158 from one blog.?period=0 gives the day's posts — 12 in the last 24 hours — and grouping by source.slug turns them into a 'which projects shipped today' report.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.
author is often null.
Verified on 18 Sep 2026: the example record carries author: null — project blogs frequently publish with no byline, even when the underlying CMS has one. Do not build a byline view that requires author to be present.
No sentiment or engagement fields.
Blog records carry likes (count) and is_liked (boolean), but no sentiment or sentiment_score. The endpoint is a feed, not a tone corpus — for sentiment-scoped blog analysis, score the short_description client-side.
sources needs the slug.
Verified on 18 Sep 2026: ?sources=kyberswap returns 0; ?sources=kyberswap_blog returns 158. Same slug ≠ name rule as the other content feeds — discoverable from any record's source.slug.