Contract Quality

25% of the composite 42 checks · 211 points contract_quality

Technical depth and richness of the API contract artifacts — OpenAPI, AsyncAPI, JSON Schema, JSON-LD.

28,886providers scored on it

9,794score above zero

15.4mean sub-score

0.0median sub-score

0at 100

How it is scored

42 checks worth 211 points, grouped by the artifact each one reads. A facet's sub-score is its awarded points normalized against the points that were actually applicable to that provider — a check needing an artifact the provider does not publish at all is N/A, and leaves both sides of the fraction.

apis.yml · apis_yml

Check	Rule	Points
The registered APIs are the provider's own to operateSettles WHO OPERATES the thing each contract describes before awarding contract credit, instead of counting documents. Skipped entirely for a provider whose apis.yml does not declare the axis, so it cannot depress anyone for catalog work we have not reached.	`apis[] declare x-operator; graded on whether the operated surfaces are the provider's own`	6

OpenAPI · openapi

Check	Rule	Points
Publishes a machine-readable contractAt least one machine-readable contract exists, in ANY format the ecosystem actually uses. The largest single award in the rubric, because nearly every downstream capability — SDK generation, mocking, linting, agent tool-calling — is unlocked by having a contract at all.CONTRACT-TYPE-AGNOSTIC IN 0.6, and renamed from `openapi_present` to say so. Through 0.5.1 this check read OpenAPI and AsyncAPI only, which meant entire FHIR-native, GraphQL-native and EDI-native markets were recorded as having no contract for a format the rubric simply declined to read. Epic served a 59-resource FHIR R4 CapabilityStatement — plus STU3, DSTU2 and a smart-configuration — and read `spec_presence: false`, `contract_quality: 22.6`. That was a measurement artifact, not a judgment about Epic.PROVENANCE-GRADED IN 0.6. An API-Evangelist-modeled spec credits at 0.25. A provider-served contract you can download should outrank one written on the provider's behalf, and until 0.6 they were indistinguishable.	`at least one OpenAPI, AsyncAPI, GraphQL SDL or FHIR CapabilityStatement`	20
OpenAPI 3.2The provider publishes OpenAPI 3.2. Scored from the version they published, not from the version our refinement produced: 275 of the 339 providers holding a 3.2 document in the catalog hold it only because refine-openapis upgraded theirs, and exactly three publish 3.2 themselves. Worth the same as 3.1 rather than more — shipping the newest version is good practice, not a different kind of contract.	`declared version >= 3.2, read from the provider's published document`	5
OpenAPI 3.1Published against 3.1, which aligns with modern JSON Schema and supports webhooks natively. Scored above 3.0 rather than instead of it.	`openapi version is 3.1.x`	5
OpenAPI 3.0Published against 3.0. Still widely tooled and a long way ahead of Swagger 2.0, but no longer where the specification is moving.	`openapi version is 3.0.x`	3
Complete info blockTitle, a description of real length, a version, and a contact. The metadata a consumer needs to identify and reach the API's owner.	`info has title, description (>= 50 chars), version, contact`	4
Real servers declaredThe spec points at a callable host. A localhost server fails — a contract you cannot call is documentation, not an interface.	`servers[] non-empty and not localhost`	3
Servers resolve to a real hostNEW IN 0.6. A specification can be genuinely provider-published, verbatim, and still be uncallable. Every CAMARA server declaration in the entire telecom stack is the template variable `{apiRoot}` and every openIdConnectUrl is a CAMARA placeholder pointing at example.com — across 19 standards and exposure repositories there was exactly one absolute base URL. Insurance produced the same defect from the other direction: Majesco declares api.majesco.example.com and ACORD api.insurer-internal.example.com. The rubric scored all of it as full contract quality.0.15.0 MAKES THE LABEL TRUE. Until then this check never resolved anything: a denylist of obvious placeholders, then "has a dot and an alphabetic TLD" — so any host an author invented that missed the denylist counted as callable. `oracle.api.com` was Oracle Hospitality's ENTIRE callable score (1 of 59) and returns no DNS answer. Resolving all 14,061 literal hosts the classifier graded `real` found 829 (5.9%) with no address and 12 cluster-internal, across 392 providers. No lexical rule could have found most of them: a host that was live when harvested and is dead today is indistinguishable from a working one by pattern matching, and that population only grows.Templated hosts are never resolved — `https://{region}.api.acme.com` is callable by a consumer who fills the variable in, and resolving the residue would ask a different question. Only an authoritative negative answer removes credit; timeouts stay unknown and keep it.Graded on the SHARE of a provider's specs that carry a resolvable host, so a provider with one placeholder spec among twenty is not treated like one whose entire surface is uncallable. Catalog-wide at 0.6: 10,950 of 87,612 specs are uncallable as published, and 834 providers hold no spec with a resolvable host at all.The distinction that took care to get right: a TEMPLATED host that still carries a real domain — `https://{region}.api.acme.com`, or Yardi's `https://{server}.yardi.com/{clientUrl}/webservices` — passes. A consumer with the variable filled in reaches a host that exists. Only a host that is nothing but substitution variables, or a known placeholder domain, fails. A naive "contains a brace" test would have failed a large share of perfectly callable multi-region specs, and a naive full-text grep for example.com over the catalog returned 4,320 false positives, because real specs mention example.com in their EXAMPLES. This check parses the `servers` block specifically.	`share of specs whose servers[].url carries a registrable domain that is not a placeholder host, a bare template variable, or a host an actual DNS resolve found to have no address`	5
Operations have summariesAt least 80% of operations carry a summary. Summaries are what render in reference docs and what an agent reads to pick the right operation.	`>= 80% of operations have summary`	6
Operations have descriptionsAt least 80% of operations carry a description. The difference between knowing an operation's name and knowing what it does.	`>= 80% of operations have description`	6
Operations are taggedAt least 80% of operations are tagged, which is what groups a reference into navigable sections instead of one flat list of endpoints.	`>= 80% of operations have tags`	4
Unique operationIdsEvery operation has a unique operationId. Required for clean SDK method names and stable agent tool names; duplicates silently break both.	`100% of operations have unique operationId`	4
Success responses definedEvery operation documents at least one success response, so a consumer knows the shape of what they get back.	`every operation defines >= one 2xx response`	5
Error responses documentedAt least half of operations document a 4xx response schema. The most commonly skipped part of a contract, and the part integrators need most when things go wrong.	`>= 50% of operations define a 4xx response schema`	4
Examples presentGRADED IN 0.6, previously a bit. As a boolean this check fired on a single token example anywhere in the document, which meant it ran near-universally across payments and healthcare and carried almost no information. It now grades on the SHARE of operations that actually carry a request or response example, so a provider who documents every operation outscores one who documented a single one. Examples are the cheapest way an agent learns a payload shape before it ever makes a call, and "the spec contains the string example:" was never evidence of that.	`share of operations carrying a request or response example`	4
Reusable componentsFive or more component schemas, actually referenced via $ref. Evidence the spec is modelled rather than copy-pasted per endpoint.	`components.schemas count >= 5 and used via $ref`	3
Security schemes definedThe spec declares how authentication works, so a consumer can authenticate from the contract without hunting through prose docs.	`components.securitySchemes non-empty`	4
Security applied to operationsDeclared schemes are actually bound to operations, globally or individually. A scheme defined but never applied tells a consumer nothing about what a given call requires.	`security applied globally or per-operation`	3
Declares no deprecated OAuth grantNEW IN 0.7. The implicit grant returns an access token in the browser redirect fragment; the password grant has the client handle the user's credentials directly. Both are recommended against by the OAuth 2.0 Security BCP (RFC 9700) and removed outright in OAuth 2.1. Measured across 14,195 published contracts, 775 still declare implicit and 72 declare password - 28.9% of every OAuth-using contract. Vacuously satisfied by a contract declaring no OAuth: this scores the PRESENCE of a deprecated flow, not the absence of OAuth.	`no securityScheme declares the implicit or resource-owner-password OAuth grant`	4
Keeps credentials out of the query stringNEW IN 0.7. An API key in the query string lands in server logs, proxy logs, browser history and referrer headers. 815 of 14,195 published contracts place the credential there. Vacuously satisfied where no apiKey scheme is declared.	`no apiKey securityScheme declares in: query`	3
Enumerates OAuth scopesNEW IN 0.7. Scope is how OAuth expresses least privilege - the difference between a token that can read a calendar and one that can delete an account. Only 15.3% of published contracts enumerate any scope, so roughly four in five OAuth-declaring contracts describe how to obtain a credential and never what it permits. This is the mechanism behind the missing least-privilege models found in every market report. Distinct from reg_oauth_scopes, which applies only where a regulatory regime does; this one applies to every provider. Vacuously satisfied without OAuth.	`every declared oauth2 flow enumerates at least one scope`	4
Webhooks or callbacksThe spec describes what the API sends back out, not only what it receives — the event surface most providers document only in prose, if at all.	`webhooks or callbacks defined (3.1) or callbacks (3.0)`	2
Inbound event contract publishedThe provider publishes a standalone machine-readable contract for the events it SENDS, not only for the calls it receives. LINE's is the clean example: a document defining the whole CallbackRequest schema tree, whose servers[] reads https://example.com because the consumer is the server. Until roadmap#175 that document was scored as an uncallable API and cost LINE a ninth of its callable share — a penalty for doing the thing this check now credits, while a provider who published nothing paid nothing.Distinct from webhooks_or_callbacks, which asks whether an OUTBOUND spec declares a webhooks/callbacks block. This asks whether the inbound surface has a contract of its own. LINE's has no webhooks: key at all — it is a paths-based envelope, which is why the older check never saw it. A provider doing both has done two things.N/A for a provider with no event surface. Asking a company with no webhooks whether it documented them would score 19,000 records down on a question that does not apply.	at least one OpenAPI document classified `inbound` in the provenance index	2

