Organization identity
Consistent org naming and allocation metadata helps Syndu connect activity to the right organization report and the right quota workspace.
Syndu uses the web's underlying metadata to simplify customer onboarding and quota ownership. Good network metadata improves attribution quality, product fit, and the accuracy of the shared context buyers rely on.
Consistent org naming and allocation metadata helps Syndu connect activity to the right organization report and the right quota workspace.
Accurate ISP, ASN, and geographic metadata makes higher-level reports more useful, especially when organizations consume the platform through city, region, or country views.
Customers are expected to maintain reasonable hygiene in how they represent and operate their networks. That gives the reporting model and the downstream memory loop a better base to serve them correctly.
Metadata hygiene is not only an ops sidecar. It improves attribution quality, which improves how confidently Syndu can route quota, score context, and preserve outcomes against the right subject or workspace.
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.
