Contract Quality

25% of the composite 40 checks · 203 points contract_quality

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

27,504providers scored on it

9,783score above zero

17.7mean sub-score

0.0median sub-score

0at 100

How it is scored

40 checks worth 203 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.

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

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 27,504 providers this facet is scored on, bucketed by sub-score.

90-1000 · 0.0%

75-89.9185 · 0.7%

50-74.95,816 · 21.1%

25-49.92,574 · 9.4%

0.1-24.91,208 · 4.4%

017,721 · 64.4%

Top providers

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

1 New Relic88.6 69.7exemplar 2 Dynatrace88.2 77.4exemplar 3 Palo Alto Networks87.6 65.9strong 4 Microsoft Outlook87.4 64.0strong 5 UiPath86.6 61.7strong 6 Asana85.7 66.5exemplar 7 Upvest85.4 57.0strong 8 Shopify85.3 84.0exemplar 9 OpsGenie84.7 50.0developing 10 Airtable84.5 63.7strong 11 Novu84.3 72.1exemplar 12 Workato84.2 64.6strong 13 ZoomInfo83.6 82.3exemplar 14 HubSpot83.3 80.4exemplar 15 Thanx83.3 76.6exemplar 16 AWS Lambda83.2 61.9strong 17 Amazon API Gateway82.8 51.3developing 18 Wappalyzer82.5 68.6exemplar 19 Tripleseat82.3 52.6developing 20 Lichess82.0 57.6strong 21 Notion81.9 62.4strong 22 doordash81.9 51.7developing 23 Workday Payroll81.8 44.2developing 24 Amazon EventBridge81.5 61.6strong 25 Amplitude81.5 58.0strong 26 Adobe Captivate81.5 54.3strong 27 veeva81.2 75.5exemplar 28 UserGems81.0 69.1exemplar 29 Jira80.9 58.0strong 30 Letta80.9 47.9developing 31 Amazon FreeRTOS80.8 67.5exemplar 32 ShipStation80.8 49.2developing 33 Render80.8 48.0developing 34 Regal80.7 78.0exemplar 35 Fireflies.ai80.7 70.7exemplar 36 Shodan80.6 64.5strong 37 Dun & Bradstreet80.5 65.7strong 38 WooCommerce80.5 51.1developing 39 Moov80.4 56.5strong 40 Medplum80.3 87.3exemplar 41 Adobe Premiere Pro80.3 60.8strong 42 Absentify80.3 51.5developing 43 Elastic.io80.3 46.5developing 44 Intuit80.1 64.3strong 45 Yelp79.9 49.7developing 46 OpenAI79.8 76.8exemplar 47 Tabby79.7 81.6exemplar 48 LinkedIn79.7 70.5exemplar 49 Shopify Admin API79.7 40.3developing 50 Onfleet79.5 62.6strong 51 Amazon Pinpoint79.4 81.1exemplar 52 Bitbucket79.4 52.1developing 53 AhaSend79.3 76.5exemplar 54 Mailmodo79.3 62.5strong 55 Canva79.2 67.0exemplar 56 Fastly79.1 60.6strong 57 Anthropic79.0 74.0exemplar 58 Confluence79.0 63.8strong 59 Beyond Identity79.0 56.4strong 60 Appwrite78.9 53.1developing 61 Orion Health78.9 45.4developing 62 Shippo78.7 52.2developing 63 Conductor78.7 45.8developing 64 airbnb78.7 44.5developing 65 Didomi78.6 78.1exemplar 66 Autodesk Construction Cloud78.6 51.9developing 67 Azure DevOps78.5 62.1strong 68 Affirm78.5 38.3thin 69 Vapi78.3 72.5exemplar 70 Okta78.3 61.0strong 71 Arcade.dev78.3 56.2strong 72 WhatsApp78.3 52.3developing 73 ankr78.2 64.5strong 74 Amazon Entity Resolution78.2 60.7strong 75 Apple78.2 56.5strong 76 AB Tasty78.2 51.7developing 77 Sideko78.2 45.3developing 78 Siemens MindSphere78.2 41.0developing 79 OpenWeatherMap78.1 63.5strong 80 Google Maps Platform78.1 52.5developing 81 Oracle Database78.1 50.1developing 82 Figma77.9 59.3strong 83 Adobe Photoshop77.9 52.7developing 84 Amazon B2B Data Interchange77.9 49.0developing 85 athenahealth77.8 77.6exemplar 86 Microsoft Azure Active Directory77.8 57.4strong 87 OpenMercantil77.7 86.4exemplar 88 Ironclad77.7 58.4strong 89 Google Gemini77.7 53.2developing 90 PandaDoc77.7 44.6developing 91 Olo77.6 62.5strong 92 Amazon EC2 Image Builder77.6 60.3strong 93 Microsoft Active Directory77.6 55.0strong 94 Cyclr77.6 52.9developing 95 TagoIO77.6 52.4developing 96 Amazon Audit Manager77.6 32.6thin 97 fal77.5 68.2exemplar 98 Microsoft77.5 59.6strong 99 Bloomreach77.4 70.8exemplar 100 Amazon Elastic Transcoder77.4 57.2strong 101 Amazon EC2 Auto Scaling77.3 62.3strong 102 Amazon AppSync77.3 32.6thin 103 emnify77.2 60.8strong 104 Microsoft Office 36577.2 56.4strong 105 Backpack77.2 55.6strong 106 Youtube77.1 59.1strong 107 Amazon Firewall Manager77.1 58.1strong 108 Sendcloud77.0 65.9strong 109 Bringg77.0 59.0strong 110 Amazon Forecast77.0 57.2strong 111 contentstack77.0 38.1thin 112 Fitbit76.9 67.1exemplar 113 Simon Data76.9 65.0strong 114 Docusign76.9 61.8strong 115 Google Docs76.9 57.8strong 116 Solcast76.9 56.1strong 117 Sanity76.9 52.2developing 118 Kubernetes76.9 52.1developing 119 Xquik76.8 89.3exemplar 120 Stannp76.8 78.3exemplar 121 Pipedream76.8 56.1strong 122 midjourney76.8 34.1thin 123 Swetrix76.6 76.6exemplar 124 Amazon Kinesis76.5 59.8strong 125 Basecamp76.5 44.4developing 126 D-ID76.4 53.5developing 127 DreamFactory76.4 42.7developing 128 Dub76.3 56.2strong 129 Salesforce76.2 82.5exemplar 130 Adobe Launch76.2 72.4exemplar 131 Canvas Medical76.2 67.6exemplar 132 Amazon DynamoDB76.2 62.6strong 133 Treblle76.2 57.3strong 134 YouSign76.2 51.7developing 135 Folk76.2 49.1developing 136 SAP HANA76.2 47.7developing 137 Bandwidth76.1 55.3strong 138 Uber76.1 50.8developing 139 Hunter76.0 68.2exemplar 140 Adyen76.0 66.9exemplar 141 Amazon S376.0 66.0strong 142 Autodesk76.0 57.2strong 143 Knative76.0 51.5developing 144 sitecore76.0 36.3thin 145 Amazon Fraud Detector75.9 56.9strong 146 Phonely75.9 49.3developing 147 Culture Amp75.9 46.3developing 148 Wayfair75.9 40.0developing 149 Amazon X-Ray75.8 61.1strong 150 Quandoo75.8 55.3strong 151 npm75.8 55.2strong 152 Brevo75.7 84.4exemplar 153 Restaurant36575.7 49.2developing 154 Signal75.7 42.2developing 155 GitBook75.7 37.9thin 156 Commerce Layer75.6 72.5exemplar 157 Knock75.6 69.3exemplar 158 Inworld AI75.6 66.7exemplar 159 Toast75.6 60.9strong 160 Shutterstock75.6 43.3developing 161 SMTP2GO75.5 72.6exemplar 162 Amazon Glue DataBrew75.5 58.7strong 163 Spoonacular75.5 56.9strong 164 API Snap75.5 51.3developing 165 OpenUV75.5 48.8developing 166 Torii75.5 48.5developing 167 Salesforce Marketing Cloud75.4 78.4exemplar 168 DataForSEO75.3 64.5strong 169 Microsoft Planner75.3 58.5strong 170 Amazon CodeArtifact75.3 56.2strong 171 Trigger.dev75.3 52.4developing 172 CryptoCompare75.3 52.2developing 173 Mubert75.3 43.6developing 174 APIGen75.3 36.7thin 175 grubhub75.3 35.6thin 176 Vantage75.2 51.2developing 177 Port Community Systems75.2 37.2thin 178 elevenlabs75.2 33.6thin 179 Convoy75.1 65.8strong 180 Snov.io75.1 65.8strong 181 Atlassian75.1 57.7strong 182 Adobe Campaign75.0 72.6exemplar 183 Adobe Experience Cloud75.0 61.9strong 184 Yapily75.0 54.2developing 185 Ramp75.0 53.2developing 186 123FormBuilder74.9 65.6strong 187 Mistral AI74.9 53.9developing 188 MuleSoft74.9 52.7developing 189 cohere74.9 35.4thin 190 Tesla Energy74.8 62.8strong 191 Amazon EventBridge Pipes74.8 62.3strong 192 Amazon EventBridge Scheduler74.8 62.3strong 193 Freestyle74.8 61.7strong 194 Apidog74.8 54.0developing 195 Seismic74.8 49.1developing 196 Cumulocity74.7 63.2strong 197 GitHub74.7 60.7strong 198 Choreo74.7 49.1developing 199 linear74.7 41.8developing 200 trello74.7 37.0thin 201 Listrak74.6 74.7exemplar 202 Mindee74.6 58.3strong 203 TaxJar74.6 53.8developing 204 Appmixer74.6 52.5developing 205 CockroachDB74.6 44.9developing 206 Wallarm74.6 42.7developing 207 Common Room74.4 65.1strong 208 Filevine74.4 59.2strong 209 Zitadel74.4 56.5strong 210 Microsoft Copilot74.4 52.8developing 211 SailPoint74.3 56.0strong 212 Routific74.3 55.4strong 213 Hookdeck74.3 53.9developing 214 Tableau74.3 51.7developing 215 Lemmy74.3 44.4developing 216 Honeycomb74.2 82.3exemplar 217 Adobe74.2 78.2exemplar 218 Apigee74.2 65.7strong 219 Amazon GuardDuty74.2 58.4strong 220 Wells Fargo74.2 38.9thin 221 WellCare Health Plans74.2 36.5thin 222 honeycomb74.2 36.2thin 223 Stripe74.1 80.6exemplar 224 Amazon EC274.1 63.5strong 225 Sorsa74.1 57.1strong 226 Wahoo Fitness74.1 54.8strong 227 Snowflake74.1 54.4strong 228 Coupa74.1 52.9developing 229 Microsoft Defender74.1 49.2developing 230 Zluri74.1 48.3developing 231 Google Places74.1 45.1developing 232 Varonis74.1 41.6developing 233 agrio74.1 40.6developing 234 Amazon Athena74.1 38.8thin 235 FullStory74.1 36.6thin 236 Elation Health74.0 81.5exemplar 237 Losant74.0 81.2exemplar 238 Square74.0 71.3exemplar 239 Runloop74.0 62.5strong 240 Amazon Kendra74.0 62.5strong 241 Figshare74.0 52.5developing 242 Tink73.9 65.9strong 243 Ribbon Health73.9 62.2strong 244 EBANX73.9 45.0developing 245 GitHub Copilot73.8 65.5strong 246 Lakera73.8 56.7strong 247 Parasail73.8 51.6developing 248 Reflektive73.8 49.4developing 249 Customer.io73.7 84.0exemplar 250 instacart73.7 65.0strong 251 Zapier73.7 62.0strong 252 Tray.ai73.7 53.5developing 253 Twenty73.7 46.0developing 254 SAP Concur73.7 44.1developing 255 Amazon Application Migration Service73.7 30.2thin 256 Benchmark Email73.6 63.8strong 257 Etsy73.6 61.7strong 258 Leonardo.AI73.6 59.4strong 259 Kajabi73.6 44.5developing 260 Prismatic73.5 64.4strong 261 Wufoo73.5 60.3strong 262 Clari73.5 59.3strong 263 positionstack73.5 58.4strong 264 Exa73.5 56.8strong 265 Jentic73.5 55.8strong 266 Fixer73.5 55.5strong 267 Checkiday - National Holiday and Event API73.5 55.2strong 268 Adobe Creative Cloud73.5 53.0developing 269 Unify73.5 52.4developing 270 KEDA73.5 48.4developing 271 Indeed73.5 48.1developing 272 Kubernetes Services73.5 44.9developing 273 UtilityAPI73.5 43.2developing 274 statsig73.5 38.0thin 275 messagebird73.5 34.6thin 276 The Things Network / The Things Stack73.4 78.1exemplar 277 Polygon73.4 68.3exemplar 278 Amazon API Gateway73.4 65.8strong 279 Boomi73.4 61.5strong 280 Datadog73.4 58.5strong 281 Spotify73.4 49.8developing 282 Strava73.4 49.5developing 283 Deepgram73.4 49.2developing 284 Sendle73.4 47.9developing 285 Android73.3 51.6developing 286 SAP Sales and Distribution (SD)73.3 48.0developing 287 Twilio Segment73.3 45.3developing 288 Reuters73.3 43.4developing 289 PagerDuty73.3 38.7thin 290 Hubble Network73.2 69.5exemplar 291 PolyAPI73.2 50.8developing 292 Squarespace73.1 74.9exemplar 293 Amazon SQS73.1 59.0strong 294 Gitcoin73.1 54.1developing 295 TradeStation73.1 45.0developing 296 Verisk73.1 42.1developing 297 OneSignal73.0 74.8exemplar 298 Omnisend73.0 67.3exemplar 299 Cellulant73.0 55.9strong 300 Warp73.0 55.4strong 301 Oracle Enterprise Manager73.0 54.0developing 302 Adobe Creative Suite73.0 50.1developing 303 Easyship73.0 46.7developing 304 Postman72.9 67.2exemplar 305 Tapfiliate72.9 66.0strong 306 Amazon SNS72.9 63.5strong 307 Refersion72.9 62.0strong 308 Buildxact72.9 53.4developing 309 Crossplane72.9 50.1developing 310 Sage72.9 42.7developing 311 RapidAPI72.9 42.0developing 312 Meltwater72.8 71.2exemplar 313 Power BI72.8 70.8exemplar 314 Remote72.8 69.2exemplar 315 Hunter72.8 57.5strong 316 Amazon WorkSpaces Web72.8 57.2strong 317 Amazon Mainframe Modernization72.8 56.7strong 318 Amazon Lex72.8 56.1strong 319 ExchangeRate-API72.8 53.6developing 320 Amazon Managed Grafana72.8 53.4developing 321 Zoom72.8 49.5developing 322 Aiven72.8 45.0developing 323 CloudZero72.8 43.9developing 324 flagsmith72.8 33.6thin 325 Oracle E-Business Suite72.7 61.4strong 326 Zuplo72.7 60.8strong 327 Mixpanel72.7 56.6strong 328 Workday72.7 52.0developing 329 Maersk72.7 48.5developing 330 BuyWhere72.7 46.2developing 331 Albato A Single No Code Platform For All Automations72.7 45.7developing 332 GenLogs72.7 45.6developing 333 Sumo Logic72.7 44.7developing 334 Application Research72.7 34.6thin 335 Cloudflare72.6 63.4strong 336 IBM72.6 61.4strong 337 Amazon RDS72.6 61.0strong 338 Altruistiq72.6 48.9developing 339 fly-io72.6 35.6thin 340 Svix72.5 78.6exemplar 341 Google Cloud Dataflow72.5 58.9strong 342 JPMorgan Chase72.5 49.6developing 343 Marqeta72.5 47.4developing 344 Zesty72.5 37.6thin 345 AbuseIPDB72.4 55.9strong 346 Grafana72.4 55.6strong 347 Amazon Data Exchange72.4 55.6strong 348 Walmart72.4 55.4strong 349 Ruby Programming Language and Popular API Gems72.4 44.4developing 350 WegoWise72.4 38.8thin 351 beehiiv72.3 71.0exemplar 352 Koala72.3 66.0strong 353 Vessel72.3 65.2strong 354 Amazon DynamoDB72.3 56.1strong 355 Tensor72.3 52.6developing 356 Transifex72.3 43.3developing 357 Cvent Event Cloud72.2 70.4exemplar 358 Hightouch72.2 67.8exemplar 359 1NCE72.2 53.7developing 360 Refinitiv Eikon72.2 48.2developing 361 Discord72.2 46.9developing 362 commercetools72.2 42.4developing 363 Schematic72.2 41.9developing 364 Mailboxlayer72.1 72.6exemplar 365 KonbiniAPI72.1 71.7exemplar 366 Seamless.AI72.1 67.9exemplar 367 Biconomy72.1 59.8strong 368 Reachdesk72.1 57.1strong 369 Google Slides72.1 55.8strong 370 BizAPI72.1 54.2developing 371 Amazon Compute Optimizer72.1 53.9developing 372 CrewAI Cloud72.1 52.7developing 373 Enable Banking72.1 51.6developing 374 ATTOM72.1 50.9developing 375 Amazon Amplify72.1 50.9developing 376 Felt72.1 50.4developing 377 Google Cloud Datastream72.1 49.0developing 378 VNC72.1 48.1developing 379 Albato72.1 47.8developing 380 Neuphonic72.1 47.3developing 381 Jito Labs72.1 47.0developing 382 Productiv72.1 41.1developing 383 Google Cloud Pub/Sub72.1 38.9thin 384 SAP S/4HANA72.1 38.6thin 385 freshdesk72.1 32.9thin 386 Amazon Aurora72.1 32.2thin 387 Amazon Aurora DSQL72.1 32.2thin 388 Amazon Augmented AI72.1 31.1thin 389 Ada72.0 74.0exemplar 390 Gong72.0 63.8strong 391 Covalent72.0 63.8strong 392 Microsoft Graph72.0 58.2strong 393 Replicate72.0 55.6strong 394 Red Hat72.0 54.4strong 395 Hamad Bin Khalifa University72.0 53.0developing 396 Finout72.0 41.4developing 397 Unsplash72.0 40.0developing 398 clickup72.0 35.3thin 399 APIIDA72.0 35.3thin 400 Klaviyo71.9 73.8exemplar 401 Giphy71.9 60.9strong 402 Amazon CloudFormation71.9 57.4strong 403 Halliday71.9 51.8developing 404 Leapsome71.9 45.5developing 405 ExchangeRate-API71.9 44.4developing 406 Unkey71.9 42.7developing 407 SimilarWeb71.8 67.9exemplar 408 Amazon Data Lifecycle Manager71.8 55.3strong 409 Google Cloud Storage71.8 54.9strong 410 Amazon Config71.8 54.8strong 411 AWS CloudWatch71.8 54.8strong 412 Mercedes-Benz Mercedes me71.8 51.3developing 413 University of Manchester71.8 50.5developing 414 SignWell71.8 50.0developing 415 Coinbase71.8 44.6developing 416 freshworks71.8 32.5thin 417 SendGrid71.7 75.5exemplar 418 Twilio71.7 72.3exemplar 419 GitLab71.7 65.2strong 420 socure71.7 64.7strong 421 Syft Data71.7 60.9strong 422 Veritas NetBackup71.7 50.9developing 423 Sendbird71.7 47.9developing 424 Volkswagen71.7 45.6developing 425 Princess Beef Heavy Industries71.7 32.9thin 426 8x871.6 66.3strong 427 Zocdoc71.6 65.3strong 428 Reputation71.6 62.5strong 429 Google Cloud Platform71.6 61.2strong 430 MOLOCO71.6 54.7strong 431 MX Technologies71.6 49.1developing 432 Lattice71.6 48.3developing 433 TVmaze71.5 60.0strong 434 Ethena71.5 52.6developing 435 Goethena71.5 48.7developing 436 Revolut71.5 45.6developing 437 Mindbody71.4 65.6strong 438 ACORD71.4 63.5strong 439 Tibber71.4 62.3strong 440 Unified.to71.4 61.7strong 441 Amazon CloudWatch71.4 59.2strong 442 Currencylayer71.4 58.3strong 443 Amazon MSK71.4 58.1strong 444 Amazon Ground Station71.4 58.1strong 445 Jobber71.4 57.2strong 446 Conekta71.4 55.7strong 447 Amazon Direct Connect71.4 54.2developing 448 Amazon DevOps Guru71.4 53.8developing 449 Google Workspace71.4 51.1developing 450 Amazon CodeCatalyst71.4 49.0developing 451 Amazon MQ71.4 48.9developing 452 TimezoneDB71.4 47.4developing 453 Spacelift71.4 45.6developing 454 Refinitiv71.4 44.9developing 455 Meteomatics71.4 44.7developing 456 anecdotes71.3 64.0strong 457 Instagram71.3 61.9strong 458 Toast71.3 56.3strong 459 Amazon CodeDeploy71.3 52.8developing 460 HipChat deprecated71.3 51.6developing 461 Inkit71.3 49.9developing 462 Tackle.io71.3 47.7developing 463 ACI.dev71.3 37.5thin 464 ThingSpeak71.2 62.2strong 465 Particle71.2 62.1strong 466 MediaMath71.2 60.5strong 467 Amazon Polly71.2 60.4strong 468 Amazon Health Dashboard71.2 59.5strong 469 Salesforce Automation71.2 55.4strong 470 SLNG71.2 55.4strong 471 Claude71.2 55.3strong 472 Amazon CodeBuild71.2 53.6developing 473 Snyk Container71.2 53.2developing 474 Amadeus71.2 51.7developing 475 Amazon71.2 51.5developing 476 Tripetto71.2 44.0developing 477 chucknorris.io71.2 43.3developing 478 Trefle71.2 42.8developing 479 Jetic71.2 40.0developing 480 Primitive71.2 24.9emerging 481 Sensible71.1 62.8strong 482 LALAL.AI71.1 62.6strong 483 OpenADR Alliance71.1 59.0strong 484 Civitai71.1 57.4strong 485 Amazon Step Functions71.1 55.5strong 486 Coval71.1 53.9developing 487 Amazon CodePipeline71.1 53.6developing 488 Uniswap71.1 47.4developing 489 CloudEvents71.1 40.5developing 490 Webflow71.0 59.7strong 491 Paragon71.0 57.2strong 492 Telstra71.0 56.5strong 493 MVMNT71.0 55.1strong 494 Resend71.0 55.1strong 495 Amazon IoT Core71.0 54.7strong 496 Tackle71.0 54.4strong 497 Todoist71.0 51.2developing 498 Pinwheel71.0 50.3developing 499 mlsgrid71.0 49.1developing 500 Juniper Networks71.0 43.4developing

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 prioritized profiling is the fast lane if you would rather have it done for you.

Scored on rubric v0.17.2 across 27,504 providers · lists rebuilt 2026-09-01 · capped at the top 500 per page.

Contract Quality

How it is scored

How the catalog distributes on it

Top providers

The other 7 facets