Compare

Chatwoot vs Stream

Chatwoot scores higher on the AgentReady, 48/100 against 43/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

Chatwoot. The modern customer support tool for your business.

Stream. Stream provides APIs and SDKs for building in-app chat, activity feeds, video, audio, and moderation.

Where Chatwoot is ahead

Chatwoot passes search discoverable, and Stream does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: pricing understandable. Stream misses it.

And on adopt, self-service signup and free trial or free allowance. Stream misses those.

Where Stream is ahead

Stream passes authentication documented and limits / constraints documented, and Chatwoot 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 adopt: copyable quickstart. Chatwoot misses it.

What neither does

Both fail llms-full.txt / full agent docs, mcp discoverable, structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, no mandatory sales call, programmatic credential creation, fast time to first request, mcp integration available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. 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. Chatwoot leads 80 to 67. Chatwoot misses llms-full.txt / full agent docs, mcp discoverable; Stream misses search discoverable, llms-full.txt / full agent docs, mcp discoverable.

Understand. Stream leads 31 to 23. Chatwoot misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Stream misses structured api reference, openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented.

Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Chatwoot leads 55 to 40. Chatwoot misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, mcp integration available; Stream misses self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, mcp integration available.

Operate. Both sit at 35/100 here. Chatwoot misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Stream misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Chatwoot starts at $0/agent/month and has a free tier. Stream does not publish one.

Signal by signal

Which to pick

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

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