Accelerator Portfolios (Y Combinator, 500 Global, Antler participation)

Where this market publishes its structure

• Y Combinator company pages (ycombinator.com/companies/, page's own data-page JSON) machine-readable, 873 company pages read (839 slugs from the catalog's y-combinator portfolio file + tag-pool repo slugs); 870 with a website; 704 providers linked by domain
• Y Combinator directory search (ycombinator.com/companies listing, Algolia) not machine-readable: driven by a time-limited Algolia secured key embedded in the page (an embedded access token); not used
• 500 Global portfolio (500.co/companies -> 500.co/api/startups, the page's own public JSON) machine-readable, 2,241 companies, 2,176 with a website; 1,661 providers linked; 4 LP fund rows held
• Antler portfolio (antler.co/portfolio, Webflow list ?0b933bfd_page=N) machine-readable, 1,096 companies, 1,076 with a website; 29 providers linked (mostly pre-seed, not in the catalog)
• Techstars portfolio search (techstars.com/portfolio) not machine-readable: Typesense multi_search with an API key embedded in the page (embedded access token); not used. Server HTML carries only the 29-company unicorn registry as logos

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 75 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 3 · other companies invest to build on it

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

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

covered 4 · reached mainly through aggregators

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

core 1 · builds the connectors its customers need

mixed 4 · no single mode dominates

list 2 · a long list on its own page, mostly unevidenced

long-tail 3 · reached only through iPaaS bridges

distribution 9 · only sells through cloud marketplaces

undeclared 19 · declares nothing we can read: no number

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: 75; bridges: 0.