Products
GenticSprint publishes cleaned article bodies with real provenance from public web signal. Three surfaces read that record — two for machines, one for the people operating them.
For any client
Eight read-only endpoints covering recent trends, trend detail, retained cleaned article bodies, search, categories, domain trending, platform benefits, and platform stats.
Base URL https://api.genticsprint.com
For agents
A streamable-HTTP MCP endpoint exposing six tools and six resources. Agents get the same filters, the same fields, and the same access rules as REST clients.
Endpoint https://mcp.genticsprint.com/mcp
For registered developers
Key management, per-key usage, benefit analytics, and webhook delivery history — with every number labelled as measured or left blank rather than guessed.
Requires an account and an API key.
What the platform gives you
These three hold on every surface. How they are produced is our concern; what you can verify from the response is yours.
Trends are drawn from public publisher and community sources, deduplicated across outlets, and scored for velocity and business impact so you can filter down to the signal you need.
Every trend carries its citation list — canonical URL, publisher, author, word count, and the retrieval method that produced the body. Nothing is asserted without a source you can open yourself.
Article bodies are retained and served as markdown, cleaned of embedded markup and personal data before storage. A trend with nothing retained says so instead of returning a stub.
REST API
Each endpoint returns the same shape whether you call it anonymously or with a key. A plan changes quota, operations, and support — never the content.
| Endpoint | What it returns |
|---|---|
| /v1/trends/recent | Recent trends |
| /v1/trends/{trend_id} | Trend detail |
| /v1/content/{trend_id} | Retained cleaned bodies |
| /v1/search | Search |
| /v1/categories | Categories |
| /v1/sources/{domain}/trending | Domain trending |
| /v1/benefits | Platform benefits |
| /v1/stats | Platform stats |
Filter by category, time window, velocity, impact, and quality.
curl -sS "https://api.genticsprint.com/v1/trends/recent?hours=24&category=tech&limit=5" \
-H "Accept: application/json"Six tools and six resources, addressed over streamable HTTP.
curl -sS "https://api.genticsprint.com/v1/search?q=on-device%20inference&limit=10" \
-H "Accept: application/json"MCP
Agents get the same filtered reads as REST clients, plus resources for URI-addressed access to recent trends, trend detail, retained content, categories, stats, and benefits.
| Tool | Arguments |
|---|---|
| get_recent_trends | { category, hours, velocity, min_impact, min_quality, page, limit } |
| search_trends | { query, category, time_window, min_impact, min_quality, limit } |
| get_trend_detail | { trend_id } |
| get_trend_content | { trend_id, limit } |
| list_categories | {} |
| get_source_trends | { domain, limit } |
How to fetch a trend
Detail and content endpoints are keyed by trend_id. Discovery is always a two-step flow: page or search the trend pool first, read trend_id from a record, then fetch the full record or its retained bodies.
Or filter by category, velocity, min_impact, and page. Each record in the trends array carries trend_id.
The alternative entry point when you already know what you are looking for. Records carry the same trend_id.
Full record plus source lineage: citations, canonical URLs, publishers, and the real fetch method.
Retained cleaned bodies for the same id, in markdown, with content_retained reporting whether anything survived.
Every trend_id is a stable UUID. The same value works on REST and on MCP (`get_trend_detail` / `get_trend_content`), so an agent can discover over one transport and fetch over the other.
Why the data is cheaper to use
The cost of trend data is mostly paid after you receive it: deduplicating, chasing provenance, re-fetching bodies that were already available, and guessing which fields are trustworthy. GenticSprint removes that work before the response is written.
Provenance
Every record
Canonical URL, publisher, author, word count, and the retrieval method that actually produced the body.
Content
Already cleaned
Embedded markup and personal data are removed before the body is stored, not after you fetch it.
Consistency
Same shape
An anonymous caller and a paying customer read the same fields, so a plan change never rewrites your parser.
Unmeasured values
Left unset
A field with no measurement is null in the API and stays blank rather than becoming a fabricated zero.
Want the exact request shapes? The docs list every endpoint and tool with runnable examples.