Markets · bedrock market · provisional

Official SDKs on Package Registries

Distribution market (official client libraries per language; providers ranked). The Kin Score Market layer reads each provider in its market: who it integrates with, how deep those integrations go, and where the market publishes its own structure. Methodology.

43providers measured
34 (79.1%)declare their own
3 (7.0%)covered by others only
6 (14.0%)distribution only (sell through, not integrations)
0 (0.0%)undeclared
22declare compatibility (report only, not weighted)
15in-market workflows shown
Provisional. Provisional and unweighted: the Market layer is not part of the composite or agent readiness. Leader lists are read within a position, never as one ranking. A provider that declares nothing we can read is shown as undeclared, with no number: we never infer integrations.

Where this market publishes its structure

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 43 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 2 · other companies invest to build on it

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Stripe 70.6 959 819 / 140 0 11 37 partner-built 89%, provider-built 2%, ipaas-bridge 4%, contract 2%, standard 1%, builds-on-platform 1%, distribution 1%
Adyen 60.6 106 44 / 62 0 9 3 partner-built 59%, provider-built 12%, ipaas-bridge 3%, contract 10%, standard 6%, builds-on-platform 2%, distribution 8%

builds-on 18 · publishes apps on other platforms' stores

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
LaunchDarkly 55.2 43 0 / 43 0 10 5 ipaas-bridge 12%, contract 5%, standard 7%, covered 12%, builds-on-platform 42%, distribution 23%
Keeper Security 55.1 28 0 / 28 0 10 0 contract 3%, standard 21%, builds-on-platform 41%, distribution 34%
Algolia 54.2 47 0 / 47 0 12 14 own-page 10%, ipaas-bridge 29%, standard 4%, covered 4%, builds-on-platform 27%, distribution 25%
Statsig 52.4 23 0 / 23 0 7 2 ipaas-bridge 9%, standard 4%, covered 13%, builds-on-platform 43%, distribution 30%
Sentry 52.1 31 0 / 31 0 13 4 ipaas-bridge 12%, standard 9%, covered 6%, builds-on-platform 33%, distribution 39%
DevCycle 51.8 18 0 / 18 0 8 1 ipaas-bridge 5%, standard 16%, builds-on-platform 37%, distribution 42%
Contentstack 49.2 18 0 / 18 0 9 2 ipaas-bridge 11%, standard 5%, covered 5%, builds-on-platform 32%, distribution 47%
Bugsnag 47.7 18 0 / 18 0 9 2 ipaas-bridge 11%, standard 11%, covered 11%, builds-on-platform 21%, distribution 47%
Flagsmith 47.1 16 0 / 16 0 9 0 standard 6%, builds-on-platform 41%, distribution 53%
Mollie 46.6 16 0 / 16 0 6 2 ipaas-bridge 12%, contract 19%, covered 6%, builds-on-platform 25%, distribution 38%
Fortanix 41.7 10 0 / 10 0 5 0 standard 20%, builds-on-platform 30%, distribution 50%
Svix 40.2 15 0 / 15 0 9 2 ipaas-bridge 12%, standard 12%, builds-on-platform 19%, distribution 56%
MailerLite 38.5 48 0 / 48 0 5 36 ipaas-bridge 78%, contract 2%, covered 2%, builds-on-platform 7%, distribution 11%
Factset 37.6 11 0 / 11 0 7 0 standard 9%, coverage 9%, builds-on-platform 18%, distribution 64%
Skyflow 33.4 5 0 / 5 0 4 0 builds-on-platform 20%, distribution 80%
WhoisFreaks 33.4 13 0 / 13 0 8 3 ipaas-bridge 23%, builds-on-platform 15%, distribution 62%
Bitculator 32.6 6 0 / 6 0 5 0 builds-on-platform 17%, distribution 83%
Chalk 32.6 6 0 / 6 0 5 0 builds-on-platform 17%, distribution 83%

coverage 3 · reaches banks, carriers, systems or channels (an aggregator)

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
RudderStack 51.4 39 0 / 39 0 8 0 coverage 62%, covered 3%, builds-on-platform 15%, distribution 21%
Telesign 31.8 11 0 / 11 0 6 2 ipaas-bridge 18%, coverage 27%, distribution 55%
SignalWire 25.9 9 0 / 9 0 6 2 ipaas-bridge 22%, coverage 11%, distribution 67%

covered 1 · reached mainly through aggregators

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Dinari 33.7 5 0 / 5 0 4 0 covered 20%, distribution 80%

regulated 1 · named in a regulator's register or partners' contracts

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Stark Bank 32.9 7 0 / 7 0 6 0 contract 14%, distribution 86%

standard 7 · listed by a voluntary standard's own directory

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Yugabyte 45.8 13 0 / 13 0 6 0 standard 31%, covered 8%, builds-on-platform 15%, distribution 46%
Authlete 39.9 11 0 / 11 0 7 0 standard 18%, builds-on-platform 18%, distribution 64%
APIMatic 37.5 9 0 / 9 0 7 0 standard 20%, builds-on-platform 10%, distribution 70%
IPinfo 35.3 13 0 / 13 0 9 2 ipaas-bridge 15%, standard 8%, builds-on-platform 8%, distribution 69%
Evervault 34.1 9 0 / 9 0 5 1 ipaas-bridge 11%, standard 33%, distribution 56%
Qiniu Cloud 31.6 8 0 / 8 0 7 0 standard 12%, distribution 88%
WebScraping.AI 26.8 10 0 / 10 0 8 2 ipaas-bridge 18%, standard 9%, distribution 73%

