Compare

GrowthBook vs June

GrowthBook scores higher on the AgentReady, 67/100 against 39/100. They differ on 16 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

GrowthBook. The warehouse-native platform used by modern product teams for experimentation, feature flags, and product analytics.

June. June was a product analytics tool for B2B SaaS companies, focused on helping companies build better products and prevent customer churn.

Where GrowthBook is ahead

GrowthBook passes search discoverable, llms.txt published, llms-full.txt / full agent docs and mcp discoverable, and June does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: structured api reference and authentication documented. June misses those.

And on adopt, self-service signup, fast time to first request, cli available and mcp integration available. June misses those.

Finally, on operate, structured, predictable output, observable execution and agent compatibility verified. June misses those.

Where June is ahead

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

It also holds adopt: no mandatory sales call and agent-compatible signup flow. GrowthBook misses those.

What neither does

Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, 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. GrowthBook leads 87 to 60. GrowthBook misses clear product positioning; June misses search discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable.

Understand. GrowthBook leads 46 to 23. GrowthBook misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; June misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. GrowthBook leads 70 to 50. GrowthBook misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation; June misses self-service signup, programmatic credential creation, fast time to first request, cli available, mcp integration available.

Operate is whether an agent can run against it in production and recover when a call fails. GrowthBook leads 65 to 24. GrowthBook misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; June misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.

Pricing

GrowthBook does not publish a machine-readable starting price and has a free tier. June does not publish one with no free tier.

Signal by signal

Which to pick

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

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