Compare

Hatchet vs Make

Hatchet scores higher on the AgentReady, 66/100 against 62/100. They differ on 7 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Hatchet. Hatchet is a developer platform that helps engineering teams build and deploy mission-critical AI agents, durable workflows, and background tasks.

Make. Make is a visual AI automation platform that enables users to connect any app, data source, or AI model to build and manage automations and AI agents visually, in code, or via natural language prompts.

Where Hatchet is ahead

Hatchet passes clear canonical domain and clear product positioning, and Make does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: limits / constraints documented. Make misses it.

And on adopt, no mandatory sales call. Make misses it.

Finally, on operate, idempotency support. Make misses it.

Where Make is ahead

Make passes structured api reference, and Hatchet does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.

It also holds operate: structured, predictable output. Hatchet misses it.

What neither does

Both fail openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, agent-compatible signup flow, programmatic credential creation, cli available, machine-readable errors, retry behavior documented, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover is whether an agent can find the product at all without being told it exists. Hatchet leads 100 to 80. Hatchet misses nothing; Make misses clear canonical domain, clear product positioning.

Understand. Make leads 38 to 31. Hatchet misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Make misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Hatchet leads 75 to 65. Hatchet misses agent-compatible signup flow, programmatic credential creation, cli available; Make misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, cli available.

Operate. Make leads 65 to 59. Hatchet misses structured, predictable output, machine-readable errors, retry behavior documented, rate-limit behavior predictable; Make misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.

Pricing

Hatchet starts at $0/mo and has a free tier. Make does not publish one and has a free tier.

Signal by signal

Which to pick

Hatchet clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Hatchet and Make. Alternatives to each: Hatchet, Make.

An agent can fetch this as data: POST /v1/compare {"slugs": ["hatchet", "make"]}