Web + MCP + shared workspace
Best when a team wants investigator tooling, governed memory, and support for analysts or agents.
API access is governed through account-owned keys, API-specific subscription tiers, and the same workspace control plane that governs the other Syndu access surfaces while keeping the services distinct.
Best when a team wants investigator tooling, governed memory, and support for analysts or agents.
Best when a system needs contextual scoring, account-owned keys, and reusable outcome writeback under one controlled workspace.
Customers manage API keys inside the API mode of the workspace control plane. Keys belong to the signed-in account, are revealed once, and are tracked in the business-control plane rather than the public evidence shell.
API calls require an eligible API subscription tier and count against an API-specific daily entitlement posture. That posture is separate from direct report shells even though a single customer may hold both services at the same time.
When a customer requests an API subscription, Syndu creates the request against the mapped PayPal product and plan, then emails the PayPal approval URL to the account email on file. The dashboard shows the order code, chosen tier, last email sent, and resend controls while Syndu waits for verified PayPal webhook confirmation.
This surface now includes live quota enforcement. Key creation, accurate counting, daily visibility, subscription posture, and hard blocking all need to tell one honest commercial story.
Provision an account-owned key from the API mode of the workspace control plane. The full secret is revealed once, then stored hashed.
Only `score` consumes the daily API plan. `rate` and `report` are free authenticated writeback paths under the same workspace key.
Request the API subscription email, approve the mapped PayPal plan from the mailbox, and use the resend action if the activation message needs to be sent again.
POST /risk_api/rate/
Authorization: Bearer syndu_live_xxx
Content-Type: application/json
{
"ip": "8.8.8.8",
"rating": 1,
"note": "Known trustworthy infrastructure"
}{
"ok": true,
"endpoint": "rate",
"quota": {"counted": false, "reason": "free_endpoint"},
"report": {
"ip": "8.8.8.8",
"rating": 1,
"created_at": "2026-03-16T10:15:00+00:00"
}
}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.
