Conductor OSS is the Netflix-founded, Orkes-stewarded open source workflow and agentic AI orchestration platform. It provides a durable, event-driven workflow engine for coordinating microservices, long-running tasks, human approvals, and LLM-powered agents across any language or cloud, with first class support for HTTP, gRPC, Kafka, AMQP, SQS, and MCP-based tool calling.
Conductor OSS publishes 5 API contracts indexed on the APIs.io network, including Events API, Metadata API, Tasks API, and 2 more. Tagged areas include AI Agents, Durable Execution, Event-Driven, Microservices, and Netflix.
The Conductor OSS catalog on APIs.io includes 1 Spectral governance ruleset.
Conductor OSS’s developer surface includes documentation, getting-started guide, GitHub presence, engineering blog, YouTube channel, pricing, developer portal, and 20 more developer resources.
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/conductor-oss/"><img src="https://apis.io/badge/conductor-oss/card.svg" alt="Conductor OSS 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)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
11 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Access Clarityscores 23.7 — up to +15.3 composite points
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.
Conductor MCP is an official Model Context Protocol server for Orkes Conductor that exposes workflow execution, task management, and metadata operations as MCP tools so that LLM...
Workflow state is persisted at every step so executions survive worker restarts, server failover, and long human-in-the-loop waits.
Polyglot Workers
Tasks are executed by language-agnostic workers that poll the server, with official SDKs in Java, Python, Go, JavaScript / TypeScript, C#, Clojure, Ruby, and Rust.
System Tasks and Operators
Built-in HTTP, Kafka, JQ, wait, human approval, sub-workflow, fork, join, switch, do-while, and dynamic-fork operators compose workflows without writing code.
Agentic AI and LLM Orchestration
Native LLM tasks for 14+ providers, vector database integrations for RAG, MCP tool calling, and human-in-the-loop checkpoints make Conductor a runtime for agentic AI applications.
Event-Driven Triggers
Event handlers consume from Kafka, AMQP, SQS, NATS, and webhook sources to start workflows or complete tasks from external systems.
Horizontal Scalability
Stateless API servers and worker pools scale horizontally, with pluggable persistence (PostgreSQL, MySQL, Cassandra, Redis) and indexing (OpenSearch / Elasticsearch).
Operational Observability
Built-in metrics, structured logs, distributed tracing, and a Swagger UI on every server expose the workflow surface for operators.
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.