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.
Once a customer can reach the report page, they can process it however they choose. Large consumers can still scrape or agent-run the report shells directly and budget by direct-access quota, whether the job is analyst review, fraud escalation, or case support.
Smaller firms, integration partners, fraud systems, and product teams may prefer a narrow API contract instead of full report scraping. The Risk API gives them the same evidence model in a compact programmable form plus writeback.
Teams using Codex, Claude Code, Cursor, Windsurf, or other MCP-compatible clients can resolve identifiers, explain risk, and preserve outcomes in a governed hive mind that survives any one chat session.
All three access surfaces stay tied to daily entitlement posture. The customer chooses how much Syndu context to consume, and the system enforces that through web, API, and MCP controls under one 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.
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.
