Markets · bedrock market · provisional

Official CLIs on Package Managers

Distribution market (official command-line tools per package manager; 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.

33providers measured
24 (72.7%)declare their own
5 (15.2%)covered by others only
4 (12.1%)distribution only (sell through, not integrations)
0 (0.0%)undeclared
16declare 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-21 from the 33 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.

TagsOpen Source 42%
Tag groupsDeveloper Tools 27%, MCP 21%, Infrastructure 21%, Kubernetes 21%
IndustriesDeveloper Tools & DevOps 64%, Artificial Intelligence 21%
CapabilitiesBC-4270 24%, BC-620 24%, BC-4210 21%

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 931 802 / 129 0 8 36 partner-built 90%, provider-built 3%, ipaas-bridge 4%, contract 2%, standard 1%, builds-on-platform 1%, distribution 1%
Phrase 51.8 56 32 / 24 0 2 2 partner-built 56%, provider-built 23%, ipaas-bridge 4%, standard 2%, builds-on-platform 12%, distribution 4%

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

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Keeper Security 54.0 21 0 / 21 0 9 0 contract 5%, standard 14%, builds-on-platform 41%, distribution 41%
Snyk 52.3 17 0 / 17 0 4 1 ipaas-bridge 6%, contract 6%, standard 28%, builds-on-platform 39%, distribution 22%
Sentry 52.1 23 0 / 23 0 9 4 ipaas-bridge 16%, standard 16%, covered 4%, builds-on-platform 28%, distribution 36%
Temporal 45.2 7 0 / 7 0 2 0 standard 14%, builds-on-platform 57%, distribution 29%
Rancher 44.1 9 0 / 9 0 3 0 standard 30%, builds-on-platform 40%, distribution 30%
Docker 42.7 10 0 / 10 0 4 0 standard 20%, builds-on-platform 40%, distribution 40%
Buf 41.5 9 0 / 9 0 5 0 standard 10%, builds-on-platform 40%, distribution 50%
Netlify 40.4 13 0 / 13 0 4 4 ipaas-bridge 29%, standard 7%, builds-on-platform 36%, distribution 29%
Gitea 40.2 8 0 / 8 0 4 0 standard 12%, builds-on-platform 38%, distribution 50%
VMware 40.2 4 0 / 4 0 2 0 builds-on-platform 50%, distribution 50%
WakaTime 38.9 7 0 / 7 0 2 1 ipaas-bridge 14%, builds-on-platform 57%, distribution 29%
Env0 38.0 5 0 / 5 0 4 0 builds-on-platform 33%, distribution 67%
Bitwarden 36.6 9 0 / 9 0 5 1 ipaas-bridge 10%, builds-on-platform 40%, distribution 50%
Fleet 36.4 3 0 / 3 0 3 0 builds-on-platform 25%, distribution 75%
IPinfo 26.8 10 0 / 10 0 7 2 ipaas-bridge 20%, builds-on-platform 10%, distribution 70%
Cursor 19.9 7 0 / 7 0 2 4 ipaas-bridge 57%, builds-on-platform 14%, distribution 29%

covered 1 · reached mainly through aggregators

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
RabbitMQ 40.2 4 0 / 4 0 2 0 standard 25%, covered 25%, distribution 50%

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

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Vultr 46.8 10 0 / 10 0 3 0 standard 50%, builds-on-platform 20%, distribution 30%
Istio 45.7 5 0 / 5 0 2 0 standard 60%, distribution 40%
Containerd 40.7 4 0 / 4 0 2 0 standard 50%, distribution 50%
Knative 40.7 4 0 / 4 0 2 0 standard 50%, distribution 50%
Arduino 35.8 4 0 / 4 0 3 0 standard 25%, distribution 75%

mixed 3 · no single mode dominates

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Google 60.7 37 0 / 37 0 3 6 ipaas-bridge 23%, contract 8%, standard 19%, covered 15%, builds-on-platform 23%, distribution 12%
Algolia 54.2 41 0 / 41 0 9 14 own-page 12%, ipaas-bridge 33%, standard 10%, covered 5%, builds-on-platform 19%, distribution 21%
Cloud Foundry 44.3 9 0 / 9 0 3 0 standard 33%, builds-on-platform 33%, distribution 33%

distribution 6 · only sells through cloud marketplaces

ProviderDepthIntegrationsIn / outUnknown builderDistributioniPaaS bridgeMix
Nexla 28.7 4 0 / 4 0 6 0 distribution 100%
Appwrite 25.7 7 0 / 7 0 7 1 ipaas-bridge 12%, distribution 88%
Airweave 21.7 3 0 / 3 0 4 1 ipaas-bridge 20%, distribution 80%
AWS CLI 19.2 thin 2 0 / 2 0 2 0 distribution 100%
Columnar 19.2 thin 2 0 / 2 0 3 0 distribution 100%
cURL 19.2 thin 2 0 / 2 0 2 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: 52; 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
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
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
Reconcile Stripe payouts in Xero bank transactions
List Stripe payouts and create matching Xero bank transactions for reconciliation.
Stripe ↔ Xero 2 1.4 workflow generated by API Evangelist
Sync BigCommerce orders to Stripe payments
For a BigCommerce storefront order, materialize the matching Stripe PaymentIntent so financial reporting consolidates in Stripe.
Stripe ↔ BigCommerce 2 1.4 workflow generated by API Evangelist
Sync Stripe trial-end events to Iterable
Retrieve a Stripe subscription nearing trial end and track it as a custom user event in Iterable to trigger conversion campaigns.
Stripe ↔ Iterable 2 1.4 workflow generated by API Evangelist

Generated 2026-10-21 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.