Nexla
Nexla is an enterprise data integration and AI-data platform, founded in 2016 and headquartered in San Mateo, California. Its core abstraction is the Nexset — a logical, schema-aware, bi-directionally usable data product that Nexla generates automatically from any connected system. The platform spans ETL/ELT, streaming and CDC, API ingestion and delivery, RAG pipelines and, since 2026, an MCP Tools layer (MCP Studio, MCP Gateway, Agentic Probe) that turns governed Nexsets into task-scoped MCP servers for AI agents. Nexla exposes two public machine-readable contracts: a 274-operation OpenAPI 3.1 REST API covering flows, sources, Nexsets, sinks, credentials, transforms, projects, teams, organizations, access control, notifications, audit logs and metrics; and a 131-operation OpenAPI 3.1 GenAI (RAG + MCPaaS) API covering agentic RAG, nexset filters, skills, tools, toolsets, MCP gateway and audit receipts. First-party clients ship as a Python SDK, a TypeScript/JS SDK, a React embedding SDK and a Python CLI. Nexla is SOC 2 Type II, HIPAA, GDPR and CCPA compliant.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Nexla the way a machine reads it — 80 machine-readable artifacts across 4 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 — Nexla scores 60.6/100 (strong), with a separate agent-readiness read of 41/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Nexla's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nexla/"
title="Nexla on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nexla.svg"
alt="Nexla Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/nexla/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nexla/"
title="Nexla on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nexla/card.svg"
alt="Nexla Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Nexla
Each block below is one kind of artifact we hold for Nexla. 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 72
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.
Nexla Access Control API
Operations for managing access control to resources
Nexla Approval Requests API
Operations for managing all requests made by users without permissions.
Nexla Async Tasks API
Operations for managing asynchronous tasks.
Nexla Audit Logs API
Operations for reviewing the change history of resources.
Nexla Bulk Evaluation API
The Bulk Evaluation API from Nexla — 1 operation(s) for bulk evaluation.
Nexla Bulk Query API
The Bulk Query API from Nexla — 1 operation(s) for bulk query.
Nexla Clear Dataset Cache API
The Clear Dataset Cache API from Nexla — 1 operation(s) for clear dataset cache.
Nexla Clear Token Cache API
The Clear Token Cache API from Nexla — 1 operation(s) for clear token cache.
Nexla Code API
The Code API from Nexla — 2 operation(s) for code.
Nexla Code Containers API
Code containers are a general-purpose resource in the platform for storing user-defined functions that can be referenced by different modules for different purposes. These conta...
Nexla Credential Mappings API
The credential-mappings API from Nexla — 2 operation(s) for credential-mappings.
Nexla Credentials API
Operations for managing data credentials.
Nexla Custom Runtimes API
Operations for managing custom runtimes.
Nexla Data Maps API
The Data Maps API from Nexla — 4 operation(s) for data maps.
Nexla Data Sets API
The Data Sets API from Nexla — 1 operation(s) for data sets.
Nexla Destinations (Data Sinks) API
Operations for managing data sinks. Note that Destinations on the Nexla UI are aliased as `data_sinks` in the Nexla API reference model, so all endpoints and responses use the t...
Nexla Docs API
The Docs API from Nexla — 1 operation(s) for docs.
Nexla Flow API
The Flow API from Nexla — 2 operation(s) for flow.
Nexla Flows API
Operations for managing flows.
Nexla Gateway API
The gateway API from Nexla — 11 operation(s) for gateway.
Nexla Gen AI Recommendations API
Operations for requesting AI recommendations for documentation.
Nexla Genai Codegen API
The Genai Codegen API from Nexla — 1 operation(s) for genai codegen.
Nexla GenAI Configs API
The GenAI Configs API from Nexla — 1 operation(s) for genai configs.
Nexla GenAI Configuration API
The GenAI Configuration API from Nexla — 1 operation(s) for genai configuration.
Nexla GenAI Configurations API
Operations for managing GenAI configurations.
Nexla Genai Dsl Transform API
The Genai Dsl Transform API from Nexla — 1 operation(s) for genai dsl transform.
Nexla Genai Transform API
The Genai Transform API from Nexla — 1 operation(s) for genai transform.
Nexla Generate Document API
The Generate Document API from Nexla — 2 operation(s) for generate document.
Nexla Health API
The health API from Nexla — 5 operation(s) for health.
Nexla Health Check API
The Health Check API from Nexla — 2 operation(s) for health check.
Nexla Initialize API
The Initialize API from Nexla — 1 operation(s) for initialize.
Nexla Limits API
Rate limit endpoints
Nexla List Dataset Cache API
The List Dataset Cache API from Nexla — 1 operation(s) for list dataset cache.
Nexla List Models API
The List Models API from Nexla — 1 operation(s) for list models.
Nexla Lookup Enrich API
The Lookup Enrich API from Nexla — 1 operation(s) for lookup enrich.
Nexla Marketing Chat API
The Marketing Chat API from Nexla — 1 operation(s) for marketing chat.
Nexla Marketplace API
Operations for managing the marketplace domains and items.
Nexla MCP API
The Mcp API from Nexla — 2 operation(s) for mcp.
Nexla MCP Config API
The mcp-config API from Nexla — 3 operation(s) for mcp-config.
Nexla Mcp Query API
The Mcp Query API from Nexla — 1 operation(s) for mcp query.
Nexla MCP Tools API
The MCP Tools API from Nexla — 6 operation(s) for mcp tools.
Nexla Metrics API
Operations for retrieving metrics.
Nexla Nexla Admin API
The Nexla Admin Api API from Nexla — 1 operation(s) for nexla admin api.
Nexla Nexsets (Data Sets) API
Operations for managing Nexsets. Note that Nexsets on the Nexla UI are aliased as `data_sets` in the Nexla API reference model, so all endpoints and responses use the term `data...
Nexla Notifications API
Operations for managing notifications.
Nexla Org authentication configs API
Operations for managing organization authentication configurations.
Nexla Organizations API
Operations for managing the user's organization.
Nexla Private Query API
The Private Query API from Nexla — 1 operation(s) for private query.
Nexla Projects API
Operations for managing projects.
Nexla Quarantine Settings API
Operations for managing quarantine settings.
Nexla Query API
The Query API from Nexla — 1 operation(s) for query.
Nexla Receipts API
The receipts API from Nexla — 2 operation(s) for receipts.
Nexla Search Nexsets API
The Search Nexsets API from Nexla — 1 operation(s) for search nexsets.
Nexla Self Sign-Up Admin API
Operations for approving self-signup requests.
Nexla Self Sign-Up API
Operations for self-signup and verification.
Nexla Session Management API
Operations for managing your Nexla session programmatically. > Note: Unless unavoidable, we recommend starting your session from the Nexla UI and using the `Nexla Session Token`...
Nexla Sessions API
The sessions API from Nexla — 5 operation(s) for sessions.
Nexla Sources API
Operations for managing data sources.
Nexla Struct Extraction API
The Struct Extraction API from Nexla — 1 operation(s) for struct extraction.
Nexla Teams API
Operations for managing teams.
Nexla Tools API
The tools API from Nexla — 10 operation(s) for tools.
Nexla Toolsets API
The toolsets API from Nexla — 19 operation(s) for toolsets.
Nexla Transforms API
Operations for managing reusable attribute and record transforms.
Nexla Usage API
The usage API from Nexla — 4 operation(s) for usage.
Nexla User Settings API
The User Settings API from Nexla — 1 operation(s) for user settings.
Nexla Users API
Operations for managing user settings.
Nexla V2 Filters API
The v2-filters API from Nexla — 3 operation(s) for v2-filters.
Nexla V2 Nexset Info API
The v2-nexset-info API from Nexla — 2 operation(s) for v2-nexset-info.
Nexla V2 Query API
The v2-query API from Nexla — 3 operation(s) for v2-query.
Nexla V2 Skills API
The v2-skills API from Nexla — 3 operation(s) for v2-skills.
Nexla Webhooks API
Operations for sending events to the Nexla `webhook` connector.
Nexla .well Known API
The .well Known API from Nexla — 2 operation(s) for .well known.
Scroll within the panel for all 72 ·
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.
Nexla MCP Server (MCP Tools / MCPaaS)
MCP SERVERPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Nexla Plans Pricing
PLANSRate 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.
Nexla Rate Limits
RATE LIMITSEvent 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.
Nexla Webhooks
ASYNCAPISecurity Posture 4
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 Nexla — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nexla · machine-readable index on apis.io
This is an independent, third-party profile of Nexla, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.