16 rules in 5 groups, worth 100 points in all. They were set before any product was scored and apply the same way to all 11.
Version 1, published 8 Oct 2026
In short
Each rule is a yes-or-no fact, a list (such as the systems with an app) or a number with published thresholds, read from the vendor's own pages.
A fact the vendor does not publish earns nothing. A feature in beta or preview does not count.
The list follows the points. A tie goes to the lower price on "cheapest paid plan", then to the name.
Desktop apps and web apps for sending and saving API requests that run on Windows or in a browser. Editor extensions, pure testing suites, API gateways, documentation platforms and Apple-only tools are left out. A line that says "on at least one plan" counts free and paid plans; prices are for one person or the smallest team the plan allows.
Systems 10 points
Rule
What it takes
Points
Other systems
An official desktop app for macOS or Linux, or an official web app that works in a browser. Each one earns 2 points.
6
Command-line runner
The vendor documents an official command-line tool that runs saved collections or requests, for example in a CI pipeline, on at least one plan.
4
Requests and protocols 33 points
Rule
What it takes
Points
Built-in protocols
The vendor's site or docs name it as a supported request type with its own request screen, generally available and not in beta, on at least one plan. Each one earns 3 points.
12
Imports OpenAPI
The vendor documents importing an OpenAPI (Swagger) file to create requests or a collection.
4
Scripts and tests
The vendor documents scripts that run before a request or after a response, with assertions on the result, on at least one plan.
8
Collection runner
The app can run a whole collection or folder of requests in order and show the results, on at least one plan.
3
Mock servers
The vendor documents creating a mock server from a collection or API definition, on at least one plan.
3
Publishes API docs
The vendor documents generating and publishing a documentation page from a collection or API definition, on at least one plan.
3
Your data 22 points
Rule
What it takes
Points
Works without an account
The vendor documents that you can send requests and keep collections on your own device, in the desktop app or the web app, without signing in to a vendor account.
8
Collections as plain files
Collections can be stored as readable files (such as YAML, JSON or Markdown) in a folder on your disk that you can commit to Git, on a free or entry paid plan.
8
Open-source apps
The source code of the apps is public under an open-source licence approved by the OSI. Source-available licences do not count.
6
Teams and trust 16 points
Rule
What it takes
Points
Shared team workspaces
A plan with cloud-hosted shared workspaces or collections, where several people edit the same collection. Sharing through your own Git repository does not count here.
7
SAML or OIDC single sign-on
The vendor lists single sign-on (SAML or OIDC) on a pricing or help page, on any plan.
4
SOC 2 Type II or ISO 27001
The vendor names a SOC 2 Type II report or an ISO/IEC 27001 certification for this product or the company running it.
5
Price 19 points
Rule
What it takes
Points
Free plan
A free plan or free edition (not a trial) that lets one person send requests and save collections and environments on a computer or in a browser. Free for personal use counts.
10
Cheapest paid plan
The cheapest paid plan for one person (or one seat of the smallest team plan) at its regular price, in US dollars a month, billed yearly. A price shown only per year is divided by 12; one-time lifetime licences, launch discounts and "free for personal use" do not count as the paid plan. A product that is entirely free counts as $0. $0 earns 9 points, $4 or less 8, $6 or less 6, $10 or less 4, $15 or less 2.