Compare

GitHub vs SourceHut

GitHub scores higher on the AgentReady, 55/100 against 29/100. They differ on 11 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

GitHub. GitHub is a platform where developers, agents, and code come together for collaboration.

SourceHut. the hacker's forge

Where GitHub is ahead

GitHub passes search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms.txt published, llms-full.txt / full agent docs and mcp discoverable, and SourceHut does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: agent-compatible signup flow and mcp integration available. SourceHut misses those.

And on operate, rate-limit behavior predictable. SourceHut misses it.

Where SourceHut is ahead

SourceHut passes authentication documented, and GitHub does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.

What neither does

Both fail machine-readable metadata, structured api reference, openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, machine-readable errors, retry behavior documented, idempotency support, 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. GitHub leads 93 to 20. GitHub misses machine-readable metadata; SourceHut misses search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable, machine-readable metadata.

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

Adopt. GitHub leads 52 to 25. GitHub misses self-service signup, no mandatory sales call, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart; SourceHut misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, mcp integration available.

Operate. GitHub leads 59 to 47. GitHub misses machine-readable errors, retry behavior documented, idempotency support, agent compatibility verified; SourceHut misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

GitHub does not publish a machine-readable starting price. SourceHut does not publish one.

Signal by signal

Which to pick

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

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