AsyncAPI · asyncapi

Check	Rule	Points
Publishes an AsyncAPI specAt least one AsyncAPI document exists, describing the messaging or streaming surface with the same rigor the OpenAPI applies to the request/response one.	`at least one api has spec_type == "AsyncAPI"`	12
AsyncAPI 3.xPublished against 3.x, which separates channels from operations and is where the specification's tooling is consolidating.	`asyncapi version is 3.x`	4
Channels definedThe spec declares the channels messages flow over — the event equivalent of declaring paths.	`channels[] non-empty`	4
Messages carry payload schemasAt least 80% of messages reference a payload schema, so a subscriber knows the shape of what arrives rather than discovering it at runtime.	`>= 80% of messages reference a payload schema`	5
Protocol bindings on serversServers declare their protocol bindings — Kafka, AMQP, WebSocket, MQTT — which is what makes the contract actually connectable.	`servers define protocol bindings`	3
Server security schemesAt least one server declares how to authenticate against it.	`securitySchemes defined for at least one server`	3

GraphQL · graphql

Check	Rule	Points
Publishes a GraphQL schemaA schema definition file is published rather than only an interactive playground. An endpoint with introspection disabled and no published SDL is, to a consumer building against it, an undocumented API.	`a .graphql / .gql SDL is published`	10
Schema defines a real type systemTwenty or more type definitions — a modelled domain rather than a handful of wrapper types around a REST passthrough.	`SDL declares >= 20 type definitions`	5
Schema is documentedHalf or more of the declared types carry description strings. In GraphQL the docstring IS the reference documentation — it is what renders in every explorer and what an agent reads to pick a field.	`>= 50% of type definitions carry a description string`	4

