Do large reports multiply quota through panel fanout?
No. A report counts once when the canonical report shell is opened. Internal panels, charts, and subordinate endpoint calls are not separate billable units.
Practical answers for teams that want to consume Syndu reports at scale while keeping the business flow simple.
No. A report counts once when the canonical report shell is opened. Internal panels, charts, and subordinate endpoint calls are not separate billable units.
Yes. Direct access remains a first-class delivery mode for scraping, browser automation, and agent workflows. The Risk API and MCP server expand the platform; they do not erase the value of the published evidence graph.
The API returns a contextual risk score plus the matched dimensional details used to compute it. It exposes the evidence that explains how the contextual score was produced.
Syndu now treats direct web quota and API quota as two separate subscription services. The customer requests the relevant service from the dashboard, Syndu creates the matching PayPal subscription request against the mapped product and plan, emails the approval link, and activates the service only after verified PayPal webhook confirmation.
Support is reserved for accounts with an active paid Syndu subscription. Once a paid Direct access, Risk API, or MCP plan is live, the account can use the in-product support desk to open tickets, attach screenshots, and continue the thread until resolution.
No. Successful login, post-login operations, payment flows, dashboard activity, and websocket control traffic are kept out of the reporting pipeline.
Syndu turns outside-in network behavior into shared cyber-and-fraud context, then preserves decisions in memory for humans, applications, and agents. This manual is the public map of that platform: the evidence graph, the Risk API, the MCP server, and the governance layer that ties them together.
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 powers the Risk API, MCP tools, and the memory loop that preserves the resulting decisions.
Syndu is an external context layer for monitoring, hygiene review, agent workflows, and decision support. It complements SoC and SIEM processes rather than replacing them, while sharing the same evidence and memory model used elsewhere on the platform.
Syndu is also a decision surface for fraud, payments, merchant-risk, and trust workflows. The same outside-in evidence graph, Risk API, and governed memory loop help teams score, review, and preserve conclusions around risky identifiers.
The platform supports three access surfaces at scale: direct report access for large-scale browser or agent consumption, the Risk API for application-native scoring, and the MCP server for collaborative agent workflows.
Syndu is one platform with three access surfaces: direct access for report-shell consumption, API access for application-side scoring, and MCP access for agent collaboration. They sit under the same workspace, quota, and subscription control plane, but differ in delivery contract.
Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.
