Hatchet
Hatchet is an open-source distributed task queue and workflow orchestration engine for background jobs, AI agents, and durable workflows. It is Postgres-backed, MIT-licensed, and ships with first-class SDKs for Python, TypeScript, Go, and Ruby plus a managed offering (Hatchet Cloud) and a self-hostable engine (Docker Compose, Hatchet Lite, Helm chart). The platform separates the orchestration engine from worker execution so workers can run on the operator's own infrastructure (Kubernetes, ECS, Render, Railway, Porter, or any container platform).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Hatchet the way a machine reads it — 110 machine-readable artifacts across 27 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 — Hatchet scores 61.1/100 (strong), with a separate agent-readiness read of 48/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.
How we profile Hatchet
Each block below is one kind of artifact we hold for Hatchet. 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 27
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.
Hatchet API Token API
The API Token API from Hatchet — 2 operation(s) for api token.
Hatchet CEL API
The CEL API from Hatchet — 1 operation(s) for cel.
Hatchet Durable Tasks API
The Durable Tasks API from Hatchet — 1 operation(s) for durable tasks.
Hatchet Event API
The Event API from Hatchet — 11 operation(s) for event.
Hatchet Feature Flags API
The Feature Flags API from Hatchet — 1 operation(s) for feature flags.
Hatchet Filter API
The Filter API from Hatchet — 2 operation(s) for filter.
Hatchet Github API
The Github API from Hatchet — 1 operation(s) for github.
Hatchet Healthcheck API
The Healthcheck API from Hatchet — 2 operation(s) for healthcheck.
Hatchet Log API
The Log API from Hatchet — 3 operation(s) for log.
Hatchet Metadata API
The Metadata API from Hatchet — 3 operation(s) for metadata.
Hatchet Monitoring API
The Monitoring API from Hatchet — 1 operation(s) for monitoring.
Hatchet Observability API
The Observability API from Hatchet — 1 operation(s) for observability.
Hatchet Rate Limits API
The Rate Limits API from Hatchet — 1 operation(s) for rate limits.
Hatchet Slack API
The Slack API from Hatchet — 2 operation(s) for slack.
Hatchet SNS API
The SNS API from Hatchet — 2 operation(s) for sns.
Hatchet Step Run API
The Step Run API from Hatchet — 7 operation(s) for step run.
Hatchet Task API
The Task API from Hatchet — 8 operation(s) for task.
Hatchet Tenant API
The Tenant API from Hatchet — 15 operation(s) for tenant.
Hatchet Tenants API
The Tenants API from Hatchet — 2 operation(s) for tenants.
Hatchet User API
The User API from Hatchet — 12 operation(s) for user.
Hatchet Version API
The Version API from Hatchet — 1 operation(s) for version.
Hatchet Webhook API
The Webhook API from Hatchet — 2 operation(s) for webhook.
Hatchet Webhook Workers API
The Webhook Workers API from Hatchet — 2 operation(s) for webhook workers.
Hatchet Worker API
The Worker API from Hatchet — 2 operation(s) for worker.
Hatchet Workflow API
The Workflow API from Hatchet — 16 operation(s) for workflow.
Hatchet Workflow Run API
The Workflow Run API from Hatchet — 6 operation(s) for workflow run.
Hatchet Workflow Runs API
The Workflow Runs API from Hatchet — 9 operation(s) for workflow runs.
Scroll within the panel for all 27 ·
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).
Hatchet API
OPEN COLLECTIONPricing 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.
Hatchet 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.
Hatchet Finops
FINOPSFeatures 15
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.
Durable Execution
Task and workflow state is persisted to Postgres so executions survive worker restarts, network partitions, and engine upgrades.
Low-Latency Scheduling
Sub-20ms task start times with intelligent assignment rules.
Code-First SDKs
Native language SDKs for Python, TypeScript, Go, and Ruby; tasks are versionable, testable functions.
Engine / Worker Separation
The orchestration engine and workers are decoupled; workers run on the customer's own infrastructure.
Postgres-Backed
Hatchet's only hard dependency is PostgreSQL; RabbitMQ is optional for higher-throughput deployments.
First-Class Rate Limits
Engine-level rate-limit primitive throttles task execution by named key, scope, and window — independent of HTTP rate limits.
CEL Event Filters
Common Expression Language filters bind incoming events to workflows with payload predicates.
Scheduled and Cron Workflows
One-shot scheduled runs and recurring cron-triggered workflows are first-class engine resources.
Webhook Workers
External HTTPS endpoints can be registered as workers; the engine delivers task runs as signed webhook requests.
OpenTelemetry Tracing
Workflows and tasks emit OTel traces; the engine exposes a trace lookup endpoint.
Replays and Restores
Failed or cancelled tasks can be replayed with the same input or restored to the run queue.
Multi-Tenant
Tenants isolate workflows, tasks, workers, and tokens; quotas and throughput are scoped per tenant.
Dashboard
Built-in web dashboard for inspecting runs, replaying tasks, and managing tenants.
Slack and SNS Alerting
Alerts can be dispatched to Slack channels or AWS SNS topics for ops escalation.
MIT-Licensed
Engine, API, SDKs, dashboard, and Helm chart are all MIT-licensed.
Scroll within the panel for all 15 ·
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.
Hatchet 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.
Hatchet API Rules
SPECTRALHatchet API Rules
SPECTRALJSON Schema 12
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.
APIToken
JSON SCHEMARateLimit
JSON SCHEMATenant
JSON SCHEMAV1Event
JSON SCHEMAV1Filter
JSON SCHEMAV1LogLine
JSON SCHEMAV1TaskEvent
JSON SCHEMAV1TaskSummary
JSON SCHEMAV1Webhook
JSON SCHEMAV1WorkflowRun
JSON SCHEMAWorker
JSON SCHEMAWorkflow
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
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.
Hatchet Api Token Structure
JSON STRUCTUREHatchet Rate Limit Structure
JSON STRUCTUREHatchet Tenant Structure
JSON STRUCTUREHatchet V1 Event Structure
JSON STRUCTUREHatchet V1 Filter Structure
JSON STRUCTUREHatchet V1 Log Line Structure
JSON STRUCTUREHatchet V1 Task Event Structure
JSON STRUCTUREHatchet V1 Task Structure
JSON STRUCTUREHatchet V1 Webhook Structure
JSON STRUCTUREHatchet V1 Workflow Run Structure
JSON STRUCTUREHatchet Worker Structure
JSON STRUCTUREHatchet Workflow Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 10
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.
Rate Limit Upsert Example
EXAMPLEV1 Event Create Example
EXAMPLEV1 Filter Create Example
EXAMPLEV1 Log Line List Example
EXAMPLEV1 Task Cancel Example
EXAMPLEV1 Task Get Example
EXAMPLEV1 Task Replay Example
EXAMPLEWorker List Example
EXAMPLEScroll within the panel for all 10 ·
Security 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.
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 7
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.
AI Agent Orchestration
Manage tool calls, conversation state, timeouts, and checkpointing for production AI agents.
Background Jobs
Classic distributed task-queue use case — replace Celery, Sidekiq, BullMQ, or RQ with durable equivalents.
Durable Workflows
Multi-step pipelines with retries, conditional branching, and exactly-once semantics.
Ingestion and Indexing
Keep vector databases, knowledge graphs, and search indexes up-to-date as upstream sources change.
Massive Parallelization
Fan out to thousands of workers for batch processing and embarrassingly parallel workloads.
Mission-Critical Workloads
Workloads where retries, checkpointing, and replay are non-negotiable (payments, billing, compliance).
Event-Driven Architectures
Use events + CEL filters to route external signals into the right workflows without bespoke routing code.
Scroll within the panel for all 7 ·
Integrations 13
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
PostgreSQL
The durability substrate; Hatchet ships with managed migrations and is happy on RDS, Cloud SQL, Neon, Supabase, or self-hosted Postgres.
RabbitMQ
Optional message bus for inter-service communication and high-throughput real-time updates.
Kubernetes
Official Helm chart at hatchet-dev/hatchet-charts for production self-hosting.
Docker
Hatchet Lite single-image deployment plus a production Docker Compose stack.
AWS (ECS, SNS)
ECS-friendly worker deployment patterns and first-class SNS alerting.
Slack
Native Slack alerting integration for run failures and SLA breaches.
GitHub
GitHub OAuth login for the dashboard plus repo-linked workflow source.
OpenTelemetry
Engine and SDKs emit OTel traces; the API exposes trace lookup.
Terraform
Official Terraform provider for managing Hatchet Cloud resources as code.
Homebrew
brew install via the hatchet-dev/homebrew-hatchet tap.
FastAPI
Documented quickstart for combining Hatchet Python SDK with FastAPI services.
Next.js
Multiple Next.js starter templates wire Hatchet into App Router and Pages Router projects.
Anthropic
Hatchet's durable-execution model is a natural substrate for orchestrating Anthropic Claude tool calls and multi-step agents; the hatchet-typescript-deep-research and hatchet-ty...
Scroll within the panel for all 13 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Hatchet Cloud
Fully managed orchestration engine on Hatchet's infrastructure with tier-included task-run allowances and SOC 2 / HIPAA controls.
Self-Hosted (Open Source)
MIT-licensed engine, API, dashboard, and Helm chart for running Hatchet on the operator's own infrastructure.
Hatchet Lite
Single-image bundled deployment of engine, API, and dashboard for development, testing, and low-throughput production.
Bring-Your-Own-Cloud (Enterprise)
Enterprise tier deploys the Hatchet engine inside the customer's own VPC while remaining managed by Hatchet.
Resources
Every other property we hold for Hatchet — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 11
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 11 ·
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/hatchet · machine-readable index on apis.io