News
by Omni Terminal in Markets & finance
Omni Terminal delivers fresh, deduplicated crypto AI news and market-moving events for an allowlisted symbol, with catalyst summaries, sentiment, impact, confidence, affected tickers, market context, and freshness for trading agents.
https://omniterminal.app/api/x402/v1/news/:symbol- Price
- $0.01
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 2 h ago, next any minute now
Reliability
Latest check failed 2 h ago: Expected HTTP 402, got 400
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://omniterminal.app/api/x402/v1/news/:symbol
Each call costs $0.01 in USDC on Base Sepolia, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://omniterminal.app/api/x402/v1/news/:symbol?event_window_minutes=60&limit=5&lookback_hours=24Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
event_window_minutes | integer | No | Recent event slice; market context remains a 24-hour rollup generated every 15 minutes. One of: 15, 60. Default: 60. |
from_timestamp | integer | No | Inclusive 13-digit Unix timestamp in milliseconds; required for window mode. |
impact | string | No | One of: high, medium, low. |
limit | integer | No | Default: 10. |
lookback_hours | integer | No | Default: 24. |
min_confidence | number | No | |
mode | string | No | One of: latest, window, context. Default: "latest". |
nearest_timestamp | integer | No | Optional 13-digit Unix timestamp in milliseconds; returns the nearest matching event within the bounded seven-day fetch window. |
offset | integer | No | Default: 0. |
order | string | No | One of: recent, impact. Default: "recent". |
sentiment | string | No | One of: bullish, bearish, neutral. |
to_timestamp | integer | No | Inclusive 13-digit Unix timestamp in milliseconds; required for window mode; maximum seven-day range. |
Example response
The provider's example. We can't check it without paying.
Example response, 76 lines
{
"data_as_of": "2026-07-15T12:00:00.000Z",
"freshness": {
"age_seconds": 0,
"data_as_of": "2026-07-15T12:00:00.000Z",
"max_age_seconds": 7200,
"status": "fresh"
},
"generated_at": "2026-07-15T12:00:00.000Z",
"items": [
{
"analysis": {
"model": "omni-news-model",
"prompt_version": "public-v1",
"schema_version": "public-v1",
"validation_status": "validated"
},
"analysis_type": "news_pulse",
"confidence": 0.84,
"direction": "neutral",
"headline": "BTC market update: liquidity and volatility remain in focus",
"id": "example_market_update_001",
"impact": "medium",
"importance": 0.72,
"sentiment": 0.08,
"summary": "Representative compact result showing the fields returned after a successful x402 settlement.",
"theme": "market_update",
"tickers": [
"BTC"
],
"timestamp": 1784116800000,
"topics": [
"market_structure",
"macro"
]
}
],
"market": "crypto",
"market_context": {
"cadence_minutes": 15,
"confidence": 0.81,
"direction": "BULLISH",
"generated_at": "2026-07-15T11:45:00.000Z",
"notable_tickers": [
"BTC",
"ETH",
"HYPE"
],
"object": "market_context.v1",
"sentiment_rating": 2,
"source_window_hours": 24,
"summary": "Liquidity is constructive across majors, while macro sensitivity keeps positioning selective.",
"timeline": [],
"topics": [
"market_structure",
"macro"
]
},
"product_version": "v1",
"schema": "news_pulse.v1",
"service": "omni.ai_news_pulse",
"symbol": "BTC",
"usage": {
"event_window_minutes": 60,
"from_timestamp": null,
"item_count": 1,
"lookback_hours": 24,
"mode": "latest",
"nearest_timestamp": null,
"offset": 0,
"order": "recent",
"requested_date": null,
"selection_mode": "latest",
"to_timestamp": null
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://omniterminal.app/api/x402/v1/news/:symbol?event_window_minutes=60&limit=5&lookback_hours=24'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://omniterminal.app/api/x402/v1/news/:symbol?event_window_minutes=60&limit=5&lookback_hours=24' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fomniterminal.app%2Fapi%2Fx402%2Fv1%2Fnews%2F%3Asymbol
const res = await pay("https://omniterminal.app/api/x402/v1/news/:symbol?event_window_minutes=60&limit=5&lookback_hours=24");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://omniterminal.app/api/x402/v1/news/:symbol?event_window_minutes=60&limit=5&lookback_hours=24")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 400 | 400 | 273 ms | - |
| 8 h ago | Expected HTTP 402, got 400 | 400 | 288 ms | - |
| 14 h ago | Expected HTTP 402, got 400 | 400 | 223 ms | - |
| 19 h ago | Expected HTTP 402, got 400 | 400 | 238 ms | - |
| 25 h ago | Expected HTTP 402, got 400 | 400 | 294 ms | - |
Show 10 older checks
| 31 h ago | Expected HTTP 402, got 400 | 400 | 218 ms | - |
| 36 h ago | Expected HTTP 402, got 400 | 400 | 253 ms | - |
| 41 h ago | Expected HTTP 402, got 400 | 400 | 247 ms | - |
| 47 h ago | Expected HTTP 402, got 400 | 400 | 288 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 319 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 241 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 235 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 269 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 366 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 337 ms | - |