Event-first schema
Built around geopolitical and operational signals instead of generic article search.
ZettaWire Signals API packages the verified event stream behind customer keys, usage visibility, archive windows, and beta webhook controls. Public access stays lightweight; paid access unlocks deeper archive and operational delivery.
Signals shape
GET /api/v1/stories?category=maritime&page=1
{
"story_id": "signal-18431",
"headline": "Port disruption near Suez corridor",
"category": "Logistics",
"geo": {"country": "EG", "lat": 30.04, "lng": 32.56},
"engagement": {"total_reactions": 41},
"briefing_url": "/briefing/port-disruption-near-suez-corridor"
}Built around geopolitical and operational signals instead of generic article search.
Categories, geodata, engagement context, and briefing links stay attached to each event.
Issued keys, live rate posture, archive window visibility, and usage summaries in one place.
Growth and Enterprise customers can manage private-beta webhook delivery from the same surface.
Packaging
Keep lightweight evaluation public. Move teams to account-backed keys once they need archive depth, higher throughput, or webhook delivery.
Rolling public signal endpoints for lightweight integrations and evaluation.
Structured geo/ops event endpoints with self-serve keys for analyst workflows and internal tools.
Longer archive access, higher throughput, and private-beta webhook delivery for production teams.
High-volume account routing, tailored categories, private-beta delivery controls, and extended archive access.
Included endpoints
Webhook rollout
Growth and Enterprise accounts can manage webhook endpoints, secrets, delivery status, and recent failures without jumping to internal ops tooling.