This is the public documentation hub for Syndu's product surface: product brief, pricing, quota rules, privacy boundary, API usage, key management, and the operational resource pages that explain how the system works.
The manual is meant to be both a human sales surface and a machine-discoverable documentation root. Search engines, AI agents, developers, and buyers should be able to start here and branch cleanly into the relevant operational pages.
The API is documented as a first-class commercial surface: account-owned keys, separate API quota posture, email-led subscription activation, and explicit request and response boundaries.
The documentation also explains the report directories, the annotator catalog, and the role those published summary tables play in contextual risk scoring.
The end-to-end product story from raw unsolicited traffic into report directories, contextual risk scoring, and consumption modes.
The `score` endpoint contract, request and response format, validity boundaries, and quota posture.
How customers provision keys, manage API quota, and activate the API subscription service through the dashboard.
The public catalog of behavioral annotators that explain how Syndu interprets observed activity.
Syndu exposes a dimensional risk surface across network entities and geography: ip address, subnet, ISP, ASN, organization, city, region, and country. That same dimensional graph is also the basis for the planned risk API.
Syndu reports are external context pages for monitoring, hygiene review, and decision support. They complement SoC and SIEM processes rather than replace them.
The product supports two delivery modes: direct report access for large-scale browser or agent consumption, and the planned risk API for customers that want application-native scoring calls.
Syndu is a two-mode product: direct access for report-shell consumption and API access for application-side scoring. Both sit under the same account, quota, and subscription control plane, but they differ in delivery contract.
The `score` endpoint accepts an IP address and returns the full contextual-risk scoring object that Syndu already renders in the homepage and report headers. It is authenticated with account-owned API keys and metered against the API subscription service, not the direct web quota service.
API access is governed through account-owned keys, API-specific subscription tiers, and the same quota-control surface that already counts direct report access, while keeping the two services separate.
Registration unlocks the quota dashboard, plan selection, and the subscription flow while keeping report delivery quota-based.
This is a custom alert message.
Are you sure you want to proceed?