Check Point
Check Point Software Technologies is a global cybersecurity vendor providing network, cloud, endpoint, mobile, and email security through its Quantum, CloudGuard, and Harmony product families. Check Point exposes a wide range of REST APIs for security automation, including the Smart-1 Management API, Gaia OS API, CloudGuard cloud security posture API, Identity Awareness API, Spark and Zero Touch device management APIs, Harmony Email and Collaboration API, Threat Hunting (TH) API, and CloudGuard WAF API.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Check Point the way a machine reads it — 37 machine-readable artifacts across 21 APIs, 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 — Check Point scores 52.8/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Check Point
Each block below is one kind of artifact we hold for Check Point. 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.
APIs 21
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Check Point Spark Management API
REST API for centrally managing Check Point Quantum Spark SMB appliances including configuration and policy.
Check Point Zero Touch API
REST API for the Zero Touch deployment service that streamlines bring-up of new Check Point appliances.
Check Point Threat Hunting API
REST API for the Check Point Threat Hunting (TH) platform exposing threat intelligence, indicators, and hunting queries.
Check Point CloudGuard WAF API
Management API for the CloudGuard WAF cloud-native web application and API protection product.
Check Point Access Rules API
The Access Rules API from Check Point — 2 operation(s) for access rules.
Check Point Cloud Accounts API
The Cloud Accounts API from Check Point — 1 operation(s) for cloud accounts.
Check Point Compliance API
The Compliance API from Check Point — 1 operation(s) for compliance.
Check Point Events API
The Events API from Check Point — 1 operation(s) for events.
Check Point Findings API
The Findings API from Check Point — 1 operation(s) for findings.
Check Point Hosts API
The Hosts API from Check Point — 2 operation(s) for hosts.
Check Point Identity API
The Identity API from Check Point — 2 operation(s) for identity.
Check Point Interfaces API
The Interfaces API from Check Point — 1 operation(s) for interfaces.
Check Point Login API
The Login API from Check Point — 2 operation(s) for login.
Check Point NAT Rules API
The NAT Rules API from Check Point — 1 operation(s) for nat rules.
Check Point Networks API
The Networks API from Check Point — 1 operation(s) for networks.
Check Point Quarantine API
The Quarantine API from Check Point — 1 operation(s) for quarantine.
Check Point Routes API
The Routes API from Check Point — 1 operation(s) for routes.
Check Point Rulesets API
The Rulesets API from Check Point — 1 operation(s) for rulesets.
Check Point Services API
The Services API from Check Point — 1 operation(s) for services.
Check Point Sessions API
The Sessions API from Check Point — 2 operation(s) for sessions.
Check Point System API
The System API from Check Point — 1 operation(s) for system.
Scroll within the panel for all 21 ·
Open Collections 5
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Check Point CloudGuard API
OPEN COLLECTIONCheck Point Gaia API
OPEN COLLECTIONCheck Point Harmony Email API
OPEN COLLECTIONCheck Point Identity Awareness API
OPEN COLLECTIONCheck Point Management API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Checkpoint Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Checkpoint Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Checkpoint Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Check Point API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Check Point Access Rule
JSON SCHEMACheck Point Host Object
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Checkpoint Structure
JSON STRUCTURESecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Check Point — 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 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/checkpoint · machine-readable index on apis.io