Contract
{
"type": "object",
"anyOf": [
{
"required": [
"source"
]
},
{
"required": [
"project"
]
},
{
"required": [
"from"
]
},
{
"required": [
"to"
]
}
],
"properties": {
"to": {
"type": "string",
"minLength": 1,
"description": "Filter articles published on or before this time. Accepts Unix seconds or date string (2024-02-01). Example: 2024-02-01."
},
"from": {
"type": "string",
"minLength": 1,
"description": "Filter articles published on or after this time. Accepts Unix seconds or date string (2024-01-01). Example: 2024-01-01."
},
"limit": {
"type": "integer",
"default": 20,
"maximum": 50,
"minimum": 1,
"description": "Results per page (max 50). Example: 20. Defaults to 20."
},
"offset": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0,
"description": "Pagination offset. Example: 0. Defaults to 0."
},
"source": {
"enum": [
"coindesk",
"cointelegraph",
"theblock",
"decrypt",
"dlnews",
"blockbeats",
"bitcoincom",
"coinpedia",
"ambcrypto",
"cryptodaily",
"cryptopotato",
"phemex",
"panews",
"odaily",
"tradingview",
"chaincatcher",
"techflow"
],
"type": "string",
"description": "Filter by news source. Example: coindesk."
},
"project": {
"type": "string",
"minLength": 1,
"description": "Comma-separated project names to filter by. Example: bitcoin,ethereum."
},
"sort_by": {
"enum": [
"recency",
"trending"
],
"type": "string",
"default": "recency",
"description": "Sort order: recency (newest first) or trending (deterministic newest-first alias until engagement ranking is available). Example: recency. Defaults to \"recency\"."
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"data": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "The article's unique id (UUID-shaped)."
},
"title": {
"type": "string"
},
"source": {
"type": "string",
"description": "The article's source, uppercase (e.g. 'COINDESK') -- note the `source` input filter's own enum values are lowercase (e.g. 'coindesk')."
},
"summary": {
"type": "string"
},
"project_name": {
"type": "string",
"description": "The crypto project or asset the article is primarily about, e.g. 'Bitcoin'."
},
"published_at": {
"type": "number",
"description": "Unix seconds."
}
},
"additionalProperties": true
},
"description": "One entry per matching article, up to `limit` per call. Empty when no articles match the given filters (confirmed against a real future-dated, zero-match call)."
},
"meta": {
"type": "object",
"properties": {
"limit": {
"type": "number"
},
"total": {
"type": "number",
"description": "Total matching articles across all pages, not just this page's count."
},
"cached": {
"type": "boolean"
},
"offset": {
"type": "number"
}
},
"additionalProperties": true
}
},
"description": "A list of matching crypto news articles, newest-first by default.",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.00819 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 15, 2026
