Conductor website screenshot

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.

Conductor publishes 6 APIs on the APIs.io network, including Admin API, Event API, Metadata - Task API, and 3 more. Tagged areas include Automation, Orchestration, State, Tasks, and Workflows.

The Conductor catalog on APIs.io includes 1 event-driven AsyncAPI specification, 2 JSON-LD contexts, and 3 Spectral governance rulesets.

Conductor’s developer surface includes engineering blog and 6 more developer resources.

🌐 Visit website 📡 Source on GitHub
47.9/100 developing ▬ flat Agent 27/100 agent aware Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessFreemium
6 APIs 6 Features 4 Use Cases
AutomationOrchestrationStateTasksWorkflows

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 47.9/100 · developing
Contract Quality 20.8 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 4.1 / 13
Governance 8.3 / 12
Discoverability 6.5 / 10
Agent readiness — 27/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/conductor: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 6

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 API collections (OpenAPI-derived and Bruno).

Conductor API

OPEN COLLECTION

GraphQL 1

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

GRAPHQL

Pricing Plans 1

Published pricing tiers and plan structures.

Conductor Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Conductor Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Conductor Finops

FINOPS

Features 6

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

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

ASYNCAPI

Semantic Vocabularies 2

JSON-LD contexts and semantic vocabularies used across these APIs.

Conductor Conductor Context

0 classes · 0 properties

JSON-LD

Conductor Context

7 classes · 40 properties

JSON-LD

Spectral Rules 3

Spectral governance rulesets for linting and validating these APIs.

Conductor API Rules

3 rules · 2 warnings 1 info

SPECTRAL

Conductor API Rules

6 rules · 4 warnings 2 info

SPECTRAL

Conductor API Rules

14 rules · 8 errors 4 warnings 2 info

SPECTRAL

JSON Schema 19

Standalone JSON Schema definitions for this provider's data models.

EventHandlerAction

5 properties

JSON SCHEMA

EventHandler

6 properties

JSON SCHEMA

SearchResultTaskSummary

2 properties

JSON SCHEMA

SearchResultWorkflowSummary

2 properties

JSON SCHEMA

SkipTaskRequest

2 properties

JSON SCHEMA

StartWorkflowRequest

7 properties

JSON SCHEMA

TaskDef

20 properties

JSON SCHEMA

TaskExecLog

3 properties

JSON SCHEMA

TaskResult

9 properties

JSON SCHEMA

Task

24 properties

JSON SCHEMA

TaskSummary

16 properties

JSON SCHEMA

WorkflowDef

15 properties

JSON SCHEMA

Workflow

20 properties

JSON SCHEMA

WorkflowSummary

15 properties

JSON SCHEMA

WorkflowTask

17 properties

JSON SCHEMA

EventHandler

6 properties

JSON SCHEMA

TaskDef

20 properties

JSON SCHEMA

WorkflowDef

15 properties

JSON SCHEMA

WorkflowExecution

21 properties

JSON SCHEMA

Scroll for all 19

JSON Structure 15

JSON Structure definitions describing this provider's data shapes.

Conductor Conductor Event Handler Action Structure

5 properties

JSON STRUCTURE

Conductor Conductor Event Handler Structure

6 properties

JSON STRUCTURE

Conductor Conductor Search Result Task Summary Structure

2 properties

JSON STRUCTURE

Conductor Conductor Search Result Workflow Summary Structure

2 properties

JSON STRUCTURE

Conductor Conductor Skip Task Request Structure

2 properties

JSON STRUCTURE

Conductor Conductor Start Workflow Request Structure

7 properties

JSON STRUCTURE

Conductor Conductor Task Def Structure

20 properties

JSON STRUCTURE

Conductor Conductor Task Exec Log Structure

3 properties

JSON STRUCTURE

Conductor Conductor Task Result Structure

9 properties

JSON STRUCTURE

Conductor Conductor Task Structure

24 properties

JSON STRUCTURE

Conductor Conductor Task Summary Structure

16 properties

JSON STRUCTURE

Conductor Conductor Workflow Def Structure

15 properties

JSON STRUCTURE

Conductor Conductor Workflow Structure

20 properties

JSON STRUCTURE

Conductor Conductor Workflow Summary Structure

15 properties

JSON STRUCTURE

Conductor Conductor Workflow Task Structure

17 properties

JSON STRUCTURE

Scroll for all 15

Examples 15

Example request and response payloads for these APIs.

Conductor Conductor Event Handler Action Example

5 fields

EXAMPLE

Conductor Conductor Event Handler Example

6 fields

EXAMPLE

Conductor Conductor Search Result Task Summary Example

2 fields

EXAMPLE

Conductor Conductor Search Result Workflow Summary Example

2 fields

EXAMPLE

Conductor Conductor Skip Task Request Example

2 fields

EXAMPLE

Conductor Conductor Start Workflow Request Example

7 fields

EXAMPLE

Conductor Conductor Task Def Example

20 fields

EXAMPLE

Conductor Conductor Task Example

24 fields

EXAMPLE

Conductor Conductor Task Exec Log Example

3 fields

EXAMPLE

Conductor Conductor Task Result Example

9 fields

EXAMPLE

Conductor Conductor Task Summary Example

16 fields

