How Matrix Score Works
Matrix Score is a 0–100 quality rating computed from real HTTP requests to each API's live endpoint — not editorial write-ups or AI-generated text. Every score is something we actually measured, so you can compare APIs on evidence instead of marketing.
Why this is different from other directories
Most API directories list whatever a provider submits and, at best, sort by popularity. The descriptions are editorial — or increasingly, AI-generated — and nobody checks whether the endpoint even responds.
Matrix Score takes the opposite approach. For every API in the directory, an automated test suite sends real requests to the live endpoint and records what actually happens: whether it resolves, how fast it answers, whether the connection is encrypted, whether the response is valid JSON, and whether it behaves consistently. The number you see is a snapshot of measured behavior — reproducible and grounded in HTTP, not adjectives.
The 100-point model
Five components add up to a maximum of 100 points. Each measures a different dimension of what makes an API worth building on.
Reachability
30 ptsDoes the endpoint (and its documentation) actually resolve and respond?
We resolve the API's DNS, open a connection, and confirm the live endpoint returns an HTTP response. We also check that the documentation URL loads. An API that cannot be reached is worthless no matter how good its docs read, so reachability carries the most weight.
Speed
20 ptsHow fast does the endpoint respond when we call it?
We measure the actual round-trip response time of a request to the endpoint and score it on a curve: sub-500 ms responses score full marks, and the score tapers off as latency climbs into the multi-second range. The measured value in milliseconds is shown on each API's page.
Security
15 ptsIs the connection encrypted and the transport configured sanely?
We verify the endpoint is served over HTTPS with a valid TLS certificate, and inspect its CORS headers to see whether the API can be called safely from browser-based applications. APIs stuck on plain HTTP or with broken certificates lose these points.
Developer Experience
20 ptsHow easy is it to make a successful first call and understand the result?
We check whether the endpoint returns well-formed, parseable JSON, whether a basic request succeeds without excessive setup, and whether documentation is available to guide that first call. Clean, predictable responses make an API pleasant to build on.
Reliability
15 ptsIs the endpoint consistently available across our checks?
We look at whether the endpoint responds consistently and returns healthy status codes rather than intermittent errors or timeouts. An API that only answers some of the time is risky to depend on in production.
Grade bands
The 0–100 score maps to a letter grade for quick scanning. Higher is better.
| Grade | Score | What it means |
|---|---|---|
| A+ | 90 – 100 | Exceptional — fast, secure, reliable, well-documented. |
| A | 80 – 89 | Excellent — production-ready with minor rough edges. |
| B | 65 – 79 | Good — solid, dependable choice for most projects. |
| C | 50 – 64 | Fair — usable, but expect trade-offs on speed or DX. |
| D | 35 – 49 | Weak — noticeable reliability or security gaps. |
| F | 0 – 34 | Poor — significant problems; verify before relying on it. |
Score distribution
Across all 1,426 APIs we have tested, the average score is 63.6. Most APIs land in the B–A range, but a meaningful tail scores poorly — which is exactly the signal a directory should surface.
How we test
Real HTTP requests
An automated suite sends live HEAD
and GET requests to each
endpoint and its documentation, recording status codes, timing, TLS, CORS headers, and response bodies.
Batched with timeouts
Tests run in small batches with strict timeouts so a single hanging endpoint cannot skew the run. Slow or non-responsive endpoints are recorded as such rather than silently passed.
Re-tested periodically
Scores are refreshed by re-running the suite. Each API page shows a "tested on" date so you always know how recent its score is.
Dead endpoints flagged
Endpoints that no longer resolve are marked Unavailable (214 at last check) and excluded from search indexing so they never waste your time.
Disclaimer
Matrix Score reflects automated measurements of each endpoint at the time it was tested. Real-world results can differ based on your region, network, authentication, and the provider's own changes, and scores may go up or down as we re-test. Matrix Score is an independent metric — we are not affiliated with, endorsed by, or sponsored by any of the API providers listed. Always verify an API against your own requirements before depending on it in production.
Frequently Asked Questions
How is the Matrix Score calculated?
Every API is scored out of 100 points from real HTTP requests to its live endpoint — never from editorial or AI-written opinion. Points come from five measured components: Reachability (30), Speed (20), Security (15), Developer Experience (20), and Reliability (15). The final score maps to a letter grade from A+ to F.
How often is the Matrix Score updated?
Scores are recomputed by re-running the automated test suite periodically. Because they reflect a live measurement, each API page shows a "tested on" date so you can see exactly when its score was last verified.
What does a low Matrix Score mean?
A low score (grade D or F) means our automated checks found real problems at test time — such as a slow endpoint, missing HTTPS, invalid JSON, or intermittent availability. It is a signal to verify the API yourself before depending on it, not a claim that it can never be used.
Is the Matrix Score affiliated with the API providers?
No. Matrix Score is an independent, automated measurement produced by this directory. We are not affiliated with, endorsed by, or sponsored by any of the API providers we test, and scores reflect endpoint behavior observed at test time only.