中文头条
直接来自中文新闻机构,点击即可打开原文。
习近平APEC宣布:提供2000万推动亚太共同体合作
法广 RFI 中文 · 1 小时前建宏福苑火灾纪录库者因揭名医之女涉嫌「请枪」反被控四宗罪:吹哨者变被告
法广 RFI 中文 · 1 小时前
特朗普总统在深圳对习近平说,希望美中共同推动结束俄乌战争
美国之音 中文 · 1 小时前
APEC的特色服飾:從克林頓皮衣到深圳「鯤鵬展翅」絲巾
BBC 中文 · 2 小时前
Anthropic上市:七位即將成為億萬富翁的創辦人
BBC 中文 · 2 小时前
特朗普总统在深圳先会普京,与习近平的双边峰会聚焦经贸分歧
美国之音 中文 · 3 小时前
美中俄深圳会晤前夕,美国国会议员对北京能否促普京结束战争看法不一
美国之音 中文 · 8 小时前
中美俄「三巨頭」坐在了一起,世界正滑向大國共管嗎?
BBC 中文 · 9 小时前- 第六届世界华文教育大会在海南召开 中新网 · 刚刚
- 新西兰前总理希普利:中国光伏储能为全球能源转型提供关键支撑 中新网 · 刚刚
- 月面聚光烧砖、远程送电、开采水冰:中国新技术推动人类从“探月”迈向“驻月” 中新网 · 1 小时前
- 暨南大学120周年华诞 校友师生共话“声教讫于四海” 中新网 · 1 小时前
- 梵谷名畫62.7億落槌創紀錄 納粹時期藏家爭議落幕 中央社 国际 · 2 小时前
- 克宮:普丁與川普會談42分鐘 會後「心情極佳」 中央社 国际 · 2 小时前
- 美官員稱科技當機潮非惡意網攻 專家指系統老舊釀禍 中央社 国际 · 2 小时前
- 新宿京王百貨「台灣夜市」熱鬧登場 雞排、蝦仁煎飄香 中央社 国际 · 2 小时前
- 中美俄元首会晤不会成为另一个雅尔塔会议 纽约时报中文网 · 5 小时前
- 习近平与高市早苗简短会面,中日关系无解冻迹象 纽约时报中文网 · 6 小时前
Endpoints
/api/v1/now.json: The live 脉搏: every active search spike with its score, 个国家 and stories./api/v1/events.json: Event records from the last 14 days: status, independent newsrooms, places and disputed figures./api/v1/event/{id}.json: One event record with every report: outlet, time, source tier, headline and link./api/v1/graph.json: Entities named in events and the observed links between them./api/v1/keys.json: The Ed25519 public key that signs every response.
Terms
- Free while in beta, with a link back to SpikeTrendWatch wherever the data is shown.
- Responses are cached for about two minutes; please do not request the same URL more than once a minute.
- Headlines and links belong to their publishers. Event status describes who is reporting an event, never whether it is true. Pulse and corroboration scores are experimental.
- Higher limits, history exports and saved monitors are planned for the Pro tier. Join the Pro list.
Threat-intelligence feed (STIX 2.1 / TAXII 2.1)
Connect a threat-intelligence platform or SIEM (OpenCTI, MISP, Microsoft Sentinel, Splunk, Anomali, ThreatConnect) to Spike's read-only TAXII 2.1 server. Discovery: https://spiketrendwatch.com/taxii2/. API root: https://spiketrendwatch.com/taxii2/api/. Authenticate with your Spike Pro API key as the password (HTTP Basic, any username) or as a Bearer token.
Collections: Spike Cyber (vulnerabilities with CISA exploitation status and EPSS, government cyber advisories, SEC cyber incident disclosures, threat actors with MITRE ATT&CK IDs), Spike Events (verified world events with places and sources) and Spike All. Filters: added_after, match[type], match[id], limit. Every object keeps its original source in external_references.
Incidents and the change feed
Provider incidents from official status pages, one record each, with numbered revisions: GET /api/v1/incidents, GET /api/v1/incidents/{id}. Every revision ever recorded, in order: GET /api/v1/changes?cursor=0. Store next_cursor and call again with it after any disconnect to receive what you missed. With a Spike Pro key, /api/v1/watch/changes returns only changes that match your workspace's watched services, with why each matched, and /api/v1/watch/deliveries returns delivery receipts. Contract: OpenAPI 3.1.
Live stream
GET https://spiketrendwatch.com/api/v1/stream?key=YOUR_KEY&types=signal,alert,cyber returns Server-Sent Events: signal (a rising signal and each status change), alert (USGS and GDACS alerts, government travel-level changes) and cyber (exploited vulnerabilities, advisories, SEC filings). Each connection runs 5 minutes and your client reconnects on its own (EventSource does this automatically).
Handoffs into incident tools
Send Spike an alert and it follows the matching Evidence Brief, then hands each material revision to your incident tool with a stable correlation key (the brief ID) and a stable delivery ID per revision and target. Corrections and scope changes go to the same downstream record and name the revision they supersede; the earlier revision stays readable at its ?as_of= link.
- Target:
POST /api/v1/watch/handoffswith{"kind":"incidentio","url":"https://api.incident.io/v2/alert_events/http/<source id>","token":"<source token>"},{"kind":"json","url":"https://…"}, or{"kind":"contract_sink"}for Spike's controlled receiver (a contract demonstration of incident.io's alert-event semantics, not incident.io). - Intake:
POST /api/v1/watch/intakewith a provider incident link, alert text containing one, or a StatusGator or IsDown alert. Unsupported, ambiguous or unrecorded inputs return 400 or 422 with candidates where Spike has them. - Payload (
spike.handoff/2): incident and brief IDs, exact revision URL, latest URL, what it supersedes, the material change,confirmed_provider_scopekept apart frompossible_customer_exposure, evidence with source links and times, open questions and a human-readable summary. Headers:spike-delivery-id,idempotency-key,spike-cursorand, when your workspace has a signing secret,spike-signature: t=…,v1=HMAC-SHA256(secret, t + "." + body). - Recovery: failed deliveries are retried up to 6 times with the same delivery ID. After an outage on your side,
POST /api/v1/watch/handoffs/replaywith{"cursor": <last cursor you stored>}; drop any delivery ID you already have. - Export:
GET /api/v1/briefs/{id}/handoff?format=json|incidentio|text&as_of=N(public evidence only) orGET /api/v1/watch/briefs/{id}/handoff(with your workspace's matches).
Runnable example: spike-handoff.mjs (intake, handoff, a missed delivery and replay). Try the payload on the synthetic demo: /api/v1/briefs/demo/handoff.
Verify a response
Fetch /api/v1/keys.json once, then check the spike-signature header against the exact response body with any Ed25519 library. Try it in your browser.