Manchetes em português

Direto das redações em português; um clique abre a matéria original.

  1. Isaltino deve achar que em Portugal vale tudo Observador · agora mesmo
  2. Estados Unidos: quadro de Van Gogh vende-se por €173 milhões para resolver litígio nazi Euronews · agora mesmo
  3. Europa fica fora do top 10 das melhores companhias aéreas de 2027 Euronews · agora mesmo
  4. Será que Xi, Trump e Putin mandam mesmo no nosso mundo? Observador · agora mesmo
  5. Lançamento de novo GTA, após 6 anos, leva muitos trabalhadores na Alemanha a tirar férias para jogar Euronews · há 1 h
  6. Coreia do Norte amplia instalação original de enriquecimento de urânio, alerta agência nuclear da ONU Euronews · há 1 h
  7. Mega-Sena 3088: sorteio desta quinta-feira (19) pode pagar R$ 40 milhões CNN Brasil · há 1 h
  8. “Eu Sou o Rocky” narra história de superação por trás de um clássico CNN Brasil · há 1 h
  9. Saiba quem é quem na Anthropic, gigante da IA que lança IPO nesta quinta CNN Brasil · há 1 h
  10. O amor descansa a gente: entre chegadas e partidas, notas de um coração Público · há 1 h

Endpoints

  • /api/v1/now.json: The live Pulso: every active search spike with its score, países 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.

  1. Target: POST /api/v1/watch/handoffs with {"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).
  2. Intake: POST /api/v1/watch/intake with 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.
  3. Payload (spike.handoff/2): incident and brief IDs, exact revision URL, latest URL, what it supersedes, the material change, confirmed_provider_scope kept apart from possible_customer_exposure, evidence with source links and times, open questions and a human-readable summary. Headers: spike-delivery-id, idempotency-key, spike-cursor and, when your workspace has a signing secret, spike-signature: t=…,v1=HMAC-SHA256(secret, t + "." + body).
  4. 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/replay with {"cursor": <last cursor you stored>}; drop any delivery ID you already have.
  5. Export: GET /api/v1/briefs/{id}/handoff?format=json|incidentio|text&as_of=N (public evidence only) or GET /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.