mixed 5 · no single mode dominates

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
OpenAI 55.6 73 0 / 73 1 6 35 ipaas-bridge 49%, contract 4%, standard 10%, covered 17%, builds-on-platform 10%, distribution 8%, unknown 1%
Anthropic 54.2 31 0 / 31 1 10 2 ipaas-bridge 6%, contract 10%, standard 16%, covered 16%, builds-on-platform 16%, distribution 32%, unknown 3%
AfterShip 53.5 30 0 / 30 0 7 1 provider-built 3%, own-page 42%, ipaas-bridge 3%, builds-on-platform 29%, distribution 23%
Talon.One 39.6 9 0 / 9 0 4 1 ipaas-bridge 11%, standard 11%, covered 22%, builds-on-platform 11%, distribution 44%
Appwrite 31.0 11 0 / 11 0 9 1 ipaas-bridge 8%, standard 8%, covered 8%, distribution 75%

distribution 6 · only sells through cloud marketplaces

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Featureflip 28.8 6 0 / 6 0 6 0 distribution 100%
ForceDream 28.8 5 0 / 5 0 5 0 distribution 100%
Incognia 28.8 6 0 / 6 0 6 0 distribution 100%
Intrinio 28.8 5 0 / 5 0 5 0 distribution 100%
ReqKey 28.8 6 0 / 6 0 6 0 distribution 100%
AxonFlow 28.7 4 0 / 4 0 4 0 distribution 100%

Top workflows by market votes

Workflows (Arazzo) and their phrasing are generated by API Evangelist, ranked by market votes (integration edges in the graph, weighted by channel).

In-market workflows only: a step on the market provider's side maps to this market's business capabilities (), and the partner is not a generic export/notify app. Other workflows are counted as bridges (including any whose steps do not resolve to a capability yet). Methodology. In-market: 71; bridges: 0.

WorkflowBetweenVotesWeightedArazzo
Push Stripe successful charges as HubSpot deals
When a Stripe charge succeeds, look up the matching HubSpot Contact and create a Closed Won HubSpot Deal with the charge amount and currency.
Stripe ↔ HubSpot 2 2.0 workflow generated by API Evangelist
Sync Stripe customers into Salesforce contacts
When a Stripe customer is created, look them up by email and create the matching Salesforce Contact with billing details.
Stripe ↔ Salesforce 2 2.0 workflow generated by API Evangelist
Replace WooCommerce Stripe plugin with declarative integration
List WooCommerce store orders and create a matching Stripe payment intent for a selected order's total and currency.
Stripe ↔ WooCommerce 2 1.9 workflow generated by API Evangelist
Commercetools
Adyen ↔ commercetools 3 1.8 workflow generated by API Evangelist
commercetools
Discover how the Adyen payments integration for commercetools can optimize your ecommerce conversions
Adyen ↔ commercetools 3 1.8 workflow generated by API Evangelist
commercetools
Algolia ↔ commercetools 3 1.8 workflow generated by API Evangelist
Get Slack notifications for new Stripe sales
Get Slack notifications for new Stripe sales
Stripe ↔ Slack 3 1.8 workflow generated by API Evangelist
Post Stripe payment alerts to Slack channels
Retrieve a Stripe charge and post a payment alert to a designated Slack channel.
Stripe ↔ Slack 3 1.8 workflow generated by API Evangelist
Post failed Stripe payments to Slack
Post failed Stripe payments to Slack
Stripe ↔ Slack 3 1.8 workflow generated by API Evangelist
plaid
Adyen ↔ Plaid 2 1.8 workflow generated by API Evangelist
Add Stripe Checkout completers to a Mailchimp audience
When a Stripe Checkout session completes, subscribe the buyer to a Mailchimp audience with plan and MRR merge tags.
Stripe ↔ Mailchimp 2 1.4 workflow generated by API Evangelist
Add new Stripe customers to Mailchimp lists
Add new Stripe customers to Mailchimp lists
Stripe ↔ Mailchimp 2 1.4 workflow generated by API Evangelist
Attach Stripe customer history to Zendesk tickets
On ticket open, fetch the requester's Stripe customer and recent charges and open a Zendesk ticket enriched with that billing history.
Stripe ↔ Zendesk 2 1.4 workflow generated by API Evangelist
Create Xero invoices for new Stripe payments
Create Xero invoices for new Stripe payments
Stripe ↔ Xero 2 1.4 workflow generated by API Evangelist
File Stripe sales through TaxJar
Sync paid Stripe invoices to TaxJar as order transactions for automated sales tax filing.
Stripe ↔ TaxJar 2 1.4 workflow generated by API Evangelist

Generated 2026-10-24 from API Evangelist's own files; nothing on this page is a model's judgement. Provisional and unweighted; not part of the Kin Score composite or agent readiness. Read the Market layer methodology. Disagree with an edge? Every edge cites its evidence and can be corrected through the normal correction path.