EXAMPLE

Conductor Conductor Workflow Def Example

15 fields

EXAMPLE

Conductor Conductor Workflow Example

20 fields

EXAMPLE

Conductor Conductor Workflow Summary Example

15 fields

EXAMPLE

Conductor Conductor Workflow Task Example

17 fields

EXAMPLE

Scroll for all 15

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Conductor Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Conductor Agentic Access

39 operations · 21 acting · 1 human-in-the-loop

39 operations · 21 acting

AGENTIC

Use Cases 4

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

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

SpectralRules
SpectralRules
 Vocabulary
Vocabulary

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubRepository
GitHubRepository

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Company 2

The organization behind the API

LinkedIn
LinkedIn
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: conductor
name: Conductor
description: 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.
accessModel:
  pricing: freemium
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Freemium
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/conductor.png
url: https://raw.githubusercontent.com/api-evangelist/conductor/refs/heads/main/apis.yml
tags:
- Automation
- Orchestration
- State
- Tasks
- Workflows
kind: contract
access: 3rd-Party
created: '2025-01-08'
modified: '2026-05-19'
specificationVersion: '0.19'
position: Consuming
apis:
- aid: conductor:conductor-admin-api
  name: Conductor Admin API
  description: Administrative and health check APIs
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Admin
  properties:
  - type: OpenAPI
    url: openapi/conductor-admin-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
- aid: conductor:conductor-event-api
  name: Conductor Event API
  description: APIs for managing event handlers
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Event
  properties:
  - type: OpenAPI
    url: openapi/conductor-event-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
- aid: conductor:conductor-metadata-task-api
  name: Conductor Metadata - Task API
  description: APIs for managing task definitions
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Metadata - Task
  properties:
  - type: OpenAPI
    url: openapi/conductor-metadata-task-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
- aid: conductor:conductor-metadata-workflow-api
  name: Conductor Metadata - Workflow API
  description: APIs for managing workflow definitions
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Metadata - Workflow
  properties:
  - type: OpenAPI
    url: openapi/conductor-metadata-workflow-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
- aid: conductor:conductor-task-api
  name: Conductor Task API
  description: APIs for polling and updating tasks
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Task
  properties:
  - type: OpenAPI
    url: openapi/conductor-task-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
- aid: conductor:conductor-workflow-api
  name: Conductor Workflow API
  description: APIs for managing workflow executions
  humanURL: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  tags:
  - Workflow
  properties:
  - type: OpenAPI
    url: openapi/conductor-workflow-api-openapi.yml
  - type: Documentation
    url: https://conductor-oss.github.io/conductor/documentation/api/workflow.html
  - type: AsyncAPI
    url: asyncapi/conductor-conductor-asyncapi.yml
  - type: JSONSchema
    url: json-schema/workflow-def.json
  - type: JSONSchema
    url: json-schema/task-def.json
  - type: JSONSchema
    url: json-schema/workflow-execution.json
  - type: JSONSchema
    url: json-schema/event-handler.json
  - type: JSONLD
    url: json-ld/conductor-context.jsonld
  - type: JSONLD
    url: json-ld/conductor-conductor-context.jsonld
  - type: GraphQL
    url: graphql/conductor-graphql.md
common:
- type: AgenticAccess
  url: agentic-access/conductor-agentic-access.yml
- type: DomainSecurity
  url: security/conductor-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/conductor-inc-
- type: GitHubRepository
  url: https://github.com/conductor-oss/conductor
- type: SpectralRules
  url: rules/conductor-spectral-rules.yml
- type: Vocabulary
  url: vocabulary/conductor-vocabulary.yaml
- url: https://orkes.io/blog/
  type: Blog
- type: Features
  data:
  - name: Workflow Orchestration
    description: Define and execute complex workflows with sequential and parallel task execution.
  - name: Task Management
    description: Register, poll, and update granular task definitions with timeout and retry policies.
  - name: Event Handling
    description: Create event handlers to trigger workflows or tasks based on external events.
  - name: Workflow Search
    description: Search and filter workflow executions by status, type, and custom parameters.
  - name: Fault Tolerance
    description: Automatic retries, pause/resume, and graceful failure handling for long-running workflows.
  - name: Workflow Lifecycle Control
    description: Pause, resume, restart, retry, and terminate workflows programmatically.
- type: UseCases
  data:
  - name: Microservices Orchestration
    description: Coordinate complex business processes across distributed microservices without tight coupling.
  - name: Data Pipeline Automation
    description: Build and manage ETL and data processing pipelines with dependency tracking and error recovery.
  - name: Order Processing
    description: Manage multi-step order fulfillment workflows including payment, inventory, and shipping.
  - name: CI/CD Pipelines
    description: Orchestrate build, test, and deployment workflows with conditional logic and parallel execution.
- type: Integrations
  data:
  - name: Apache Kafka
    description: Trigger workflows and tasks from Kafka events using event handler subscriptions.
  - name: Amazon SQS
    description: Integrate with SQS for message-driven workflow initiation and task completion.
  - name: Docker
    description: Run Conductor server and workers in containerized environments for scalable deployment.
  - name: Orkes Cloud
    description: Use managed Conductor service from Orkes for enterprise-grade orchestration without infrastructure management.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com