Perimeter 81

Perimeter 81 is a cloud-native Secure Access Service Edge (SASE) and Zero Trust Network Access (ZTNA) platform, now part of Check Point as Check Point Harmony SASE following its 2023 acquisition. It lets organizations build and manage secure, software-defined networks that connect a distributed workforce to on-premises resources, cloud infrastructure, and SaaS applications without legacy hardware appliances. The Harmony SASE Public API (v2.3) exposes programmatic control over networks, regions and points-of-presence, gateways, IPSec/WireGuard/OpenVPN tunnels, route tables, firewall policies, and network objects, using a two-step API-key-to-JWT access-token authentication model across US, EU, Australia, and India regional gateways.

Perimeter 81 publishes 17 API contracts indexed on the APIs.io network, including Application API, Enhanced Networks API, Enhanced Regions API, and 14 more. Tagged areas include Company, Cybersecurity, SASE, Zero Trust, and Networking.

The Perimeter 81 catalog on APIs.io includes 1 Spectral governance ruleset.

Perimeter 81’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, and 14 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

30.3/100 thin ▬ flat Agent 25/100 agent aware Front door AI 3/6 light saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Company Cybersecurity SASE Zero Trust Networking VPN ZTNA Security Cloud Security

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information Technology Management

BC-600

Enhanced NetworksEnhanced Route TablesEnhanced TunnelsNetworksOpenVPNStandard Networks

POST /v2.3/networks/enhanced GET /v2.3/networks POST /v2.3/networks GET /v2.3/networks/{networkId}

Cybersecurity Management

BC-620

Firewall Policy

PUT /v2.3/networks/{networkId}/policy

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 30.3/100 · thin

Contract Quality 9.9 / 19

Developer Ergonomics 2.9 / 15

Access Clarity 1.6 / 15

Operational Transparency 1.5 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/perimeter-81/"><img src="https://apis.io/badge/perimeter-81/card.svg" alt="Perimeter 81 on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 10.5 — up to +17.9 composite points
Developer Ergonomics scores 19.6 — up to +16.1 composite points
Contract Quality scores 52.9 — up to +11.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/perimeter-81/apis.yml: open an issue on github.com/api-evangelist/perimeter-81 to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Network Edge (CDN, networking, peering, edge compute)	builds-on	26.8 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

VPN

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Zero Trust Network Access

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 17

Individual APIs this provider publishes, each with its own machine-readable definition.

Perimeter 81 Application API

The Application API from Perimeter 81 — 3 operation(s) for application.

Perimeter 81 Enhanced Networks API

The Enhanced Network API allows you to manage and configure enhanced networks.

Perimeter 81 Enhanced Regions API

The Enhanced Region API allows you to manage and configure enhanced regions, including scale units.

Perimeter 81 Enhanced Route Tables API

The Enhanced Route Tables API allows you to manage and configure enhanced route tables of static and dynamic tunnels.

Perimeter 81 Enhanced Tunnels API

The Enhanced Tunnel API allows you to manage and configure enhanced tunnels.

Perimeter 81 Firewall Policy API

The Firewall Policy API from Perimeter 81 — 1 operation(s) for firewall policy.

Perimeter 81 Gateways API

The Gateways API from Perimeter 81 — 2 operation(s) for gateways.

Perimeter 81 IPSec-Redundant API

The IPSec-Redundant API from Perimeter 81 — 2 operation(s) for ipsec-redundant.

Perimeter 81 IPSec-Single API

The IPSec-Single API from Perimeter 81 — 2 operation(s) for ipsec-single.

Perimeter 81 Networks API

This API allows you to manage and configure standard networks using the old API and keep you BC.

Perimeter 81 Objects Addresses API

The Objects Addresses API from Perimeter 81 — 2 operation(s) for objects addresses.

Perimeter 81 Objects Services API

The Objects Services API from Perimeter 81 — 2 operation(s) for objects services.

Perimeter 81 OpenVPN API

The OpenVPN API from Perimeter 81 — 2 operation(s) for openvpn.

Perimeter 81 Regions API

The Regions API from Perimeter 81 — 3 operation(s) for regions.

Perimeter 81 Route Table API

The Route Table API from Perimeter 81 — 1 operation(s) for route table.

Perimeter 81 Standard Networks API

The Standard Network API allows you to manage and configure standard networks.

Perimeter 81 Wireguard API

The Wireguard API from Perimeter 81 — 2 operation(s) for wireguard.

Scroll for all 17

Open Collections 17

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Harmony SASE Public Application API

OPEN COLLECTION

Harmony SASE Public Application Enhanced Networks API

OPEN COLLECTION

Harmony SASE Public Application Enhanced Regions API

OPEN COLLECTION

Harmony SASE Public Application Enhanced Route Tables API

OPEN COLLECTION

Harmony SASE Public Application Enhanced Tunnels API

OPEN COLLECTION

Harmony SASE Public Application Firewall Policy API

