cloud1
cloud2
cloud3
cloud4
cloud5
cloud6
Quota rules
How Quotas Work
← Back to platform brief
Quota rules

How Quotas Work

Syndu identifies the consuming workspace when possible and otherwise falls back to the current requester network. That network evidence helps route quota, but it does not by itself prove ownership. The commercial handoff is ownership of access: move from a shared anonymous budget into a workspace that owns the reads.

Documentation Index Platform brief Pricing
Documentation index Platform brief Quota rules Privacy FAQ

Briefing Points

Quota rules

Direct web identity chain

Direct web access now starts with identity. Signed-in report reads meter to the user's workspace first. That handoff happens on the free plan too, because the point is owned access, not just a larger cap. If a visitor is still anonymous, Syndu falls back through anonymous requester organization and requester IP. Customers can optionally provision explicit IPs, one subnet, larger CIDR ranges, or a web access credential when they want anonymous traffic from a broader perimeter to land in the same owned workspace access.

Quota rules

Direct access counting

Directories, map tiles, chart endpoints, meta endpoints, and internal smart-panel fanout are non-billable. Syndu bills the canonical report shell, not the page internals. Signed-in direct reads always meter to the workspace that opened them. Provisioned IPs, subnets, network ranges, and authenticated web access credentials are the optional mechanism for claiming anonymous traffic into that same workspace instead of leaving it in the shared requester-network pool.

Quota rules

API access counting

The Risk API meters score requests by account workspace and API key. It does not inherit network ownership from the direct web surface, and the free `rate` plus `report` writeback endpoints do not consume score quota.

Quota rules

MCP access counting

The MCP surface meters authenticated investigation calls by account workspace and credential. Memory policy, memory lookup, and writeback into workspace memory or the hive mind do not consume that investigative quota. Private memory stays workspace-bound until the account explicitly turns on hive-mind sharing.

Quota rules

Operational simplicity

The customer still makes one business decision: how much Syndu capacity to buy. Syndu then exposes that decision through web, API, and MCP entitlements under the same workspace. Anonymous network fallback remains available for cold visitors, but the intended product posture is owned workspace access first, with broader network provisioning added only when the customer explicitly wants it.

Related Resources

Documentation

Syndu Documentation Index

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.

4 briefing points Documentation
Open article
Coverage

What Syndu Reports Cover

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.

4 briefing points Coverage
Open article
Operations

Using Syndu with SoC and SIEM Workflows

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.

4 briefing points Operations
Open article
Fraud operations

Using Syndu with Fraud, Payments, and Merchant-Risk Workflows

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.

4 briefing points Fraud operations
Open article
AI and scale

Consuming Syndu at Scale

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.

4 briefing points AI and scale
Open article
Delivery modes

Direct, API, and MCP Access

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.

4 briefing points Delivery modes
Open article
Register

Create a workspace to govern access to Syndu.

Registration unlocks the workspace control plane, plan selection, credential provisioning, and the subscription flow across web, API, and MCP access.

Register Sign in to workspace