30 billable report lookups / day
$0 / month for analysts, browser automation, and governed web workflows.
Syndu prices three access surfaces under one commercial model: evidence-graph access for people and governed web workflows, the Risk API for applications, and the Syndu MCP server for shared agent workflows. The same ladder supports cyber operations, fraud review, merchant-risk, and agentic investigation.
$0 / month for analysts, browser automation, and governed web workflows.
$0 / month for application-side contextual-risk scoring under workspace API keys.
$0 / month for hosted agent workflows with shared memory and governed hive-mind controls.
Compare web, API, and MCP on one page, then expand the customer account without changing the control plane. Active paid subscribers also unlock the in-product support desk.
The pricing page should do the commercial sorting work quickly: what gets metered, who it is for, and how to choose the first surface without guessing from a partial ladder.
Only the canonical report detail shells count: ip address, subnet, ISP, ASN, organization, city, region, and country. Direct web reads can stay requester-network-governed for buyers who want to cover a whole network, or customers can provision explicit IPs, one subnet, larger CIDR ranges, and web access credentials so the same billable shells meter to an account-bound pool instead.
The API product extends the same access model to risk-score calls. Each API request will be bound to the customer workspace, key material, and subscribed tier rather than to the smart-panel surface. This is the cleanest buying motion for fraud, product-risk, and integration teams that want contextual scoring plus writeback.
The MCP product meters authenticated investigation calls and governs a workspace-bound hive mind. Teams buy shared agent capacity against the evidence and risk layer, while workspace memory lookup, contribution, and approved hive-mind sharing stay included instead of being billed as a separate loop.
Quota resets every day. The dashboard and the documentation expose direct, API, and MCP posture under the same customer account without forcing the user to reason about internal panel fanout or ETL mechanics. Operational buyers can stay in reports and MCP; integration buyers can stay in API and writeback; both paths use the same control plane.
Use the selector to compare the three commercial surfaces directly. The workspace and billing posture stay shared; the ladder changes because the delivery contract changes. Every free tier now stops at 30 daily metered calls, while API writeback and MCP memory contribution remain included.
Canonical report shells for people, browser automation, and scraping stacks. Free evaluation starts at 30 metered report lookups per day.
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.
