Compare

June vs Statsig

Statsig scores higher on the AgentReady, 51/100 against 39/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

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

Statsig. Statsig is a unified platform for feature flags, A/B testing, and product analytics that helps teams ship, measure, and learn.

Where June is ahead

June passes no mandatory sales call, and Statsig does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

Where Statsig is ahead

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

It also holds adopt: self-service signup and fast time to first request. June misses those.

And on operate, observable execution. June misses it.

What neither does

Both fail mcp discoverable, structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, cli available, 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 is whether an agent can find the product at all without being told it exists. Statsig leads 87 to 60. June misses search discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable; Statsig misses mcp discoverable.

Understand. Both sit at 23/100 here. June misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Statsig misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

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

Operate. Statsig leads 35 to 24. June misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified; Statsig misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

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

Signal by signal

Which to pick

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

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