FHIR · fhir

Check	Rule	Points
Publishes a FHIR CapabilityStatementThe server publishes its conformance statement. This is the FHIR equivalent of shipping an OpenAPI, and it is served at a well-known path by every conformant server, which makes its absence a deliberate omission rather than an oversight.	`a CapabilityStatement / Conformance resource is published`	12
Broad resource coverageTwenty or more resources declared — the difference between a server that supports Patient and Observation and one that supports a working clinical record.	`CapabilityStatement declares >= 20 resources`	6

JSON Schema · json_schema

Check	Rule	Points
Publishes JSON SchemaAt least one JSON Schema is published as its own artifact, so the data model can be validated against and reused independently of any single API.	`at least one api property has type == "JSONSchema"`	6
Schema per resourceTwo or more schemas, broken out per primary resource rather than one catch-all document — evidence the data model is decomposed.	`schemas extracted per primary resource (>= 2)`	4

JSON-LD · json_ld

Check	Rule	Points
Publishes a JSON-LD contextAt least one JSON-LD context is defined, binding the API's terms to shared semantics instead of leaving field names to be guessed from spelling.	`at least one jsonld context defined`	5
Context defines classesFive or more classes in a context — a modelled domain rather than a token gesture at semantics.	`any jsonld context has class_count >= 5`	3
Context defines propertiesTen or more properties, giving the classes enough detail to be useful to a consumer mapping the API onto their own model.	`any jsonld context has property_count >= 10`	3

Spectral Rules · spectral

Check	Rule	Points
Documented resource lifecycleOf the resources a provider lets you CREATE, the share that also document how to read the thing back, change it, and remove it. Grouped by RESOURCE, not by path -- REST splits one resource across `POST /things` and `GET\|PUT\|DELETE /things/{id}`, and a path-level view would score that as two incomplete resources. WHY IT IS A CONTRACT SIGNAL. An agent that creates something and cannot read it back has no way to confirm the write landed, no way to correct it, and no way to clean up after itself. That is a property of the contract, visible in the contract, and orthogonal to everything else this facet measures -- a provider can document one endpoint impeccably, score full marks on tagging, schemas and examples, and tell an agent nothing about what happens next. REWARD-ONLY AND CAPPED. Absence of a documented DELETE is not absence of DELETE: a resource can be genuinely append-only (an event, a log line, an audit record), the capability can exist and be undocumented, or the resource can be managed elsewhere. Only the middle case is a provider deficiency and none of the three is distinguishable by reading the spec, so incompleteness is never penalised. The 0.33 cap means a provider clears this on a healthy third rather than needing 100%, and it stops the check rewarding CRUD-for-its-own-sake -- an API that deliberately exposes no DELETE must not score below a worse one that ships a dangerous one. MEASURED 2026-08-18 over 5,884 providers with a creatable resource: 96,704 creatable resources, 15.5% fully round-trippable, mean provider share 15.6%, MEDIAN 0.0%, and 59.1% documenting not one. This check reads near-zero across the catalog on day one, which IS the finding, and the band re-cut is part of the change rather than a follow-up. TWO CONVENTION BUGS WERE FOUND AND FIXED BEFORE THIS SHIPPED, both by spot-checking providers whose answer could be reasoned about independently rather than by trusting the aggregate. (1) Requiring PUT or PATCH for the update leg scored STRIPE 0.000 on 189 creatable resources -- Stripe uses POST on the instance path and does not use PUT or PATCH anywhere. (2) Not stripping file extensions scored SHOPIFY 0.000 on 166 -- `/customers.json` and `/customers/{id}.json` folded to two different resources. Corrected: Stripe 0.583, Shopify 1.000. KNOWN CAVEAT, recorded rather than hidden: an RPC-style API inflates the denominator. Slack publishes 636 paths and NOT ONE parameter segment (`/calls.add`, `/calls.end`) -- it is not resource-oriented, so 121 of its POST endpoints are counted as creatable resources that can never round-trip. Because this check is reward-only, no such provider is penalised; the effect is that the catalog-wide percentages above UNDERSTATE round-trip coverage among genuinely RESTful APIs. Quote them with that caveat.	`share of creatable resources that also document read, update and delete, capped at 0.33`	5
Implements a domain standardThe contract itself declares conformance to an interoperability standard for its market -- a SCIM schema URN, an OData metadata surface, an OpenRTB bid endpoint, a Sparkplug topic namespace, an ActivityPub actor. A customer who already speaks the standard can integrate with no bespoke connector; one who does not needs a bilateral one, and until 0.12 both scored identically. REWARD-ONLY, and that is deliberate. Absence earns nothing and costs nothing, because most markets in this catalog have no domain standard to implement and penalising their providers would measure the market rather than the provider. EVIDENCE, NOT CLAIM -- inherited from reg_mandate_verified, whose own finding was that a claimed-but-unverifiable mandate scored BELOW organizations under no obligation at all. Naming SCIM in marketing copy earns nothing here; declaring `urn:ietf:params:scim:schemas:...` in the contract earns. Measured 2026-08-17: 164 of 7,579 providers with a contract (2.2%) -- OData 89, SCIM 60, ActivityPub 10, OpenRTB 4, Sparkplug 2. Web of Things, oneM2M and HR Open have ZERO detectable adoption. That thinness is why this is a check and not the conditional facet originally proposed.	`contract carries a recognised domain-standard signature`	4

