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.

32,443providers scored on it

10,742score above zero

15.0mean 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 32,443 providers this facet is scored on, bucketed by sub-score.

90-1000 · 0.0%

75-89.956 · 0.2%

50-74.94,924 · 15.2%

25-49.94,090 · 12.6%

0.1-24.91,672 · 5.2%

021,701 · 66.9%

Top providers

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

1 New Relic80.6 71.0exemplar 2 Nylas79.9 87.4exemplar 3 Microsoft Outlook79.8 65.9strong 4 Payrix79.8 62.1strong 5 Karma.Domains79.8 54.3strong 6 UiPath78.8 66.6exemplar 7 Novu78.5 63.4strong 8 BB&T Corp (Truist)78.5 51.2developing 9 AWS Lambda78.2 68.4exemplar 10 Scalar78.1 70.3exemplar 11 Palo Alto Networks78.1 68.2exemplar 12 Withlocals78.0 52.5developing 13 Eventwren77.9 85.6exemplar 14 Revolut77.9 70.0exemplar 15 Asana77.9 67.8exemplar 16 Monite77.6 66.3strong 17 Airtable77.6 62.9strong 18 Upvest77.6 50.1developing 19 SendGrid77.4 85.9exemplar 20 BTSE77.3 55.6strong 21 Phare77.2 62.0strong 22 Amazon API Gateway77.1 69.1exemplar 23 Veeva77.0 76.1exemplar 24 Fireflies.ai76.7 71.1exemplar 25 Telnyx76.6 86.2exemplar 26 Canva76.6 69.3exemplar 27 GatiFlow76.4 95.3exemplar 28 ZoomInfo76.4 86.6exemplar 29 Kit76.4 79.7exemplar 30 GitHub76.4 79.0exemplar 31 Karbon76.4 71.2exemplar 32 Firma.dev76.4 63.3strong 33 Xero76.2 84.5exemplar 34 Weavr76.0 72.2exemplar 35 Super Payments76.0 67.5exemplar 36 Vertesia76.0 54.1developing 37 Method Financial75.9 69.5exemplar 38 Lightspark75.9 67.3exemplar 39 Thanx75.8 74.4exemplar 40 Paack75.7 50.8developing 41 Seismic75.6 66.2strong 42 EmailConnect by XADI75.6 60.7strong 43 Kontakt.io75.5 71.4exemplar 44 Canvas Medical75.5 64.6strong 45 Wappalyzer75.4 66.6exemplar 46 Citi75.4 61.4strong 47 Tray.ai75.3 87.8exemplar 48 Okta75.3 73.8exemplar 49 Commune75.2 64.2strong 50 Atlar75.2 57.3strong 51 Lightspeed Commerce75.1 83.9exemplar 52 MediaRuntime75.1 63.5strong 53 Bancomat75.1 58.0strong 54 OpsGenie75.1 48.0developing 55 ExchangeRate-API75.1 46.1developing 56 Narmi75.0 66.7exemplar 57 Hagglebee74.9 84.3exemplar 58 Yarnhen74.9 84.3exemplar 59 Yawplet74.9 84.3exemplar 60 Cloudflare74.9 80.6exemplar 61 cloro74.9 74.6exemplar 62 Moov74.9 74.4exemplar 63 Tripleseat74.9 42.0developing 64 Deel74.8 63.0strong 65 Notion74.7 61.5strong 66 Lichess74.7 53.0developing 67 Entur74.6 69.6exemplar 68 Plugsurfing74.6 49.5developing 69 Didomi74.5 80.0exemplar 70 Ironfang74.5 78.7exemplar 71 Adobe Captivate74.5 48.3developing 72 Workday Payroll74.5 42.1developing 73 Confluent74.3 85.3exemplar 74 Snyk74.3 79.1exemplar 75 Salesforce Marketing Cloud74.3 79.1exemplar 76 Vaquill AI74.3 71.6exemplar 77 Eagle Eye Networks74.2 51.5developing 78 NMI74.2 47.2developing 79 Medplum74.1 71.7exemplar 80 Amazon FreeRTOS74.1 65.9strong 81 FIS Global74.1 60.6strong 82 Spendesk74.1 59.8strong 83 Huddlekit74.1 54.3strong 84 Letta74.1 51.5developing 85 KnoxCall74.0 73.7exemplar 86 Moneyhub74.0 67.8exemplar 87 Bitbucket73.9 71.4exemplar 88 Bud Financial Limited73.9 53.6developing 89 Render73.9 50.9developing 90 Yelp73.9 47.8developing 91 Zoho CRM73.8 84.4exemplar 92 Anysphere Cursor Ai73.8 75.1exemplar 93 Anysphere Cursor.com73.8 75.1exemplar 94 Forage73.7 59.9strong 95 Amazon EventBridge73.7 59.2strong 96 Shodan73.7 56.7strong 97 Popp73.7 47.7developing 98 Elation Health73.6 79.4exemplar 99 JobsPipe73.6 74.4exemplar 100 Honeycomb73.6 65.0strong 101 Copper Financial73.6 64.4strong 102 Absentify73.6 49.0developing 103 Paubox73.5 77.0exemplar 104 NameGender73.5 60.6strong 105 Fusio73.5 59.4strong 106 ZnanyLekarz73.4 74.3exemplar 107 Shopify Admin API73.4 36.3thin 108 Postman73.3 78.0exemplar 109 Atlassian73.3 73.8exemplar 110 UserGems73.3 70.2exemplar 111 Mailmodo73.3 63.0strong 112 Amplitude73.3 57.6strong 113 BodySpec73.3 48.0developing 114 Amazon Pinpoint73.2 77.8exemplar 115 BigCommerce73.1 82.5exemplar 116 Dun & Bradstreet73.1 60.7strong 117 Act-On73.0 66.1strong 118 Riskified73.0 61.6strong 119 Salesforce72.9 88.8exemplar 120 Square72.9 78.1exemplar 121 Vonage72.9 71.3exemplar 122 akta.pro72.9 69.5exemplar 123 Akahu72.9 64.0strong 124 The Colony72.8 74.8exemplar 125 Regal72.8 70.0exemplar 126 E2B72.8 65.4strong 127 Massive (formerly Polygon.io)72.8 64.9strong 128 MX Technologies72.8 64.9strong 129 Elastic.io72.8 41.6developing 130 Smile72.7 43.2developing 131 CData72.6 82.9exemplar 132 Snowflake72.6 81.2exemplar 133 shipcloud72.6 53.9developing 134 Certifyos72.5 65.8strong 135 Telesign72.4 72.0exemplar 136 Bandwidth72.4 61.0strong 137 Intuit72.4 57.7strong 138 Beyond Identity72.4 48.4developing 139 Recal72.4 46.4developing 140 Tabby72.3 77.3exemplar 141 HighLevel72.3 66.9exemplar 142 DataForSEO72.3 65.8strong 143 OpenAI72.2 84.5exemplar 144 Fama72.2 62.5strong 145 GTM API72.2 59.9strong 146 SMTP Senpai (MailSenpai)72.2 59.0strong 147 Infinite Audience72.2 47.7developing 148 Infobip72.1 84.9exemplar 149 Stripe72.1 81.1exemplar 150 Tyk72.1 59.6strong 151 Ada72.0 87.6exemplar 152 Brevo72.0 80.8exemplar 153 hi.health72.0 65.3strong 154 Limble CMMS71.9 75.5exemplar 155 Sinch71.9 71.7exemplar 156 Pandium71.9 63.2strong 157 HM Courts & Tribunals Service71.9 50.0developing 158 Twilio71.8 91.6exemplar 159 Cockroach Labs71.8 71.5exemplar 160 Sendcloud71.8 66.7exemplar 161 Arcade.dev71.8 58.7strong 162 Sideko71.8 40.4developing 163 C.H. Robinson71.7 55.3strong 164 Arcadiapower271.7 52.1developing 165 Orion Health71.7 38.4thin 166 AfterShip71.6 82.6exemplar 167 Unstoppable Finance (Iron)71.6 67.2exemplar 168 FRAYT71.6 49.7developing 169 APIs.io71.5 93.8exemplar 170 Azure DevOps71.5 75.4exemplar 171 Zapier71.5 67.4exemplar 172 Amazon Entity Resolution71.5 62.0strong 173 commercetools71.5 61.8strong 174 Shippo71.5 48.8developing 175 Gainsight71.4 82.4exemplar 176 Amazon Lex71.4 76.2exemplar 177 Thanks.io71.4 72.1exemplar 178 CM.com71.4 64.1strong 179 Coinbase71.4 54.8strong 180 AB Tasty71.4 47.4developing 181 Dwolla71.3 72.9exemplar 182 Raiffeisenbank (Russia)71.3 63.2strong 183 Ankr71.3 55.6strong 184 Apple71.3 55.2strong 185 Caliza71.3 53.7developing 186 Monerium71.3 51.8developing 187 Amazon B2B Data Interchange71.3 46.3developing 188 Cito CS2 API71.2 63.0strong 189 Plainrouter71.2 62.3strong 190 Asapp371.2 60.2strong 191 ShipStation71.2 56.2strong 192 Recall.ai71.2 51.2developing 193 Formfeed71.1 76.8exemplar 194 Trustly Group71.1 71.4exemplar 195 Microsoft71.1 67.7exemplar 196 SecurityScorecard71.1 60.3strong 197 Asaas71.1 43.2developing 198 Grain71.0 52.3developing 199 WhatsApp71.0 51.1developing 200 Appmixer71.0 50.5developing 201 Amazon Audit Manager71.0 32.0thin 202 Anthropic70.9 89.0exemplar 203 Cumulocity70.9 68.1exemplar 204 FrontApp70.9 61.8strong 205 FISKIL70.9 52.7developing 206 Appwrite70.8 82.3exemplar 207 OpenMercantil70.8 79.0exemplar 208 Figma70.8 59.6strong 209 Amazon EC2 Image Builder70.8 58.8strong 210 Bond70.8 58.2strong 211 Latitude70.8 57.7strong 212 Bird70.8 48.6developing 213 Lemmy70.8 34.3thin 214 Shopify70.7 83.0exemplar 215 Adobe Launch70.7 73.9exemplar 216 Delinea70.7 69.8exemplar 217 Eliq70.7 66.5exemplar 218 fal70.7 65.6strong 219 Ploid70.7 65.2strong 220 Origin Energy70.7 59.6strong 221 Gloat70.7 54.5strong 222 Olo70.7 52.7developing 223 Adobe Photoshop70.7 50.7developing 224 Sanity70.7 50.6developing 225 Amazon AppSync70.7 31.8thin 226 Harness70.6 89.2exemplar 227 Customer.io70.6 84.0exemplar 228 Roark70.6 72.6exemplar 229 Workato70.6 65.7strong 230 Microsoft Office 36570.6 61.8strong 231 Axuall70.6 61.4strong 232 Notarize70.6 54.0developing 233 LaunchDarkly70.5 79.7exemplar 234 Automation Anywhere70.5 74.6exemplar 235 Contentstack70.5 73.6exemplar 236 SpicyAPI70.5 68.3exemplar 237 Microsoft Active Directory70.5 61.8strong 238 1Password70.5 60.4strong 239 AhaSend70.4 82.8exemplar 240 Optimizely70.4 81.3exemplar 241 Amigo70.4 78.8exemplar 242 Microsoft Azure70.4 76.5exemplar 243 Onfleet70.4 60.5strong 244 Amazon Firewall Manager70.4 57.5strong 245 LinkedIn70.3 74.8exemplar 246 Arcmira70.3 64.3strong 247 Amazon Forecast70.3 56.1strong 248 Airbnb70.3 45.8developing 249 Backpack70.3 44.7developing 250 GitHub Actions70.2 81.3exemplar 251 Sentry70.2 79.0exemplar 252 Clerk70.2 70.5exemplar 253 Azupay70.2 63.3strong 254 Monocrawl70.2 57.3strong 255 Edit Square70.2 49.7developing 256 Sorsa70.2 48.7developing 257 Amazon SES70.1 79.0exemplar 258 drchrono70.1 77.0exemplar 259 SnapTrade70.1 58.9strong 260 Solcast70.1 51.2developing 261 Clearstreet8e7170.1 50.0developing 262 openEO70.1 48.5developing 263 D-ID70.1 40.9developing 264 Slash70.0 69.5exemplar 265 Wealth Reader70.0 67.8exemplar 266 Synup70.0 62.2strong 267 Google Docs70.0 57.9strong 268 Pipeliner CRM70.0 57.9strong 269 YouSign70.0 53.3developing 270 Pipedream70.0 53.2developing 271 Dub70.0 52.7developing 272 Simon Data69.9 64.8strong 273 Metriport69.9 64.0strong 274 UptimeRobot69.9 61.0strong 275 DeepL69.9 51.8developing 276 Q269.9 48.5developing 277 Folk69.9 38.5thin 278 Swetrix69.8 75.5exemplar 279 Hint Health69.8 73.5exemplar 280 Lili69.8 68.7exemplar 281 gridX69.8 59.7strong 282 Bringg69.8 48.5developing 283 SAP HANA69.8 45.2developing 284 Fastly69.7 63.7strong 285 Treblle69.7 62.6strong 286 Domain Group69.7 58.7strong 287 Argyle9a2569.7 52.4developing 288 Informatica69.7 48.7developing 289 Sitecore69.7 32.8thin 290 GitLab69.6 81.0exemplar 291 Amazon DynamoDB69.6 78.8exemplar 292 Timely (Memory AS)69.6 72.3exemplar 293 Astra69.6 47.7developing 294 Stannp69.5 74.7exemplar 295 CircleCI69.5 66.1strong 296 iDenfy69.4 67.2exemplar 297 Autodesk69.4 60.3strong 298 Amazon Fraud Detector69.4 55.9strong 299 AWS App Runner69.4 55.6strong 300 LiveLike69.4 50.0developing 301 OutSystems69.3 75.8exemplar 302 Bloomreach69.3 71.3exemplar 303 Nutanix69.3 65.9strong 304 Snov.io69.3 65.7strong 305 Bluecore69.3 57.7strong 306 August Health69.3 53.6developing 307 DoorLoop69.3 51.6developing 308 Conductor69.3 40.5developing 309 DreamFactory69.3 40.1developing 310 Wayfair69.3 38.1thin 311 Axiom69.3 37.7thin 312 Plaid69.2 84.6exemplar 313 Uphold69.2 79.6exemplar 314 Amazon CodeGuru Profiler69.2 73.7exemplar 315 publiq69.2 71.5exemplar 316 Contrast Security69.2 58.6strong 317 Workday69.2 55.9strong 318 Quandoo69.2 44.6developing 319 Phonely69.2 38.7thin 320 Doordash69.1 76.2exemplar 321 Cash App69.1 65.8strong 322 Up69.1 60.1strong 323 Amazon X-Ray69.1 59.6strong 324 Bendigo and Adelaide Bank69.1 54.6strong 325 Trigger.dev69.1 52.2developing 326 Torii69.1 48.6developing 327 Listen Notes69.1 47.9developing 328 CryptoCompare69.1 41.5developing 329 LogicMonitor69.0 72.6exemplar 330 Culture Amp69.0 66.6exemplar 331 Currencycloud69.0 63.8strong 332 Amazon Glue DataBrew69.0 63.5strong 333 Amazon Direct Connect69.0 60.4strong 334 Amazon DevOps Guru69.0 58.5strong 335 Amazon Device Farm69.0 54.7strong 336 Ironclad69.0 51.8developing 337 Silverfin69.0 45.7developing 338 Spoonacular69.0 45.4developing 339 Telenor Sverige69.0 44.5developing 340 Shutterstock69.0 42.9developing 341 API Snap69.0 38.0thin 342 OpenUV69.0 36.9thin 343 Memo Bank68.9 68.8exemplar 344 Docusign68.9 68.5exemplar 345 Adobe Experience Cloud68.9 67.2exemplar 346 Sifflet68.9 60.0strong 347 Tableau68.9 49.9developing 348 Siemens Insights Hub (MindSphere)68.9 41.9developing 349 Mubert68.9 34.2thin 350 APIGen68.9 34.1thin 351 Convoy68.8 66.9exemplar 352 VideoGen68.8 64.8strong 353 OpenWeatherMap68.8 54.1developing 354 npm68.8 48.3developing 355 Knative68.8 47.1developing 356 MongoDB68.7 76.9exemplar 357 Adyen68.7 71.1exemplar 358 NextGen Healthcare68.7 66.6exemplar 359 Common Room68.7 65.7strong 360 Microsoft Planner68.7 59.3strong 361 Ringover68.7 53.9developing 362 Autodesk Construction Cloud68.7 49.1developing 363 Affirm68.7 33.0thin 364 Omnisend68.6 73.0exemplar 365 PipesHub68.6 72.0exemplar 366 SMTP2GO68.6 67.4exemplar 367 Knock68.6 61.2strong 368 Amazon CodeArtifact68.6 57.0strong 369 Bump.sh68.6 56.0strong 370 Axway68.6 54.6strong 371 123FormBuilder68.6 52.5developing 372 Signal68.6 41.4developing 373 Jira68.5 75.3exemplar 374 Match It Up68.5 68.6exemplar 375 SafetyCulture68.5 68.1exemplar 376 iBanFirst68.5 63.8strong 377 Rachio68.5 57.8strong 378 Rollee68.5 55.6strong 379 WhiteBIT68.5 51.5developing 380 Google Maps Platform68.5 51.3developing 381 JPMorgan Chase68.5 50.7developing 382 PagoPA68.4 69.0exemplar 383 Clarafintech68.4 63.1strong 384 S&P Global68.4 61.3strong 385 Hookdeck68.4 59.4strong 386 Phone Com68.4 55.9strong 387 Predoc68.4 55.0strong 388 Banyan Systems68.4 45.0developing 389 Yapily68.4 42.1developing 390 Thomson Reuters68.3 55.5strong 391 Cognition Labs68.3 52.3developing 392 Choreo68.3 50.2developing 393 IFS68.3 47.8developing 394 Twenty68.3 39.5developing 395 Kinde68.2 82.4exemplar 396 Adobe Campaign68.2 70.7exemplar 397 Boomi68.2 62.7strong 398 Hookbase68.2 59.2strong 399 Trulioo68.2 55.6strong 400 Blockdaemon68.2 55.0strong 401 Knit68.2 51.6developing 402 KeySavvy68.2 46.9developing 403 TaxJar68.2 44.6developing 404 Chloris Geospatial68.2 39.9developing 405 Wallarm68.2 38.9thin 406 Birdeye68.1 77.0exemplar 407 Dentsply Sirona68.1 67.7exemplar 408 Immutable68.1 67.7exemplar 409 Amazon Cognito68.1 65.7strong 410 Mlsgrid68.1 63.0strong 411 Observe68.1 63.0strong 412 Amazon EventBridge Pipes68.1 60.2strong 413 Amazon EventBridge Scheduler68.1 60.2strong 414 AppOmni68.1 56.3strong 415 Zitadel68.1 49.0developing 416 Inscribe68.1 45.8developing 417 BrewPage68.1 41.5developing 418 PandaDoc68.1 41.4developing 419 Port Community Systems68.1 34.6thin 420 Amber Electric68.0 64.2strong 421 Genome68.0 63.9strong 422 Zoom68.0 56.2strong 423 Apidog68.0 52.9developing 424 Adobe67.9 76.2exemplar 425 Chronosphere67.9 60.9strong 426 SPS Commerce67.9 59.8strong 427 Microsoft Copilot67.9 50.8developing 428 Billie67.9 49.4developing 429 Dealroom67.9 44.1developing 430 TagoIO67.9 40.7developing 431 Billieio67.9 39.5developing 432 Amazon EC267.8 62.2strong 433 SailPoint67.8 54.6strong 434 Google Gemini67.8 53.5developing 435 Ramp67.8 47.5developing 436 Google Places67.8 45.0developing 437 Basecamp67.8 43.2developing 438 Varonis67.8 37.8thin 439 Transifex67.8 35.0thin 440 WellCare Health Plans67.8 34.7thin 441 The Things Network / The Things Stack67.7 70.9exemplar 442 Amazon GuardDuty67.7 62.3strong 443 PostOnce67.7 59.5strong 444 Veracode67.7 57.3strong 445 Ribbon Health67.7 56.6strong 446 Zluri67.7 46.4developing 447 Warp67.7 43.8developing 448 Routific67.7 43.7developing 449 TROLIE67.7 43.5developing 450 Loggi67.7 42.9developing 451 Statsig67.6 75.2exemplar 452 Kong67.6 71.8exemplar 453 Meltwater67.6 71.2exemplar 454 Tink67.6 65.3strong 455 Space Frontiers67.6 63.4strong 456 Groupe BPCE67.6 62.5strong 457 Etsy67.6 50.3developing 458 Two67.6 49.8developing 459 Wahoo Fitness67.6 46.5developing 460 Parasail67.6 43.9developing 461 EBANX67.6 34.7thin 462 Amazon Athena67.6 31.8thin 463 Amazon Kendra67.5 66.2strong 464 Amazon CloudWatch67.5 60.6strong 465 Lucca67.5 47.5developing 466 Agrio67.5 36.6thin 467 Datadog67.4 77.6exemplar 468 Google67.4 68.6exemplar 469 Kargo67.4 54.0developing 470 Moment67.4 45.2developing 471 RapidAPI67.4 40.4developing 472 Fellow67.3 67.2exemplar 473 SAKURA internet67.3 63.7strong 474 Benchmark Email67.3 63.5strong 475 AccuraCite67.3 59.3strong 476 Runloop67.3 54.0developing 477 Exa67.3 53.7developing 478 Adobe Creative Cloud67.3 51.1developing 479 Wufoo67.3 50.4developing 480 CloudTruth67.3 46.4developing 481 KEDA67.3 45.6developing 482 Gumlet67.2 69.6exemplar 483 Apigee67.2 66.9exemplar 484 Fortify67.2 57.4strong 485 Amazon SNS67.2 56.9strong 486 Fitbit67.2 54.3strong 487 Byrd67.2 53.1developing 488 Mindee67.2 50.0developing 489 Oracle Database67.2 49.8developing 490 Reflektive67.2 39.4developing 491 Amazon Application Migration Service67.2 30.5thin 492 BigPanda67.1 71.6exemplar 493 Checkmarx67.1 57.0strong 494 Fixer67.1 47.9developing 495 Indexed67.1 44.8developing 496 Cesium67.1 43.7developing 497 GitHub Copilot67.0 68.7exemplar 498 Squarespace67.0 68.3exemplar 499 1NCE67.0 46.1developing 500 Indeed67.0 44.4developing

Move this number. Every provider in the catalog is profiled into a public record at artifacts.apis.io/<provider>/, and each check above names the exact artifact it reads. Publish the artifact, open an issue on github.com/api-evangelist/<provider> pointing at it, 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.25.0 across 32,443 providers · lists rebuilt 2026-10-29 · 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