Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Linx website screenshot

Linx

Linx Security is an AI-native identity security and governance platform covering the full identity lifecycle across human, non-human, and AI-agent identities. The platform builds an Identity Graph that normalizes identity data across SaaS, cloud, and on-prem systems, then layers identity security posture management (dormant accounts, admin sprawl, SSO bypass, missing MFA), modern IGA (access requests, approvals, provisioning, access certification), just-in-time access in place of standing privileges, automated joiner-mover-leaver lifecycle management, and an autonomous remediation agent called Autopilot. Linx also ships an MCP Server that exposes the Identity Graph and governed identity actions to LLM agents, plus an MCP Gateway for controlling AI agent traffic. Founded by Israel Duanis, Niv Goldenberg, and Sarit Reiner Frumkes, the company is headquartered in New York and has raised $85M from Cyberstarts, Index Ventures, and Insight Partners. Linx does not publish a public developer portal, API reference, or API specification — the API referenced in its Master Services Agreement is documented to customers only.

human only

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles Linx the way a machine reads it — 3 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 — Linx scores 19.6/100 (emerging), with a separate agent-readiness read of 12/100 (human only). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 19.6/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 12/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Linx

Each block below is one kind of artifact we hold for Linx. 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.

Linx MCP Server

MCP SERVER

Security 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.

Linx Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Linx Trust Center

SOC 2 Type II, SOC 1, ISO 27001:2022, ISO 42001, HIPAA, GDPR

SECURITY

Resources

Every other property we hold for Linx — 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

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

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/linx · machine-readable index on apis.io