Langflow
Langflow is an open-source low-code visual builder for AI agents, RAG pipelines, and LangChain-based workflows. It pairs a drag-and-drop React Flow frontend with a FastAPI backend that exposes every flow as a REST API, an MCP server, and an OpenAI-compatible Responses endpoint. Components are editable Python and ship with integrations across most major LLMs, vector stores, and observability platforms. Langflow was acquired by DataStax in 2025; DataStax itself was acquired by IBM and the deal closed on May 28, 2025, making Langflow an IBM property while remaining MIT-licensed open source. The project is the canonical reference implementation for visually composing LangChain agents — 149k+ GitHub stars, distributed via PyPI, Docker, Helm, and native Desktop apps, with a hosted cloud option run by DataStax.
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 Langflow the way a machine reads it — 71 machine-readable artifacts across 1 API, 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 — Langflow scores 41.7/100 (developing), with a separate agent-readiness read of 26/100 (agent aware). 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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Langflow'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/langflow/"
title="Langflow on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/langflow.svg"
alt="Langflow Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/langflow/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/langflow/"
title="Langflow on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/langflow/card.svg"
alt="Langflow 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 Langflow
Each block below is one kind of artifact we hold for Langflow. 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.
Langflow Base API
The Base API from Langflow — 6 operation(s) for base.
Langflow Chat API
The Chat API from Langflow — 6 operation(s) for chat.
Langflow Files API
The Files API from Langflow — 11 operation(s) for files.
Langflow Flow Events API
The Flow Events API from Langflow — 1 operation(s) for flow events.
Langflow Flows API
The Flows API from Langflow — 8 operation(s) for flows.
Langflow Health Check API
The Health Check API from Langflow — 2 operation(s) for health check.
Langflow Log API
The Log API from Langflow — 2 operation(s) for log.
Langflow MCP API
The MCP API from Langflow — 2 operation(s) for mcp.
Langflow mcp_projects API
The mcp_projects API from Langflow — 4 operation(s) for mcp_projects.
Langflow Monitor API
The Monitor API from Langflow — 12 operation(s) for monitor.
Langflow OpenAI Responses API API
The OpenAI Responses API API from Langflow — 1 operation(s) for openai responses api.
Langflow Projects API
The Projects API from Langflow — 4 operation(s) for projects.
Langflow Traces API
The Traces API from Langflow — 2 operation(s) for traces.
Langflow Users API
The Users API from Langflow — 4 operation(s) for users.
Langflow Workflow API
The Workflow API from Langflow — 2 operation(s) for workflow.
Scroll within the panel for all 15 ·
Open Collections 17
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).
API Collection
OPEN COLLECTIONLangflow Base API
OPEN COLLECTIONLangflow Base Chat API
OPEN COLLECTIONLangflow Base Files API
OPEN COLLECTIONLangflow Base Flow Events API
OPEN COLLECTIONLangflow Base Flows API
OPEN COLLECTIONLangflow Base Health Check API
OPEN COLLECTIONLangflow Base Log API
OPEN COLLECTIONLangflow Base MCP API
OPEN COLLECTIONLangflow Base mcp_projects API
OPEN COLLECTIONLangflow Base Monitor API
OPEN COLLECTIONLangflow Base OpenAI Responses API API
OPEN COLLECTIONLangflow Base Projects API
OPEN COLLECTIONLangflow Base Traces API
OPEN COLLECTIONLangflow Base Users API
OPEN COLLECTIONLangflow Base Workflow API
OPEN COLLECTIONLangflow
OPEN COLLECTIONScroll within the panel for all 17 ·
Features 22
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 22 ·
Semantic 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.
Langflow Context
JSON-LDSpectral Rules 2
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.
Langflow API Rules
SPECTRALLangflow API Rules
SPECTRALJSON Schema 5
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.
FlowRead
JSON SCHEMAMCPServerConfig
JSON SCHEMAMessageResponse
JSON SCHEMAFolderReadWithFlows
JSON SCHEMAUserRead
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.
Langflow Flow Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Langflow Create Flow Example
EXAMPLELangflow Run Flow Example
EXAMPLELangflow Webhook Example
EXAMPLESecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Langflow — 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 19
Reference material describing how the API behaves
Scroll within the panel for all 19 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 9
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 9 ·
Access & Security 4
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/langflow · machine-readable index on apis.io
This is an independent, third-party profile of Langflow, 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.