Gogs vs Unkey
Unkey scores higher on the AgentReady, 56/100 against 53/100. They differ on 10 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Gogs. A simple, stable and extensible self-hosted Git service that can be set up in the most painless way
Unkey. Unkey is a developer platform for modern APIs that unifies infrastructure, allowing developers to deploy APIs instantly, route traffic through global gateways, and understand usage in one place.
Where Gogs is ahead
Gogs passes llms-full.txt / full agent docs and mcp discoverable, and Unkey does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds adopt: mcp integration available. Unkey misses it.
And on operate, agent compatibility verified. Unkey misses it.
Where Unkey is ahead
Unkey passes public docs discoverable, and Gogs 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. Gogs misses those.
And on adopt, self-service signup, fast time to first request and official python sdk. Gogs misses those.
What neither does
Both fail openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, structured, predictable output, 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. Gogs leads 87 to 80. Gogs misses public docs discoverable; Unkey misses llms-full.txt / full agent docs, mcp discoverable.
Understand is whether an agent can read the docs and work out how the API behaves before calling it. Unkey leads 54 to 31. Gogs misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented; Unkey misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented.
Adopt. Unkey leads 55 to 40. Gogs misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, fast time to first request, official python sdk; Unkey misses no mandatory sales call, agent-compatible signup flow, programmatic credential creation, mcp integration available.
Operate. Gogs leads 53 to 35. Gogs misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Unkey misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Gogs does not publish a machine-readable starting price and has a free tier. Unkey starts at $5/mo and has a free tier.
| Gogs plans | Unkey plans |
|---|---|
| - | Starter $5/mo |
| - | Pro $25/mo |
| - | Business Custom |
Signal by signal
| Signal | Gogs | Unkey |
|---|---|---|
| AgentReady | 53 | 56 |
| Discovery | 87 | 80 |
| Understanding | 31 | 54 |
| Adoption | 40 | 55 |
| Operability | 53 | 35 |
| Public API | Yes | Yes |
| MCP server | Yes | No |
| OpenAPI spec | Unknown | Yes |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Unknown | Yes |
| Free tier | Yes | Yes |
Which to pick
Unkey clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Gogs and Unkey. Alternatives to each: Gogs, Unkey.
An agent can fetch this as data: POST /v1/compare {"slugs": ["gogs", "unkey"]}