OPEN COLLECTION

Harmony SASE Public Application Gateways API

OPEN COLLECTION

Harmony SASE Public Application IPSec-Redundant API

OPEN COLLECTION

Harmony SASE Public Application IPSec-Single API

OPEN COLLECTION

Harmony SASE Public Application Networks API

OPEN COLLECTION

Harmony SASE Public Application Objects Addresses API

OPEN COLLECTION

Harmony SASE Public Application Objects Services API

OPEN COLLECTION

Harmony SASE Public Application OpenVPN API

OPEN COLLECTION

Harmony SASE Public Application Regions API

OPEN COLLECTION

Harmony SASE Public Application Route Table API

OPEN COLLECTION

Harmony SASE Public Application Standard Networks API

OPEN COLLECTION

Harmony SASE Public Application Wireguard API

OPEN COLLECTION

Scroll for all 17

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Define network objects and update a Harmony SASE firewall policy

AGENT SKILL

Provision a Harmony SASE enhanced network with a region and IPSec tunnel

AGENT SKILL

Perimeter 81 API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Perimeter 81 Plans Pricing

0 plans

PLANS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Perimeter 81 API Rules

57 rules · 49 errors 7 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Perimeter 81 Openapi Overlay

2 actions · update · perimeter-81-openapi-original.json

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Perimeter 81 Authentication

http · 1 scheme

SECURITY

Perimeter 81 Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Perimeter 81 Agentic Access

107 operations · 63 acting · 14 human-in-the-loop

107 operations · 63 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

WellKnown

AgentSkill

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Lifecycle

Lifecycle

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

ParentCompany

ParentCompany

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: perimeter-81
name: Perimeter 81
description: Perimeter 81 is a cloud-native Secure Access Service Edge (SASE) and Zero Trust Network Access (ZTNA) platform,
  now part of Check Point as Check Point Harmony SASE following its 2023 acquisition. It lets organizations build and manage
  secure, software-defined networks that connect a distributed workforce to on-premises resources, cloud infrastructure, and
  SaaS applications without legacy hardware appliances. The Harmony SASE Public API (v2.3) exposes programmatic control over
  networks, regions and points-of-presence, gateways, IPSec/WireGuard/OpenVPN tunnels, route tables, firewall policies, and
  network objects, using a two-step API-key-to-JWT access-token authentication model across US, EU, Australia, and India regional
  gateways.
url: https://raw.githubusercontent.com/api-evangelist/perimeter-81/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- insight-partners
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - url: https://www.perimeter81.com/
    status: 301
    note: declared website redirects to https://sase.checkpoint.com:443/ — a different registrable domain (perimeter81.com
      -> checkpoint.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
