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.

26,626providers scored on it

9,938score above zero

18.7mean 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 26,626 providers this facet is scored on, bucketed by sub-score.

90-1000 · 0.0%

75-89.9188 · 0.7%

50-74.96,006 · 22.6%

25-49.92,588 · 9.7%

0.1-24.91,156 · 4.3%

016,688 · 62.7%

Top providers

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

1 New Relic87.4 68.1exemplar 2 Microsoft Outlook86.2 63.3strong 3 UiPath85.4 66.1strong 4 Asana85.1 66.7exemplar 5 Upvest84.2 55.4strong 6 Palo Alto Networks83.7 70.4exemplar 7 OpsGenie83.7 48.3developing 8 Airtable83.5 62.0strong 9 Workato83.1 62.9strong 10 Amazon API Gateway82.8 68.9exemplar 11 Veeva82.6 75.6exemplar 12 ZoomInfo82.5 84.7exemplar 13 Thanx82.2 74.9exemplar 14 Fireflies.ai82.1 70.3exemplar 15 AWS Lambda82.0 68.2exemplar 16 Seismic81.9 63.9strong 17 Tray.ai81.5 86.8exemplar 18 Wappalyzer81.4 67.6exemplar 19 Workday Payroll81.4 43.7developing 20 Tripleseat81.2 50.9developing 21 Deel81.1 66.5exemplar 22 Notion81.0 60.8strong 23 Lichess80.9 55.9strong 24 Amazon FreeRTOS80.8 66.2strong 25 Amplitude80.7 56.4strong 26 Bitbucket80.6 67.8exemplar 27 Adobe Captivate80.5 54.4strong 28 Amazon EventBridge80.4 59.9strong 29 Absentify80.3 50.1developing 30 Letta80.2 54.4strong 31 Okta80.0 62.8strong 32 UserGems79.9 67.4exemplar 33 ShipStation79.9 58.7strong 34 Yelp79.9 48.3developing 35 Render79.8 50.4developing 36 Shodan79.5 67.2exemplar 37 Canva79.4 64.9strong 38 Mailmodo79.4 64.0strong 39 Dun & Bradstreet79.4 64.0strong 40 WooCommerce79.4 49.4developing 41 Moov79.3 67.8exemplar 42 Intuit79.2 62.7strong 43 Elastic.io79.2 44.8developing 44 OpenAI79.0 82.9exemplar 45 Beyond Identity79.0 58.9strong 46 Amazon Pinpoint78.9 82.4exemplar 47 Snowflake78.9 80.5exemplar 48 ExchangeRate-API78.9 57.0strong 49 Shopify Admin API78.8 39.4developing 50 Tabby78.7 80.6exemplar 51 LinkedIn78.6 73.8exemplar 52 Onfleet78.6 61.0strong 53 Doordash78.4 77.0exemplar 54 Regal78.4 76.7exemplar 55 Dynatrace78.3 84.4exemplar 56 DataForSEO78.3 65.5strong 57 Pandium78.3 63.7strong 58 Arcade.dev78.3 59.8strong 59 APIs.io78.2 88.8exemplar 60 Amazon Lex78.2 77.0exemplar 61 Fastly78.2 66.0strong 62 Amazon Entity Resolution78.2 60.4strong 63 Apple78.2 55.1strong 64 AB Tasty78.2 50.3developing 65 Sideko78.2 43.9developing 66 Siemens MindSphere78.2 43.1developing 67 OpenWeatherMap78.1 64.9strong 68 Ironclad78.1 57.0strong 69 Google Maps Platform78.1 51.1developing 70 MX Technologies77.9 75.6exemplar 71 Amazon B2B Data Interchange77.9 48.3developing 72 Airbnb77.9 43.6developing 73 Conductor77.8 44.9developing 74 Orion Health77.8 43.8developing 75 Salesforce77.7 87.5exemplar 76 Trello77.7 73.9exemplar 77 Shippo77.7 51.3developing 78 Amazon EC2 Image Builder77.6 58.9strong 79 Autodesk Construction Cloud77.6 50.2developing 80 Amazon Audit Manager77.6 31.9thin 81 Limble CMMS77.5 74.0exemplar 82 Novu77.5 71.1exemplar 83 Ankr77.5 62.8strong 84 Microsoft77.5 58.8strong 85 Figma77.5 57.9strong 86 Affirm77.5 37.3thin 87 Amazon Elastic Transcoder77.4 55.8strong 88 Azure DevOps77.3 74.4exemplar 89 Amazon AppSync77.3 31.8thin 90 emnify77.2 59.4strong 91 Microsoft Office 36577.2 59.3strong 92 WhatsApp77.2 51.4developing 93 Amazon Firewall Manager77.1 56.7strong 94 Oracle Database77.1 50.6developing 95 Sendcloud77.0 71.3exemplar 96 Amazon Forecast77.0 55.7strong 97 Lemmy77.0 46.5developing 98 Common Room76.9 65.0strong 99 Google Docs76.9 56.4strong 100 Sorsa76.9 56.3strong 101 Solcast76.9 55.7strong 102 athenahealth76.8 75.1exemplar 103 Knock76.8 71.6exemplar 104 Microsoft Active Directory76.8 59.8strong 105 Pipedream76.8 54.7strong 106 Google Gemini76.8 52.2developing 107 Adobe Photoshop76.8 52.1developing 108 PandaDoc76.8 42.9developing 109 Olo76.7 64.8strong 110 OpenMercantil76.6 88.2exemplar 111 Automation Anywhere76.6 72.9exemplar 112 fal76.6 69.7exemplar 113 AhaSend76.5 81.8exemplar 114 Sentry76.5 77.4exemplar 115 Cloudflare76.5 71.1exemplar 116 Datadog76.5 66.5exemplar 117 BB&T Corp (Truist)76.5 60.0strong 118 Cyclr76.5 51.9developing 119 Losant76.4 80.4exemplar 120 GitHub Actions76.4 80.2exemplar 121 Statsig76.4 76.9exemplar 122 D-ID76.4 52.0developing 123 Informatica76.4 43.7developing 124 Docusign76.3 68.9exemplar 125 Dub76.3 60.9strong 126 Amazon DynamoDB76.2 79.4exemplar 127 Microsoft Azure76.2 73.3exemplar 128 Adobe Premiere Pro76.2 58.3strong 129 Treblle76.2 55.8strong 130 YouSign76.2 53.8developing 131 Folk76.2 48.4developing 132 SAP HANA76.2 42.9developing 133 Adobe Launch76.1 72.0exemplar 134 Bringg76.1 59.6strong 135 Backpack76.1 54.9strong 136 Uber76.1 49.5developing 137 Contentstack76.0 73.6exemplar 138 E2B76.0 65.5strong 139 Fitbit76.0 65.4strong 140 Sanity76.0 50.6developing 141 Kajabi76.0 44.4developing 142 Amazon SES75.9 79.1exemplar 143 Amazon Fraud Detector75.9 55.5strong 144 Culture Amp75.9 46.6developing 145 Wayfair75.9 39.3developing 146 Midjourney75.9 33.1thin 147 Appwrite75.8 80.1exemplar 148 Stannp75.8 80.1exemplar 149 Simon Data75.8 64.0strong 150 Quandoo75.8 53.9developing 151 Kubernetes75.8 50.4developing 152 Basecamp75.7 43.5developing 153 Swetrix75.6 75.9exemplar 154 Clari75.6 59.1strong 155 Amazon X-Ray75.6 58.7strong 156 Shutterstock75.6 42.5developing 157 RapidAPI75.6 41.9developing 158 Freestyle75.5 60.4strong 159 Amazon Direct Connect75.5 58.5strong 160 Amazon Glue DataBrew75.5 58.4strong 161 Spoonacular75.5 55.5strong 162 Amazon DevOps Guru75.5 53.4developing 163 API Snap75.5 49.9developing 164 Torii75.5 49.8developing 165 OpenUV75.5 48.1developing 166 Shopify75.4 88.0exemplar 167 Canvas Medical75.4 67.8exemplar 168 DreamFactory75.4 41.8developing 169 GitLab75.3 72.0exemplar 170 Convoy75.3 69.0exemplar 171 Amazon Cognito75.3 66.0strong 172 Microsoft Planner75.3 57.8strong 173 Amazon CodeArtifact75.3 54.8strong 174 Trigger.dev75.3 54.8strong 175 Mubert75.3 42.9developing 176 APIGen75.3 37.3thin 177 Medplum75.2 86.4exemplar 178 Amazon CodeGuru Profiler75.2 73.0exemplar 179 Clerk75.2 70.9exemplar 180 Bandwidth75.2 53.7developing 181 ElevenLabs75.1 82.3exemplar 182 Adyen75.1 69.5exemplar 183 Sitecore75.1 35.4thin 184 Gainsight75.0 80.9exemplar 185 Bloomreach75.0 68.6exemplar 186 Yapily75.0 53.5developing 187 Knative75.0 49.9developing 188 Phonely75.0 48.4developing 189 Hunter74.9 69.8exemplar 190 123FormBuilder74.9 64.2strong 191 Autodesk74.9 57.4strong 192 JPMorgan Chase74.9 53.4developing 193 MuleSoft74.9 51.3developing 194 Amazon EventBridge Pipes74.8 60.9strong 195 Amazon EventBridge Scheduler74.8 60.9strong 196 Apidog74.8 52.5developing 197 Brevo74.7 87.3exemplar 198 GitHub74.7 77.2exemplar 199 AppOmni74.7 58.3strong 200 npm74.7 49.3developing 201 Choreo74.7 47.7developing 202 Transifex74.7 43.2developing 203 Signal74.7 41.3developing 204 GitBook74.7 36.9thin 205 Stripe74.6 87.9exemplar 206 HubSpot74.6 87.5exemplar 207 TaxJar74.6 52.4developing 208 Appmixer74.6 51.1developing 209 Wallarm74.6 42.0developing 210 Kinde74.5 86.1exemplar 211 Salesforce Marketing Cloud74.5 82.6exemplar 212 LaunchDarkly74.5 77.9exemplar 213 Token.io74.5 73.3exemplar 214 SMTP2GO74.5 71.7exemplar 215 Omnisend74.5 70.8exemplar 216 Mlsgrid74.4 63.1strong 217 Zoom74.4 54.0developing 218 CryptoCompare74.4 52.2developing 219 Microsoft Copilot74.4 51.4developing 220 Zitadel74.4 50.2developing 221 Toast74.3 67.7exemplar 222 Hookdeck74.3 61.5strong 223 SailPoint74.3 55.3strong 224 Routific74.3 53.9developing 225 Tableau74.3 50.8developing 226 Apigee74.2 65.8strong 227 ESRI ArcGIS74.2 65.8strong 228 Snov.io74.2 64.9strong 229 Amazon GuardDuty74.2 57.0strong 230 WellCare Health Plans74.2 36.5thin 231 Port Community Systems74.2 36.3thin 232 Adobe Experience Cloud74.1 66.0strong 233 Amazon EC274.1 62.8strong 234 ChatGPT74.1 59.7strong 235 Amazon CloudWatch74.1 58.4strong 236 Ramp74.1 52.3developing 237 Microsoft Defender74.1 48.5developing 238 Zluri74.1 46.9developing 239 Google Places74.1 44.4developing 240 Varonis74.1 40.2developing 241 Agrio74.1 39.9developing 242 Amazon Athena74.1 38.1thin 243 Adobe Campaign74.0 74.9exemplar 244 Amazon Kendra74.0 61.1strong 245 Splunk74.0 54.0developing 246 Mistral AI74.0 51.6developing 247 TagoIO74.0 51.1developing 248 Cohere74.0 35.4thin 249 Tink73.9 65.2strong 250 Ribbon Health73.9 61.5strong 251 Cumulocity73.8 64.4strong 252 GitHub Copilot73.8 64.1strong 253 IFS73.8 54.3strong 254 Parasail73.8 50.9developing 255 Reflektive73.8 48.7developing 256 Didomi73.7 77.3exemplar 257 Jira73.7 72.6exemplar 258 Synup73.7 62.1strong 259 FIS Global73.7 61.7strong 260 Twenty73.7 47.8developing 261 SAP Concur73.7 43.0developing 262 Amazon Application Migration Service73.7 29.5thin 263 Adobe73.6 79.4exemplar 264 Runloop73.6 61.0strong 265 Mindee73.6 56.6strong 266 TheFork73.6 51.9developing 267 CockroachDB73.6 44.3developing 268 Tidb73.5 74.8exemplar 269 positionstack73.5 64.2strong 270 Prismatic73.5 63.0strong 271 Exa73.5 59.2strong 272 Filevine73.5 57.5strong 273 Fixer73.5 54.8strong 274 Checkiday - National Holiday and Event API73.5 54.6strong 275 Jentic73.5 54.3strong 276 Unify73.5 52.0developing 277 Indeed73.5 46.7developing 278 UtilityAPI73.5 42.5developing 279 Customer.io73.4 89.3exemplar 280 Twilio73.4 77.8exemplar 281 Spotify73.4 48.3developing 282 1Password73.3 57.9strong 283 Android73.3 49.8developing 284 SAP Sales and Distribution (SD)73.3 46.2developing 285 Reuters73.3 42.7developing 286 FullStory73.3 38.0thin 287 The Things Network / The Things Stack73.2 78.3exemplar 288 Wahoo Fitness73.2 56.7strong 289 Coupa73.2 51.9developing 290 Figshare73.2 50.9developing 291 Honeycomb73.2 35.3thin 292 Square73.1 78.5exemplar 293 OneTrust73.1 70.7exemplar 294 Meltwater73.1 70.5exemplar 295 Verisk73.1 40.7developing 296 Warp73.0 54.0developing 297 Marqeta73.0 53.7developing 298 Oracle Enterprise Manager73.0 52.6developing 299 Adobe Creative Suite73.0 50.9developing 300 Restaurant36573.0 47.8developing 301 Easyship73.0 46.0developing 302 Wells Fargo73.0 45.2developing 303 EBANX73.0 44.1developing 304 Ghost72.9 75.6exemplar 305 Instacart72.9 70.5exemplar 306 Resend72.9 54.1developing 307 Crossplane72.9 43.1developing 308 Etsy72.8 63.1strong 309 Red Hat72.8 62.8strong 310 Zapier72.8 60.4strong 311 Amazon WorkSpaces Web72.8 55.8strong 312 Amazon Mainframe Modernization72.8 55.2strong 313 1NCE72.8 52.4developing 314 Amazon Managed Grafana72.8 51.9developing 315 Aiven72.8 44.3developing 316 CloudZero72.8 43.5developing 317 Benchmark Email72.7 62.9strong 318 Oracle E-Business Suite72.7 59.9strong 319 Zuplo72.7 59.4strong 320 Workday72.7 53.3developing 321 Adobe Creative Cloud72.7 52.8developing 322 Maersk72.7 47.8developing 323 AT Protocol72.7 47.5developing 324 BuyWhere72.7 45.5developing 325 Paystack72.6 70.9exemplar 326 IBM72.6 62.6strong 327 Amazon RDS72.6 60.3strong 328 Wufoo72.6 58.6strong 329 Leonardo.AI72.6 57.7strong 330 Altruistiq72.6 48.2developing 331 KEDA72.6 48.1developing 332 Deepgram72.6 47.6developing 333 Elation Health72.5 83.6exemplar 334 S&P Global72.5 66.3strong 335 Payrix72.5 58.4strong 336 Google Cloud Dataflow72.5 57.5strong 337 PagerDuty72.5 45.9developing 338 Kubernetes Services72.5 43.9developing 339 1Factory72.5 39.6developing 340 Zesty72.5 36.9thin 341 Xquik72.4 86.8exemplar 342 Canvas LMS72.4 73.9exemplar 343 BigPanda72.4 69.9exemplar 344 Atlassian72.4 65.6strong 345 Grafana72.4 65.3strong 346 AbuseIPDB72.4 54.4strong 347 Amazon Data Exchange72.4 54.2developing 348 Sendle72.4 46.3developing 349 Twilio Segment72.4 44.3developing 350 Ruby Programming Language and Popular API Gems72.4 43.1developing 351 WegoWise72.4 38.1thin 352 Messagebird72.3 92.1exemplar 353 Avalara72.3 69.1exemplar 354 Amazon Polly72.3 60.4strong 355 EvolutionaryScale72.3 44.4developing 356 TradeStation72.3 44.1developing 357 Listrak72.2 78.5exemplar 358 Arcade72.2 75.7exemplar 359 Postman72.2 72.4exemplar 360 Clickup72.2 70.3exemplar 361 Hubble Network72.2 68.5exemplar 362 PolyAPI72.2 49.1developing 363 Leapsome72.2 48.7developing 364 Schematic72.2 47.1developing 365 Kit72.1 84.1exemplar 366 KonbiniAPI72.1 71.0exemplar 367 MOLOCO72.1 62.7strong 368 Tesla Energy72.1 61.1strong 369 Amazon SQS72.1 57.4strong 370 BizAPI72.1 54.5strong 371 Google Slides72.1 54.5strong 372 Buildpacks Io72.1 53.7developing 373 Amazon Compute Optimizer72.1 53.2developing 374 Felt72.1 52.0developing 375 Fyno72.1 51.9developing 376 ATTOM72.1 51.8developing 377 Mercedes-Benz Mercedes me72.1 51.2developing 378 Enable Banking72.1 50.9developing 379 Amazon Amplify72.1 50.2developing 380 Albato72.1 49.7developing 381 Sumo Logic72.1 47.9developing 382 VNC72.1 46.7developing 383 Neuphonic72.1 46.6developing 384 Productiv72.1 39.7developing 385 SAP S/4HANA72.1 35.6thin 386 Amazon Aurora72.1 31.5thin 387 Amazon Aurora DSQL72.1 31.5thin 388 Amazon Augmented AI72.1 30.4thin 389 Tapfiliate72.0 67.8exemplar 390 Refersion72.0 61.1strong 391 Youtube72.0 56.4strong 392 Cloud Foundry72.0 56.2strong 393 Mixpanel72.0 55.0strong 394 Cellulant72.0 54.2developing 395 Buildxact72.0 52.5developing 396 Finout72.0 39.9developing 397 Unsplash72.0 39.3developing 398 APIIDA72.0 34.6thin 399 Squarespace71.9 73.9exemplar 400 Remote71.9 72.6exemplar 401 Giphy71.9 59.5strong 402 Amazon CloudFormation71.9 57.4strong 403 Sinch71.9 56.1strong 404 Unkey71.9 44.0developing 405 Sage71.9 41.7developing 406 Flagsmith71.8 77.9exemplar 407 Google Cloud Storage71.8 63.2strong 408 AWS CloudWatch71.8 56.7strong 409 Amazon Config71.8 55.2strong 410 Amazon Data Lifecycle Manager71.8 53.8developing 411 Argyle71.8 51.6developing 412 SignWell71.8 49.3developing 413 Leap71.8 48.6developing 414 Particle71.7 63.7strong 415 Walmart71.7 60.8strong 416 Bancomat71.7 60.7strong 417 Veritas NetBackup71.7 52.4developing 418 Volkswagen71.7 44.9developing 419 GenLogs71.7 44.7developing 420 Princess Beef Heavy Industries71.7 32.2thin 421 Stedi71.6 84.1exemplar 422 Anthropic71.6 74.4exemplar 423 Hightouch71.6 66.9exemplar 424 Reputation71.6 61.8strong 425 Google Cloud Platform71.6 59.4strong 426 Scanverity Resolution API71.6 57.0strong 427 Rigetti Computing71.6 55.5strong 428 Transit71.6 53.1developing 429 Amadeus71.6 51.5developing 430 Todoist71.6 49.9developing 431 Lattice71.6 47.6developing 432 Fly Io71.6 34.7thin 433 Svix71.5 80.4exemplar 434 Avaya71.5 50.4developing 435 Cvent Registration71.4 79.5exemplar 436 beehiiv71.4 71.2exemplar 437 Mindbody71.4 64.2strong 438 Unified.to71.4 63.8strong 439 Tibber71.4 60.9strong 440 OpenADR Alliance71.4 58.4strong 441 Biconomy71.4 58.2strong 442 Currencylayer71.4 57.6strong 443 Amazon MSK71.4 56.7strong 444 Amazon Ground Station71.4 56.7strong 445 Jobber71.4 56.5strong 446 Amazon App Runner71.4 55.9strong 447 Amazon Step Functions71.4 52.3developing 448 Refinitiv Eikon71.4 51.8developing 449 Tensor71.4 51.7developing 450 Amazon MQ71.4 47.5developing 451 TimezoneDB71.4 47.4developing 452 Spring Framework71.4 46.2developing 453 Meteomatics71.4 44.7developing 454 Spacelift71.4 44.2developing 455 Aviation Weather Center71.4 41.1developing 456 Koala71.3 64.3strong 457 Runway71.3 52.3developing 458 CrewAI Cloud71.3 51.1developing 459 University of Manchester71.3 50.4developing 460 Inkit71.3 48.4developing 461 Lyft71.3 48.2developing 462 Oracle WebLogic Server71.3 44.6developing 463 ACI.dev71.3 36.8thin 464 Freshdesk71.3 32.0thin 465 Ada71.2 83.1exemplar 466 Commerce Layer71.2 69.9exemplar 467 Cvent Event Cloud71.2 69.9exemplar 468 TVmaze71.2 58.5strong 469 Amazon Health Dashboard71.2 58.1strong 470 Conekta71.2 54.9strong 471 Salesforce Automation71.2 54.7strong 472 Claude71.2 53.8developing 473 Amazon71.2 52.3developing 474 Snyk Container71.2 51.8developing 475 AMC Entertainment Holdings71.2 47.9developing 476 Jito Labs71.2 46.0developing 477 chucknorris.io71.2 44.3developing 478 Trefle71.2 42.8developing 479 commercetools71.2 42.6developing 480 Tripetto71.2 42.6developing 481 Jetic71.2 39.3developing 482 Klaviyo71.1 79.1exemplar 483 Amazon VPN71.1 73.3exemplar 484 Confluence71.1 67.4exemplar 485 LALAL.AI71.1 64.0strong 486 Covalent71.1 63.1strong 487 Reachdesk71.1 56.2strong 488 Amazon CodeDeploy71.1 54.1developing 489 Replicate71.1 53.9developing 490 Amazon CodePipeline71.1 52.9developing 491 Google Cloud Datastream71.1 47.3developing 492 Uniswap71.1 46.0developing 493 Barogo71.1 38.0thin 494 Google Cloud Pub/Sub71.1 37.9thin 495 EPA — U.S. Environmental Protection Agency71.0 66.0strong 496 Gong71.0 62.9strong 497 Raygun71.0 61.9strong 498 Telstra71.0 55.1strong 499 Amazon CodeBuild71.0 52.9developing 500 Pinwheel71.0 49.6developing

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.22.0 across 26,626 providers · lists rebuilt 2026-09-21 · 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