c/side
c/side (cside) is a client-side security platform that detects script attacks, AI agents, account takeover, and fraud at the browser layer. It provides active runtime detection that watches what third-party scripts, users, and agents actually do as they execute in the live browser session, in real time, rather than relying on static scans or block-lists, and it automates PCI DSS 4.0.1 requirements 6.4.3 and 11.6.1 (validated by a VikingCloud QSA). cside deploys as a single JavaScript snippet with no proxy and no DNS changes, and was the first client-side security product with integrated AI analysis. The platform protects websites from malicious third-party scripts, e-skimming, Magecart, and supply chain attacks, and adds device fingerprinting (102+ signals), VPN/bot/AI-agent detection, chargeback evidence, and privacy monitoring for GDPR, CCPA, and HIPAA. Founded in 2024 and backed by Uncork Capital, cside integrates via a CLI, Next.js and Vite plugins, a manual script tag, and Salesforce Lightning, and sends security alerts through webhook, S3, and Jira/Linear notification endpoints. cside publishes an llms.txt, a public read-only MCP server, and a Trust Center covering SOC 2 Type II, PCI SAQ-D, and ISO 27001.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles c/side the way a machine reads it — 5 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — c/side scores 40.9/100 (thin), with a separate agent-readiness read of 24/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile c/side
Each block below is one kind of artifact we hold for c/side. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
c-side-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
C Side Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for c/side — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/c-side · machine-readable index on apis.io