image: https://www.perimeter81.com/favicon.ico
tags:
- Company
- Cybersecurity
- SASE
- Zero Trust
- Networking
- VPN
- ZTNA
- Security
- Cloud Security
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: perimeter-81:perimeter-81-application-api
  name: Perimeter 81 Application API
  description: The Application API from Perimeter 81 — 3 operation(s) for application.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Application
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-application-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-enhanced-networks-api
  name: Perimeter 81 Enhanced Networks API
  description: The Enhanced Network API allows you to manage and configure enhanced networks.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Enhanced Networks
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-enhanced-networks-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-enhanced-regions-api
  name: Perimeter 81 Enhanced Regions API
  description: The Enhanced Region API allows you to manage and configure enhanced regions, including scale units.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Enhanced Regions
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-enhanced-regions-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-enhanced-route-tables-api
  name: Perimeter 81 Enhanced Route Tables API
  description: The Enhanced Route Tables API allows you to manage and configure enhanced route tables of static and dynamic
    tunnels.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Enhanced Route Tables
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-enhanced-route-tables-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-enhanced-tunnels-api
  name: Perimeter 81 Enhanced Tunnels API
  description: The Enhanced Tunnel API allows you to manage and configure enhanced tunnels.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Enhanced Tunnels
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-enhanced-tunnels-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-firewall-policy-api
  name: Perimeter 81 Firewall Policy API
  description: The Firewall Policy API from Perimeter 81 — 1 operation(s) for firewall policy.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Firewall Policy
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-firewall-policy-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-gateways-api
  name: Perimeter 81 Gateways API
  description: The Gateways API from Perimeter 81 — 2 operation(s) for gateways.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Gateways
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-gateways-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-ipsec-redundant-api
  name: Perimeter 81 IPSec-Redundant API
  description: The IPSec-Redundant API from Perimeter 81 — 2 operation(s) for ipsec-redundant.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - IPSec-Redundant
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-ipsec-redundant-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-ipsec-single-api
  name: Perimeter 81 IPSec-Single API
  description: The IPSec-Single API from Perimeter 81 — 2 operation(s) for ipsec-single.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - IPSec-Single
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-ipsec-single-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-networks-api
  name: Perimeter 81 Networks API
  description: This API allows you to manage and configure standard networks using the old API and keep you BC.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Networks
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-networks-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-objects-addresses-api
  name: Perimeter 81 Objects Addresses API
  description: The Objects Addresses API from Perimeter 81 — 2 operation(s) for objects addresses.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Objects Addresses
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-objects-addresses-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-objects-services-api
  name: Perimeter 81 Objects Services API
  description: The Objects Services API from Perimeter 81 — 2 operation(s) for objects services.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Objects Services
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-objects-services-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-openvpn-api
  name: Perimeter 81 OpenVPN API
  description: The OpenVPN API from Perimeter 81 — 2 operation(s) for openvpn.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - OpenVPN
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-openvpn-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-regions-api
  name: Perimeter 81 Regions API
  description: The Regions API from Perimeter 81 — 3 operation(s) for regions.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Regions
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-regions-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-route-table-api
  name: Perimeter 81 Route Table API
  description: The Route Table API from Perimeter 81 — 1 operation(s) for route table.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Route-Table
  tags_raw:
  - Route Table
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-route-table-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-standard-networks-api
  name: Perimeter 81 Standard Networks API
  description: The Standard Network API allows you to manage and configure standard networks.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - Standard Networks
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-standard-networks-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
- aid: perimeter-81:perimeter-81-wireguard-api
  name: Perimeter 81 Wireguard API
  description: The Wireguard API from Perimeter 81 — 2 operation(s) for wireguard.
  humanURL: https://support.perimeter81.com/docs/api-getting-started
  baseURL: https://api.perimeter81.com/api/rest
  tags:
  - WireGuard
  tags_raw:
  - Wireguard
  properties:
  - type: OpenAPI
    url: openapi/perimeter-81-wireguard-api-openapi.yml
  - type: APIReference
    url: https://support.perimeter81.com/apidocs/introduction
  - type: GettingStarted
    url: https://support.perimeter81.com/docs/api-getting-started
  - type: Authentication
    url: authentication/perimeter-81-authentication.yml
  - type: ErrorCatalog
    url: errors/perimeter-81-problem-types.yml
  - type: Conventions
    url: conventions/perimeter-81-conventions.yml
  - type: RateLimits
    url: conventions/perimeter-81-conventions.yml
  - type: DataModel
    url: data-model/perimeter-81-data-model.yml
  - type: Conformance
    url: conformance/perimeter-81-conformance.yml
  - type: AgenticAccess
    url: agentic-access/perimeter-81-agentic-access.yml
common:
- type: Plans
  url: plans/perimeter-81-plans-pricing.yml
- type: ParentCompany
  url: https://apis.io/providers/checkpoint/
  name: Check Point
  x-relationship: acquired
  x-evidence: description names Check Point and https://www.perimeter81.com/ now redirects to sase.checkpoint.com (roadmap#390,
    corroborate-dead.py)
- type: CapabilityMap
  url: capabilities/perimeter-81-capability-edges.yml
  name: Perimeter 81 Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/perimeter-81-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/perimeter-81-openapi-overlay.yaml
- type: DomainSecurity
  url: security/perimeter-81-domain-security.yml
- type: Website
  url: https://www.perimeter81.com/
- type: DeveloperPortal
  url: https://support.perimeter81.com/docs
- type: Documentation
  url: https://support.perimeter81.com/docs
- type: APIReference
  url: https://app.swaggerhub.com/apis/Check-Point/Harmony-SASE-API
- type: GettingStarted
  url: https://support.perimeter81.com/docs/api-getting-started
- type: Support
  url: https://support.perimeter81.com/
- type: Blog
  url: https://www.perimeter81.com/blog
- type: Pricing
  url: https://www.perimeter81.com/pricing
- type: PrivacyPolicy
  url: https://www.perimeter81.com/privacy-policy
- type: StatusPage
  url: https://status.perimeter81.com/
- type: Lifecycle
  url: lifecycle/perimeter-81-lifecycle.yml
- type: LLMsTxt
  url: llms/perimeter-81-llms.txt
- type: WellKnown
  url: well-known/perimeter-81-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-20'
  status: nochange
  artifacts_added: 0
  pass: local-v1

Perimeter 81 API — frequently asked questions

Does Perimeter 81 have an API?

Yes. APIs.io lists 17 APIs from Perimeter 81, including Perimeter 81 Application API, Perimeter 81 Enhanced Networks API and Perimeter 81 Enhanced Regions API, and 14 more.

Is there an OpenAPI specification for the Perimeter 81 API?

Yes. APIs.io indexes 17 OpenAPI specifications for Perimeter 81, each linked for download from this page.

How do I authenticate with the Perimeter 81 API?

Perimeter 81 uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Perimeter 81 Authentication.

Is the Perimeter 81 API ready for AI agents?

Perimeter 81 has a Kin Score of 30.3 out of 100 (thin) and an Agent Readiness score of 24.7 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/perimeter-81"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/perimeter-81/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/perimeter-81/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.