IT AI Index

Index › Vendors › ReadMe · September 2026 Edition

1 category · Named, not ranked

ReadMe

8Judge labels

1First choices

0Negative labels

6 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

3 labels, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. ReadMe was named 3 times in API management, where Kong Gateway led with 37%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small business13 of 47

under the label threshold

Mid-market13 of 55

under the label threshold

Enterprisenot named

No model named it for this buyer.

In api management · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named ReadMe for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
API management	Developer platform	2%	13 of 55	0%	3	under 10 labels · led by Kong Gateway at 37%

Movement

This is the first edition on this tier, so no move can be computed for ReadMe yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated ReadMe across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	First choice	Alternative	Labels
Claude Haiku 4.5	0	0	0
GPT-5.4 mini	0	0	0
Gemini 3.5 Flash	0	1	1
Perplexity Sonar	0	0	0
Grok 4.1 Fast	0	0	0
Mistral Small	0	0	0
DeepSeek V4 Flash	0	1	1
Llama 4 Maverick	0	0	0
Qwen 3.7 Flash	0	0	0
Kimi K2	0	0	0
GLM 4.7 FlashX	1	0	1
MiniMax M2.5	0	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase5 labels1

Comparative2 labelsNone

Budget-constrained0 labelsNone

Scale-constrained1 labelNone

Negative0 labelsNone

First choiceAlternativeMentionNegative8 labels in all, every segment counted; 1 of the 1 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Developer portal ... | ReadMe (or Mintlify)” GLM 4.7 FlashX · API management · paraphrase prompt · first choice

“ReadMe is exceptional for external B2B partners because it features "personalized docs"” Gemini 3.5 Flash · API management · paraphrase prompt · alternative

“ReadMe / Mintlify — great for interactive docs aimed at external developers” DeepSeek V4 Flash · API management · paraphrase prompt · alternative

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as ReadMe, over the 8 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and ReadMe was named but was not.

ProductSame answerTook the first choice insteadHead to head

Kong Gateway8 of 80Not in the top three

Amazon API Gateway6 of 80Not in the top three

Zuplo5 of 83Not in the top three

Stoplight5 of 80Not in the top three

Tyk5 of 80Not in the top three

Apigee4 of 80Not in the top three

Mintlify4 of 80Not in the top three

MuleSoft Anypoint Platform4 of 80Not in the top three

Postman3 of 83Not in the top three

SwaggerHub3 of 80Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named ReadMe. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 6 of the 8 answers that named ReadMe and are not a share of its labels.

Domains cited

digitalapi.ai5

zuplo.com5

integrate.io4

moesif.com4

dev.to3

g2.com3

konghq.com3

reddit.com3

swagger.io3

trakkr.ai3

Thirty-six of the thirty-six domain citations in answers naming ReadMe came from somebody else's page.

Pages cited

integrate.io/blog/api-management-tools4

moesif.com/blog/technical/api-development/Top-API-Managers4

digitalapi.ai/blogs/best-api-developer-portals3

digitalapi.ai/blogs/best-api-lifecycle-management-tools3

g2.com/categories/api-management/small-business3

swagger.io/blog/best-api-lifecycle-management-platforms3

trakkr.ai/ai-recommends/api-management/small-business3

b2bsaastools.com/blog/best-b2b-saas-developer-portal-tools2

Pages are listed as the models cited them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when ReadMe's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as ReadMe, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at readme.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.