Event-first schema
Signals are shaped around disruptions, geodata, engagement context, and workflow-ready metadata instead of generic article search.
Signals API
Operational geo and disruption signals for products and automations.
Signals API packages the same ZettaWire event layer behind customer keys, usage posture, archive packaging, and webhook rollout controls. Public access stays lightweight while paid access becomes a real operational surface for products, automations, and partner delivery.
Structured event schemaCustomer-managed keysArchive packagingWebhook rollout path
Primary use case
Operational APIs
Structured geo and disruption events packaged for internal tooling, partner products, and analyst automation.
Delivery posture
Keys + webhooks
Self-serve customer keys first, with private-beta webhook delivery layered on for production rollouts.
Archive model
24h to 24mo
Lightweight public evaluation stays separate from paid archive access and higher-throughput packaging.
Commercial motion
Starter -> Enterprise
Start with evaluation and account-backed usage, then move into support-led production packaging when integration depth grows.
GET /api/v1/stories?category=maritime&page=1
A denser signal shape for product and desk workflows.
A safe preview of the object shape developers receive from account-backed Signals API access.
{
"schema_version": "2026-04-22",
"event_id": "evt_20260422_red_sea_18431",
"story_id": "signal-18431",
"headline": "Port disruption near Suez corridor raises shipping risk",
"category": "security",
"score": 8.4,
"source_confidence": "multi_source",
"confirmation_status": "developing",
"canonical_url": "https://zettawire.com/stories/signal-18431",
"related_briefing_url": "https://zettawire.com/briefing/red-sea-shipping-risk",
"geo": {
"country": "Egypt",
"region": "Red Sea",
"lat": 30.04,
"lng": 32.56
},
"affected_entities": [
{
"name": "Suez Canal",
"type": "infrastructure",
"confidence": 0.86
},
{
"name": "Container shipping",
"type": "sector",
"confidence": 0.82
}
],
"key_facts": [
"Shipping advisories point to elevated risk near a major chokepoint.",
"The signal is linked to recent maritime security and regional escalation updates."
],
"archive_tier": "signals_growth",
"delivery_state": "api",
"published_at": "2026-04-22T12:20:00Z"
}Versioned
schema_version 2026-04-22 keeps clients explicit.
Canonical
Every event points back to a first-party ZettaWire URL.
Commercial
archive_tier and delivery_state separate evaluation from paid access.
Delivery surface
Customer-visible controls are part of the product, not hidden internal tooling.
Signals customers can move from simple API access into stronger delivery posture without leaving the commercial surface. That keeps rollout cleaner for beta customers and future enterprise packaging.
Key issuance and usage posture
Account-backed keys, rate windows, and package visibility for internal teams and customer integrations.
Webhook rollout controls
Growth and Enterprise accounts can manage endpoints, secrets, and delivery posture from the same product line.
Upgrade path for governed deployments
When integrations move from evaluation to production, archive depth and support packaging scale with them.
Operational controls
Customer-facing key issuance, rate posture, package visibility, and archive windows live in the same commercial surface.
Geo + briefing linkage
Stories keep geography, category, and briefing references attached so teams can bridge APIs with desk workflows.
Webhook rollout path
Growth and Enterprise customers can move from pull access into controlled webhook delivery without re-buying the product line.
Package matrix
Signals packaging keeps evaluation, internal automation, and production delivery clearly separated.
That separation keeps the public surface useful without collapsing the value of account-backed keys, longer archive access, and controlled rollout features.
| Package | Best fit | Throughput | Archive | Controls |
|---|---|---|---|---|
Public accessEvaluation | Prototype evaluation, public discovery, light internal experimentation | 60 requests/hr | 24-hour rolling window | No customer keys, no webhook delivery |
Signals StarterPaid | Analyst tooling, internal automation, early product integration | 1,000 requests/hr | 30-day event archive | 2 customer keys, usage visibility |
Signals GrowthPrivate beta | Production teams that need higher throughput and controlled delivery | 5,000 requests/hr | 12-month archive | 5 keys + webhook beta access |
Signals EnterpriseCustom | Partner programs, high-volume routing, governed deployments | 25,000 requests/hr | 24-month archive | Managed rollout, tailored routing, support-led controls |
Endpoint families
The API surface already maps to live story, category, and workflow objects.
Signals access is meant to plug into product or analyst systems quickly, so the dense route map matters as much as the packaging.
Core retrieval
/api/v1/stories
/api/v1/stories/{story_id}
/api/v1/categories
/api/v1/trending
Workflow linkage
/api/v1/stories/{story_id}/engagement
/api/v1/briefings
/api/v1/stories?category=maritime
Rollout path
A clearer progression from evaluation to production.
Signals API works best when teams understand the commercial posture early: evaluate publicly, activate account-backed keys, then expand into delivery controls.
1
Evaluate the surface
Use public access to inspect schema, categories, and story shape before you issue any managed credentials.
2
Move into account-backed keys
Starter introduces customer-owned keys, rate visibility, and a cleaner baseline for internal automation or analyst products.
3
Graduate to delivery controls
Growth and Enterprise add more throughput, longer archive depth, and webhook rollout for production systems.
Beta access
Request Signals API beta access with source attribution.
We use this form to understand developer demand, integration use cases, and which public pages produce qualified API leads.
Submissions are stored through newsletter attribution today, so the growth dashboard can group leads by page, campaign, and source while we keep API-key issuance entitlement-gated.