AI Agents (A2A agent cards)

Where this market publishes its structure

• Providers' own A2A Agent Cards (/.well-known/agent-card.json, agent.json), catalog all/*/a2a manifests re-probed live machine-readable, 487 probed 2026-10-15: live 389, flavored 62, gone 27, not_a_card 7, platform_served 2
• a2aregistry.org /api/agents (limit<=100, offset paged; registry.json is a soft-200 shell) machine-readable, 566 listings on 304 hosts; getvda.ai 98, workers.dev 73
• AGNTCY Agent Directory (dir.agntcy.org) not machine-readable: gRPC/DHT via dirctl; no public HTTP listing
• Agent Name Service (agentnameservice.org) not machine-readable: marketing page; no public listing API
• NANDA index (index.projectnanda.org) not machine-readable: JS testnet app; no machine-readable listing
• agentregistry.ai not machine-readable: parked domain

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-15 from the 151 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 1 · other companies invest to build on it

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

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

covered 4 · reached mainly through aggregators

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

mixed 2 · no single mode dominates

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

long-tail 8 · reached only through iPaaS bridges

distribution 2 · only sells through cloud marketplaces

undeclared 115 · 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: 11; bridges: 0.