Conductor
Conductor allows you to build a complex application using simple and granular tasks that do not need to be aware of or keep track of the state of your application's execution flow. Conductor keeps track of the state, calls tasks in the right order (sequentially or in parallel, as defined by you), retry calls if needed, handle failure scenarios gracefully, and outputs the final result.
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 Conductor the way a machine reads it — 82 machine-readable artifacts across 6 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 — Conductor scores 52.2/100 (developing), with a separate agent-readiness read of 44/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Conductor
Each block below is one kind of artifact we hold for Conductor. 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 6
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.
Conductor Admin API
Administrative and health check APIs
Conductor Event API
APIs for managing event handlers
Conductor Metadata - Task API
APIs for managing task definitions
Conductor Metadata - Workflow API
APIs for managing workflow definitions
Conductor Task API
APIs for polling and updating tasks
Conductor Workflow API
APIs for managing workflow executions
Open Collections 1
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).
Conductor API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Conductor GraphQL API
Conductor allows you to build a complex application using simple and granular tasks that do not need to be aware of or keep track of the state of your application's execution fl...
GRAPHQLPricing 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate 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.
Conductor Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Conductor Finops
FINOPSFeatures 6
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.
Workflow Orchestration
Define and execute complex workflows with sequential and parallel task execution.
Task Management
Register, poll, and update granular task definitions with timeout and retry policies.
Event Handling
Create event handlers to trigger workflows or tasks based on external events.
Workflow Search
Search and filter workflow executions by status, type, and custom parameters.
Fault Tolerance
Automatic retries, pause/resume, and graceful failure handling for long-running workflows.
Workflow Lifecycle Control
Pause, resume, restart, retry, and terminate workflows programmatically.
Event 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.
Conductor Events API
Asynchronous event API for Conductor workflow orchestration platform. Conductor emits events when workflows and tasks change state, enabling reactive event-driven architectures....
ASYNCAPISemantic Vocabularies 2
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.
Conductor Conductor Context
JSON-LDConductor Context
JSON-LDSpectral Rules 3
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.
JSON Schema 19
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.
EventHandlerAction
JSON SCHEMAEventHandler
JSON SCHEMASearchResultTaskSummary
JSON SCHEMASearchResultWorkflowSummary
JSON SCHEMASkipTaskRequest
JSON SCHEMAStartWorkflowRequest
JSON SCHEMATaskDef
JSON SCHEMATaskExecLog
JSON SCHEMATaskResult
JSON SCHEMATask
JSON SCHEMATaskSummary
JSON SCHEMAWorkflowDef
JSON SCHEMAWorkflow
JSON SCHEMAWorkflowSummary
JSON SCHEMAWorkflowTask
JSON SCHEMAEventHandler
JSON SCHEMATaskDef
JSON SCHEMAWorkflowDef
JSON SCHEMAWorkflowExecution
JSON SCHEMAScroll within the panel for all 19 ·
JSON Structure 15
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.
Conductor Conductor Event Handler Action Structure
JSON STRUCTUREConductor Conductor Event Handler Structure
JSON STRUCTUREConductor Conductor Search Result Task Summary Structure
JSON STRUCTUREConductor Conductor Skip Task Request Structure
JSON STRUCTUREConductor Conductor Start Workflow Request Structure
JSON STRUCTUREConductor Conductor Task Def Structure
JSON STRUCTUREConductor Conductor Task Exec Log Structure
JSON STRUCTUREConductor Conductor Task Result Structure
JSON STRUCTUREConductor Conductor Task Structure
JSON STRUCTUREConductor Conductor Task Summary Structure
JSON STRUCTUREConductor Conductor Workflow Def Structure
JSON STRUCTUREConductor Conductor Workflow Structure
JSON STRUCTUREConductor Conductor Workflow Summary Structure
JSON STRUCTUREConductor Conductor Workflow Task Structure
JSON STRUCTUREScroll within the panel for all 15 ·
Examples 15
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.
Scroll within the panel for all 15 ·
Security Posture 1
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.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Microservices Orchestration
Coordinate complex business processes across distributed microservices without tight coupling.
Data Pipeline Automation
Build and manage ETL and data processing pipelines with dependency tracking and error recovery.
Order Processing
Manage multi-step order fulfillment workflows including payment, inventory, and shipping.
CI/CD Pipelines
Orchestrate build, test, and deployment workflows with conditional logic and parallel execution.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Apache Kafka
Trigger workflows and tasks from Kafka events using event handler subscriptions.
Amazon SQS
Integrate with SQS for message-driven workflow initiation and task completion.
Docker
Run Conductor server and workers in containerized environments for scalable deployment.
Orkes Cloud
Use managed Conductor service from Orkes for enterprise-grade orchestration without infrastructure management.
Resources
Every other property we hold for Conductor — 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.
Agent Surfaces 1
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
Access & Security 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/conductor · machine-readable index on apis.io