Score before you decide
Use the Risk API to score risky IPs and related network context before approving a transaction, account action, or merchant decision.
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.
Use the Risk API to score risky IPs and related network context before approving a transaction, account action, or merchant decision.
Move from one IP into subnet, org, ASN, geography, and related memory so a reviewer can understand the surrounding context instead of a single field.
Preserve dispute, abuse, chargeback, or merchant findings in workspace memory so the next case starts with prior outcomes instead of a blank screen.
Fraud and payments teams can call the Risk API before approval to add outside-in network context to a transaction, account, or merchant decision instead of relying only on internal event telemetry.
Reviewers can investigate a risky identifier through the report graph and understand the surrounding infrastructure, geographic concentration, provider footprint, and recurring organization patterns.
Syndu helps teams attach infrastructure and geography context to merchant reviews, dispute cases, chargeback clusters, and suspicious account operations so the decision record has more than one internal label.
MCP-compatible agents can resolve identifiers, explain risk, connect related subjects, and preserve the resulting outcome in private workspace memory for the next reviewer, escalation desk, or automated workflow.
The same product can support human review, programmable enrichment, and memory-backed agent workflows without changing the underlying evidence layer.
Best when a fraud or payments system needs contextual scoring plus writeback under one authenticated API contract.
Best when a human reviewer wants the full drill-down surface across IP, subnet, org, ASN, and geography.
Best when fraud or abuse teams want agents to investigate, explain, and remember outcomes across sessions.
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.
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.
Score risky IPs in real time, report lightweight business feedback, and push structured identifier outcomes back into workspace memory from the same authenticated API surface. Syndu keeps the contract simple: `score` is the metered read path, while `rate` and `report` are authenticated writeback endpoints that do not consume score quota.
Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.