Developer Ergonomics · ergonomics

Check	Rule	Points
Published example corpusA published corpus of worked examples, separate from the contract. DISTINCT FROM `examples_present`, which reads examples INSIDE the OpenAPI document: a provider can reasonably have either or both, and 595 providers declare this pointer while it was read by no check at all. Found by Ahmet Soormally at WunderGraph, who wired nine pointers to his own record unprompted and got nothing for two of them — with nothing in the build that would ever have told him, or us. The catalog already treats examples as first-class: there is an `examples/` artifact class and an api-search/examples site. The rubric was the only part that could not see them.	`common[].type includes "Examples" (alias-aware: CodeExamples, Samples, CodeSamples, Demos)`	4

How the catalog distributes on it

Every one of the 28,886 providers this facet is scored on, bucketed by sub-score.

90-1000 · 0.0%

75-89.925 · 0.1%

50-74.94,500 · 15.6%

25-49.93,847 · 13.3%

0.1-24.91,422 · 4.9%

019,092 · 66.1%

Top providers

The top 500 of 9,794 providers scoring above zero on this facet, ranked by facet sub-score, ties broken by composite.

1 New Relic80.6 72.3exemplar 2 Microsoft Outlook79.8 66.0strong 3 Payrix79.8 61.2strong 4 Asana79.3 70.2exemplar 5 UiPath78.8 66.3strong 6 AWS Lambda78.2 69.8exemplar 7 Scalar77.7 71.7exemplar 8 Novu77.6 71.6exemplar 9 Airtable77.6 63.0strong 10 Upvest77.6 51.5developing 11 Phare77.2 62.0strong 12 Amazon API Gateway77.1 70.6exemplar 13 Veeva77.0 72.8exemplar 14 Canva77.0 70.9exemplar 15 Fireflies.ai76.7 72.6exemplar 16 Telnyx76.6 79.6exemplar 17 ZoomInfo76.4 87.8exemplar 18 Palo Alto Networks76.0 76.9exemplar 19 Thanx75.8 75.9exemplar 20 GitHub75.6 80.3exemplar 21 Seismic75.6 66.4strong 22 Wappalyzer75.4 68.1exemplar 23 Tray.ai75.3 89.3exemplar 24 Okta75.3 75.3exemplar 25 OpsGenie75.1 48.1developing 26 Tripleseat74.9 50.3developing 27 Notion74.7 62.9strong 28 Lichess74.7 57.0strong 29 Didomi74.5 81.5exemplar 30 Ironfang74.5 78.2exemplar 31 Bitbucket74.5 70.6exemplar 32 Adobe Captivate74.5 48.5developing 33 Workday Payroll74.5 43.7developing 34 WooCommerce74.4 49.2developing 35 Confluent74.3 86.8exemplar 36 Snyk74.3 80.6exemplar 37 Amazon FreeRTOS74.1 67.3exemplar 38 Letta74.1 53.0developing 39 Render73.9 51.0developing 40 Yelp73.9 47.9developing 41 Anysphere Cursor Ai73.8 75.1exemplar 42 Anysphere Cursor.com73.8 75.0exemplar 43 Shodan73.7 65.0strong 44 Amazon EventBridge73.7 60.7strong 45 Honeycomb73.6 66.5exemplar 46 Absentify73.6 50.5developing 47 Shopify Admin API73.4 37.8thin 48 Postman73.3 79.6exemplar 49 Atlassian73.3 75.1exemplar 50 UserGems73.3 70.1exemplar 51 Mailmodo73.3 64.4strong 52 Amazon Pinpoint73.2 79.4exemplar 53 Amplitude73.2 57.8strong 54 Dun & Bradstreet73.1 66.4strong 55 Moov73.0 65.6strong 56 Salesforce72.8 91.0exemplar 57 Regal72.8 71.6exemplar 58 MX Technologies72.8 71.0exemplar 59 Elastic.io72.8 43.1developing 60 CData72.6 84.4exemplar 61 Snowflake72.6 82.7exemplar 62 Deel72.5 64.2strong 63 Bandwidth72.4 62.7strong 64 Intuit72.4 59.2strong 65 Beyond Identity72.4 56.7strong 66 APIs.io72.3 90.6exemplar 67 Tabby72.3 77.1exemplar 68 DataForSEO72.3 67.2exemplar 69 HighLevel72.3 66.4strong 70 Infobip72.1 82.4exemplar 71 Telesign72.1 69.1exemplar 72 Tyk72.1 64.0strong 73 ExchangeRate-API72.1 54.4strong 74 BodySpec72.1 47.6developing 75 JobsPipe72.0 73.9exemplar 76 OpenAI71.9 84.8exemplar 77 cloro71.9 79.4exemplar 78 Limble CMMS71.9 75.4exemplar 79 Pandium71.9 64.7strong 80 Arcade.dev71.8 57.1strong 81 Sideko71.8 41.9developing 82 Orion Health71.7 40.0developing 83 Azure DevOps71.5 76.7exemplar 84 Zapier71.5 68.9exemplar 85 Amazon Entity Resolution71.5 60.9strong 86 Shippo71.5 50.1developing 87 Amazon Lex71.4 78.1exemplar 88 AB Tasty71.4 48.9developing 89 Ankr71.3 62.3strong 90 Apple71.3 55.4strong 91 Amazon B2B Data Interchange71.3 44.9developing 92 Nylas71.2 86.7exemplar 93 Commune71.2 69.7exemplar 94 Asapp371.2 58.8strong 95 ShipStation71.2 57.7strong 96 Formfeed71.1 75.1exemplar 97 Microsoft71.1 69.2exemplar 98 Huddlekit71.1 53.5developing 99 WhatsApp71.0 52.0developing 100 Amazon Audit Manager71.0 30.5thin 101 Appwrite70.8 83.6exemplar 102 OpenMercantil70.8 80.6exemplar 103 Twilio70.8 77.8exemplar 104 Vaquill AI70.8 77.5exemplar 105 Amazon EC2 Image Builder70.8 60.3strong 106 Lemmy70.8 41.8developing 107 Shopify70.7 84.4exemplar 108 Adobe Launch70.7 74.8exemplar 109 Delinea70.7 73.9exemplar 110 fal70.7 68.6exemplar 111 Figma70.7 61.0strong 112 Olo70.7 61.0strong 113 Adobe Photoshop70.7 52.6developing 114 Sanity70.7 50.8developing 115 Amazon AppSync70.7 30.3thin 116 Harness70.6 90.7exemplar 117 Massive (formerly Polygon.io)70.6 75.8exemplar 118 Workato70.6 67.2exemplar 119 Microsoft Office 36570.6 61.9strong 120 Axuall70.6 57.9strong 121 MediaRuntime70.6 49.6developing 122 Automation Anywhere70.5 76.1exemplar 123 Contentstack70.5 75.1exemplar 124 Microsoft Active Directory70.5 62.0strong 125 Adobe Premiere Pro70.5 60.2strong 126 AhaSend70.4 84.3exemplar 127 Losant70.4 83.1exemplar 128 Microsoft Azure70.4 76.2exemplar 129 Sendcloud70.4 68.0exemplar 130 Onfleet70.4 60.7strong 131 Amazon Firewall Manager70.4 57.6strong 132 BB&T Corp (Truist)70.4 55.0strong 133 Anthropic70.3 81.5exemplar 134 LinkedIn70.3 76.3exemplar 135 Arcmira70.3 62.6strong 136 Amazon Forecast70.3 56.2strong 137 Backpack70.3 52.2developing 138 Airbnb70.3 45.9developing 139 GitHub Actions70.2 82.8exemplar 140 Sentry70.2 80.5exemplar 141 Canvas Medical70.2 62.5strong 142 Monocrawl70.2 57.2strong 143 Sorsa70.2 53.7developing 144 Edit Square70.2 49.6developing 145 Cyclr70.2 49.4developing 146 Amazon SES70.1 80.5exemplar 147 Docusign70.1 70.3exemplar 148 Solcast70.1 52.8developing 149 D-ID70.1 49.7developing 150 Google Docs70.0 58.0strong 151 Pipeliner CRM70.0 57.8strong 152 Pipedream70.0 54.2developing 153 YouSign70.0 53.4developing 154 akta.pro69.9 73.5exemplar 155 Simon Data69.9 66.3strong 156 Dub69.9 59.6strong 157 Kubernetes69.9 49.7developing 158 Folk69.9 45.9developing 159 Swetrix69.8 77.0exemplar 160 E2B69.8 65.3strong 161 Bringg69.8 55.5strong 162 SAP HANA69.8 45.3developing 163 Fastly69.7 65.2strong 164 Treblle69.7 63.2strong 165 Argyle9a2569.7 52.4developing 166 Informatica69.7 50.2developing 167 Sitecore69.7 33.8thin 168 GitLab69.6 80.8exemplar 169 Amazon DynamoDB69.6 80.3exemplar 170 Stannp69.5 76.1exemplar 171 CircleCI69.5 67.6exemplar 172 Retool69.5 54.7strong 173 Clerk69.4 71.4exemplar 174 Autodesk69.4 60.4strong 175 AWS App Runner69.4 56.0strong 176 Amazon Fraud Detector69.4 56.0strong 177 Medplum69.3 79.1exemplar 178 OutSystems69.3 75.8exemplar 179 Bloomreach69.3 72.8exemplar 180 athenahealth69.3 69.6exemplar 181 Nutanix69.3 67.4exemplar 182 Snov.io69.3 67.2exemplar 183 Freestyle69.3 58.7strong 184 Conductor69.3 41.9developing 185 DreamFactory69.3 41.3developing 186 Wayfair69.3 38.3thin 187 Plaid69.2 86.1exemplar 188 Amazon CodeGuru Profiler69.2 73.6exemplar 189 Firma.dev69.2 60.5strong 190 Contrast Security69.2 58.5strong 191 Workday69.2 57.5strong 192 Quandoo69.2 50.7developing 193 Phonely69.2 45.5developing 194 Doordash69.1 77.2exemplar 195 Amazon X-Ray69.1 61.1strong 196 Trigger.dev69.1 53.7developing 197 Torii69.1 49.9developing 198 CryptoCompare69.1 49.8developing 199 LaunchDarkly69.0 80.8exemplar 200 LogicMonitor69.0 74.6exemplar 201 OpenWeatherMap69.0 62.4strong 202 Amazon Direct Connect69.0 60.0strong 203 Amazon Glue DataBrew69.0 58.9strong 204 Ironclad69.0 55.8strong 205 Amazon Device Farm69.0 54.3strong 206 Amazon DevOps Guru69.0 53.9developing 207 Spoonacular69.0 52.9developing 208 API Snap69.0 46.3developing 209 Culture Amp69.0 45.3developing 210 OpenUV69.0 45.2developing 211 Shutterstock69.0 43.0developing 212 Cloudflare68.9 80.6exemplar 213 Hunter68.9 71.9exemplar 214 Adobe Experience Cloud68.9 68.7exemplar 215 Tableau68.9 51.4developing 216 Siemens Insights Hub (MindSphere)68.9 42.0developing 217 Mubert68.9 40.2developing 218 APIGen68.9 35.6thin 219 Convoy68.8 68.4exemplar 220 Cumulocity68.8 67.5exemplar 221 npm68.8 49.8developing 222 Knative68.8 48.4developing 223 MongoDB68.7 78.4exemplar 224 Knock68.7 68.6exemplar 225 Sinch68.7 68.3exemplar 226 Common Room68.7 67.2exemplar 227 Adyen68.7 66.1strong 228 Microsoft Planner68.7 59.4strong 229 Arcadiapower268.7 51.3developing 230 Autodesk Construction Cloud68.7 50.6developing 231 Affirm68.7 34.6thin 232 Omnisend68.6 72.9exemplar 233 SMTP2GO68.6 69.0exemplar 234 123FormBuilder68.6 59.4strong 235 Axway68.6 56.1strong 236 Amazon CodeArtifact68.6 55.6strong 237 Signal68.6 41.6developing 238 Jira68.5 76.3exemplar 239 JPMorgan Chase68.5 52.3developing 240 Google Maps Platform68.5 51.4developing 241 S&P Global68.4 66.9exemplar 242 GitBook68.4 61.4strong 243 AccuraCite68.4 59.6strong 244 Bancomat68.4 57.0strong 245 Yapily68.4 50.4developing 246 Salesforce Marketing Cloud68.3 77.3exemplar 247 Synup68.3 63.2strong 248 Cognition Labs68.3 60.6strong 249 Choreo68.3 50.3developing 250 IFS68.3 49.4developing 251 Twenty68.3 46.4developing 252 Kinde68.2 88.0exemplar 253 Adobe Campaign68.2 72.0exemplar 254 Boomi68.2 67.6exemplar 255 TaxJar68.2 50.6developing 256 Appmixer68.2 50.5developing 257 Wallarm68.2 40.1developing 258 Canvas LMS68.1 67.5exemplar 259 Amazon Cognito68.1 67.0exemplar 260 Mlsgrid68.1 62.4strong 261 Amazon EventBridge Pipes68.1 61.7strong 262 Amazon EventBridge Scheduler68.1 61.7strong 263 AppOmni68.1 59.0strong 264 Zitadel68.1 50.5developing 265 PandaDoc68.1 42.7developing 266 Port Community Systems68.1 36.1thin 267 Vonage68.0 62.2strong 268 Hookdeck68.0 60.8strong 269 FIS Global68.0 58.1strong 270 Zoom68.0 56.3strong 271 Apidog68.0 54.0developing 272 Adobe67.9 80.9exemplar 273 Red Hat67.9 70.6exemplar 274 Chronosphere67.9 62.4strong 275 Microsoft Copilot67.9 52.8developing 276 TagoIO67.9 49.0developing 277 CockroachDB67.9 44.4developing 278 Amazon EC267.8 63.7strong 279 SailPoint67.8 56.1strong 280 Google Gemini67.8 50.7developing 281 Ramp67.8 47.7developing 282 Google Places67.8 44.9developing 283 Basecamp67.8 43.3developing 284 Transifex67.8 40.6developing 285 Varonis67.8 39.3developing 286 WellCare Health Plans67.8 36.2thin 287 The Things Network / The Things Stack67.7 79.2exemplar 288 Cockroach Labs67.7 72.0exemplar 289 Veracode67.7 58.8strong 290 Ribbon Health67.7 58.1strong 291 Amazon GuardDuty67.7 57.7strong 292 emnify67.7 55.6strong 293 Warp67.7 52.1developing 294 Routific67.7 51.1developing 295 Zluri67.7 47.9developing 296 Elation Health67.6 77.5exemplar 297 Statsig67.6 76.7exemplar 298 Meltwater67.6 73.2exemplar 299 Kong67.6 73.2exemplar 300 Tink67.6 62.3strong 301 Etsy67.6 58.7strong 302 Wahoo Fitness67.6 51.9developing 303 Microsoft Defender67.6 51.4developing 304 Parasail67.6 49.5developing 305 EBANX67.6 41.2developing 306 Amazon Athena67.6 36.4thin 307 Amazon Kendra67.5 61.6strong 308 Amazon CloudWatch67.5 59.1strong 309 Agrio67.5 37.8thin 310 Datadog67.4 79.1exemplar 311 Google67.4 70.1exemplar 312 VideoGen67.4 63.0strong 313 SAP67.4 55.4strong 314 RapidAPI67.4 41.7developing 315 Benchmark Email67.3 65.0strong 316 Runloop67.3 59.6strong 317 Exa67.3 59.0strong 318 Wufoo67.3 56.0strong 319 Adobe Creative Cloud67.3 53.4developing 320 KEDA67.3 46.9developing 321 Gumlet67.2 71.1exemplar 322 Apigee67.2 70.8exemplar 323 Fitbit67.2 60.1strong 324 Fortify67.2 58.9strong 325 Amazon SNS67.2 58.5strong 326 Mindee67.2 54.0developing 327 Oracle Database67.2 50.8developing 328 Reflektive67.2 46.2developing 329 Amazon Application Migration Service67.2 29.0thin 330 BigPanda67.1 71.8exemplar 331 Checkmarx67.1 58.5strong 332 Fixer67.1 53.5developing 333 Indexed67.1 44.7developing 334 Squarespace67.0 69.9exemplar 335 GitHub Copilot67.0 65.8strong 336 1NCE67.0 48.9developing 337 Indeed67.0 46.0developing 338 AT Protocol67.0 45.0developing 339 UtilityAPI67.0 40.0developing 340 Square66.9 75.9exemplar 341 SolarWinds66.9 62.5strong 342 Prismatic66.9 62.5strong 343 positionstack66.9 62.4strong 344 Splunk66.9 60.5strong 345 Youtube66.9 59.8strong 346 1Password66.9 59.6strong 347 Filevine66.9 57.4strong 348 Dataiku66.9 53.3developing 349 Checkiday - National Holiday and Event API66.9 52.1developing 350 Uber66.9 49.0developing 351 Amazon66.9 48.9developing 352 Figshare66.9 45.7developing 353 Bump.sh66.8 60.6strong 354 Oracle Enterprise Manager66.8 52.1developing 355 Android66.8 49.9developing 356 SAP Sales and Distribution (SD)66.8 48.4developing 357 Ariba66.8 45.6developing 358 Neuphonic66.8 43.9developing 359 TradeStation66.8 40.3developing 360 Xquik66.7 88.7exemplar 361 Ghost66.7 78.4exemplar 362 Listrak66.7 74.3exemplar 363 Remote66.7 73.7exemplar 364 Ploid66.7 68.9exemplar 365 Celigo66.7 58.1strong 366 Resend66.7 54.1developing 367 Amazon Managed Grafana66.7 53.9developing 368 Jentic66.7 53.9developing 369 Buildxact66.7 51.5developing 370 Crossplane66.7 47.2developing 371 Restaurant36566.7 44.9developing 372 Sendle66.7 44.6developing 373 Canonical66.6 76.3exemplar 374 OpenText Cybersecurity66.6 60.3strong 375 Amazon WorkSpaces Web66.6 56.8strong 376 Amazon Mainframe Modernization66.6 56.2strong 377 Aiven66.6 45.3developing 378 Kubernetes Services66.6 43.4developing 379 Verisk66.6 38.6thin 380 Trello66.5 74.8exemplar 381 Leonardo.AI66.5 56.9strong 382 Refinitiv Eikon66.5 49.8developing 383 Altruistiq66.5 44.4developing 384 Kajabi66.5 42.0developing 385 Tapfiliate66.4 69.8exemplar 386 Amazon RDS66.4 61.3strong 387 Mercedes-Benz Mercedes me66.4 51.9developing 388 Adobe Creative Suite66.4 51.7developing 389 Tensor66.4 49.0developing 390 CloudZero66.4 43.1developing 391 Sage66.4 42.0developing 392 MOLOCO66.3 64.0strong 393 Posit66.3 63.3strong 394 Amazon SQS66.3 58.7strong 395 OpenADR Alliance66.3 54.5strong 396 Avalara66.2 70.9exemplar 397 Juniper Networks66.2 59.7strong 398 Twilio Segment66.2 42.7developing 399 BuyWhere66.2 42.7developing 400 Ruby Programming Language and Popular API Gems66.2 40.8developing 401 Algolia66.1 82.8exemplar 402 Svix66.1 76.7exemplar 403 Amazon Polly66.1 61.0strong 404 Google Cloud Dataflow66.1 59.3strong 405 Albato66.1 49.3developing 406 WegoWise66.1 35.3thin 407 Zesty66.1 35.2thin 408 Brevo66.0 81.7exemplar 409 Hubble Network66.0 70.4exemplar 410 Appian66.0 69.0exemplar 411 Toast66.0 68.9exemplar 412 Buildkite66.0 68.0exemplar 413 Openhandle66.0 61.7strong 414 Clari66.0 60.4strong 415 SnapLogic66.0 59.6strong 416 Amazon Data Exchange66.0 55.1strong 417 Coupa66.0 54.0developing 418 AbuseIPDB66.0 51.5developing 419 CrewAI Cloud66.0 49.7developing 420 Sumo Logic66.0 49.6developing 421 Schematic66.0 46.1developing 422 Blockworks66.0 42.2developing 423 1Factory66.0 37.7thin 424 Fly Io66.0 35.8thin 425 Stedi65.9 78.8exemplar 426 OneTrust65.9 73.2exemplar 427 CloudBees65.9 72.8exemplar 428 KonbiniAPI65.9 65.1strong 429 Oracle E-Business Suite65.9 59.9strong 430 Tesla Energy65.9 55.8strong 431 PolyAPI65.9 47.4developing 432 Unsplash65.9 40.1developing 433 Amazon Aurora DSQL65.9 30.0thin 434 Stripe65.8 82.1exemplar 435 Koala65.8 64.9strong 436 Talend65.8 63.0strong 437 Amazon Amplify65.8 51.2developing 438 VNC65.8 47.1developing 439 JFrog65.7 71.6exemplar 440 Confluence65.7 70.6exemplar 441 Unified.to65.7 65.4strong 442 Giphy65.7 59.8strong 443 PosteAhora65.7 54.7strong 444 Felt65.7 49.8developing 445 Fyno65.7 48.3developing 446 Enable Banking65.7 48.2developing 447 GenLogs65.7 42.5developing 448 EvolutionaryScale65.7 41.1developing 449 Amazon Lightsail65.6 75.3exemplar 450 Salla65.6 68.3exemplar 451 CycleCalcs65.6 67.0exemplar 452 Raygun65.6 61.6strong 453 Amazon Config65.6 56.7strong 454 Amazon Health Dashboard65.6 55.1strong 455 Amazon Compute Optimizer65.6 54.3strong 456 Oracle WebLogic Server65.6 44.8developing 457 Finout65.6 39.2thin 458 SAP S/4HANA65.6 37.6thin 459 APIIDA65.6 32.9thin 460 Cvent Event Cloud65.5 72.4exemplar 461 Reachdesk65.5 58.2strong 462 Amazon CloudFormation65.5 58.2strong 463 Scanverity Resolution API65.5 57.2strong 464 Google Slides65.5 56.5strong 465 Amazon Data Lifecycle Manager65.5 54.8strong 466 Rivery65.5 53.0developing 467 Veritas NetBackup65.5 52.8developing 468 ATTOM65.5 49.0developing 469 Maersk65.5 48.7developing 470 Leap65.5 45.6developing 471 Unkey65.5 42.2developing 472 commercetools65.5 41.8developing 473 Freshdesk65.5 31.8thin 474 Amazon Aurora65.5 30.7thin 475 Amazon Augmented AI65.5 29.1thin 476 Cvent Registration65.4 77.4exemplar 477 Gainsight65.4 74.7exemplar 478 Amazon VPN65.4 74.6exemplar 479 beehiiv65.4 73.6exemplar 480 Lytics65.4 67.3exemplar 481 Amazon Ground Station65.4 58.7strong 482 Amazon MSK65.4 58.5strong 483 Cellulant65.4 51.2developing 484 Google Cloud Datastream65.4 49.3developing 485 Amazon MQ65.4 48.5developing 486 HonestHook65.4 45.0developing 487 Spring Framework65.4 44.4developing 488 Google Cloud Pub/Sub65.4 38.8thin 489 CloudEvents65.4 37.6thin 490 Elastic65.3 74.2exemplar 491 Google Cloud Storage65.3 65.0strong 492 FirstPromoter65.3 64.8strong 493 Gong65.3 64.7strong 494 Vessel65.3 64.0strong 495 Google Cloud Platform65.3 63.4strong 496 Reputation65.3 61.8strong 497 TVmaze65.3 57.6strong 498 Currencylayer65.3 56.4strong 499 FindLocal65.3 55.1strong 500 Avaya65.3 52.5developing

Move this number. Every provider in the catalog is profiled from a public repository at github.com/api-evangelist/<provider>, and each check above names the exact artifact it reads. Publish the artifact, open a pull request, and the next scoring run picks it up — no gatekeeping and no fee. The full rubric is at apis.io/rating/, and the Influence plan is the fast lane if you would rather work your own listing through the API — remediation, projections and re-check requests.

Scored on rubric v0.23.0 across 28,886 providers · lists rebuilt 2026-10-08 · capped at the top 500 per page.

Contract Quality

How it is scored

How the catalog distributes on it

Top providers

The other 8 facets