20 combined metered actions / day
$0 / month for analysts, browser automation, and governed web workflows moving from shared anonymous access into one owned workspace meter.
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 moving from shared anonymous access into one owned workspace meter.
$0 / month for application-side contextual-risk scoring that spends from the same owned workspace meter as the web and MCP surfaces.
$0 / month for hosted agent workflows with shared memory and governed hive-mind controls under the same owned workspace meter.
Reports, Risk API score calls, and metered MCP investigation now spend from the same daily budget so customers can understand value and upgrade pressure without juggling separate quota ladders.
The pricing page should do the commercial sorting work quickly: what gets metered, who it is for, and how the same owned workspace budget follows you across reports, Risk API usage, and MCP investigation.
Only the canonical report detail shells count: ip address, subnet, ISP, ASN, organization, city, region, and country. Signed-in direct web reads meter to the workspace that opened them. Anonymous visitors fall back to requester-network attribution until someone identifies themselves, and customers can still provision explicit IPs, one subnet, larger CIDR ranges, or web access credentials when they want a broader network perimeter to land in the same workspace on purpose.
Risk API score calls spend from the same owned workspace meter as report shells and metered MCP investigation. API keys stay account-bound for governance and attribution, but customers no longer have to learn a second quota ladder just to automate the same operating loop.
Metered MCP investigation also burns from that same workspace budget. Subject resolution, memory lookup, memory contribution, and approved hive-mind sharing stay included; the meter is for real investigation pressure, not for every supporting operation around it.
Quota resets every day under one owned workspace entitlement. The commercial ladder is now Free, Basic, Pro, Team, and Enterprise, with one daily meter following the customer across reports, Risk API usage, and MCP investigation instead of fragmenting the product into separate budgets.
Use the selector to compare the three product surfaces directly. The ladder itself is now shared: one workspace, one daily budget, five commercial tiers. Anonymous browsing still stays in a shared network budget until a workspace takes ownership, while API writeback and MCP memory contribution remain included.
Canonical report shells for people, browser automation, and scraping stacks. Signed-in usage spends from the same owned workspace meter as the API and MCP. Anonymous visitors still fall back to network attribution until claimed. Free workspace access starts at 20 combined metered actions per day.
Syndu gives computer-using agents outside-in risk context and a governed memory loop. This index maps the supporting docs: plugin install, MCP workflows, the Risk API, pricing, privacy, and the evidence depth behind the system.
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.
