Border0
Border0 is an identity-aware Zero Trust network access platform for securing access to infrastructure — SSH and RDP servers, PostgreSQL/MySQL/MSSQL/MongoDB/Elasticsearch databases, Kubernetes clusters, AWS consoles and S3 buckets, and any internal HTTP or TCP service. Instead of VPNs and shared credentials, Border0 publishes each resource as a policy-gated "socket," authenticates users through their existing SSO/identity provider, and records every session for audit. Its REST admin API (api.border0.com/api/v1) manages sockets, access policies, connectors, organizations, identity providers, service accounts, tokens, sessions, and audit logs, and is complemented by an official Go SDK, a Terraform provider, a CLI, and GitHub Actions. Border0 was acquired by Tailscale in March 2026.
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 Border0 the way a machine reads it — 20 machine-readable artifacts across 15 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 — Border0 scores 52.0/100 (developing), with a separate agent-readiness read of 65/100 (agent native). 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 Border0
Each block below is one kind of artifact we hold for Border0. 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 15
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.
Border0 Audit Actions API
The Audit Actions API from Border0 — 2 operation(s) for audit actions.
Border0 Client API
The Client API from Border0 — 6 operation(s) for client.
Border0 Connect API
The Connect API from Border0 — 1 operation(s) for connect.
Border0 Login API
The Login API from Border0 — 2 operation(s) for login.
Border0 Mtls-Ca API
The Mtls-Ca API from Border0 — 3 operation(s) for mtls-ca.
Border0 Organization API
The Organization API from Border0 — 4 operation(s) for organization.
Border0 Organizations API
The Organizations API from Border0 — 15 operation(s) for organizations.
Border0 Policies API
The Policies API from Border0 — 2 operation(s) for policies.
Border0 Policy API
The Policy API from Border0 — 1 operation(s) for policy.
Border0 Session API
The Session API from Border0 — 3 operation(s) for session.
Border0 Sessions API
The Sessions API from Border0 — 2 operation(s) for sessions.
Border0 Socket API
The Socket API from Border0 — 10 operation(s) for socket.
Border0 Stats API
The Stats API from Border0 — 2 operation(s) for stats.
Border0 User API
The User API from Border0 — 4 operation(s) for user.
Border0 Users API
The Users API from Border0 — 5 operation(s) for users.
Scroll within the panel for all 15 ·
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.
border0-mcp.yml
MCP SERVERSecurity 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.
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 Border0 — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 4
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/border0 · machine-readable index on apis.io