Social and Fediverse

Where this market publishes its structure

• FediDB server software register (api.fedidb.org/v1/software) machine-readable
• Providers' own ActivityPub / federation pages (fetched, saved under evidence/compatibility/) machine-readable
• Discord App Directory not machine-readable: undocumented internal endpoint
• Patreon app directory not machine-readable: 403 to non-browser clients
• YouTube / Twitch creator partner directories not machine-readable: no public listing
• joinmastodon.org server directory not machine-readable: JSON, but community instances, not companies

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 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.

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.

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

covered 6 · reached mainly through aggregators

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

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

undeclared 21 · declares nothing we can read: no number

Workflows

No in-market workflows yet; bridges: 3 (3 not yet mapped to a capability). In-market workflows only: a step on the market provider's side maps to this market's business capabilities (BC-4270, BC-400.60, BC-3780), 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.

Shape adoption report only — not weighted

Pattern: register. Shape gravity (counted by company, one edge per provider, the best evidence kept): 9. Convergence in the cohort: 8 of 31 (25.8%) — cohort members (minus the anchor's family, mediators and rival shapes) with at least one compatible edge to the shape, read from evidence.

activitypub anchor ActivityPub · 9 adopters, 9 declared by the provider

By degree: declared-subset 5, declared-unqualified 2. By evidence: own-docs 7.

• Rival shapes (own contracts, not re-served): Bluesky
• In the cohort, declaring nothing we can read: Automattic, X, LinkedIn, Instagram, Snapchat, Reddit, Discord, Twitch, YouTube Data, TikTok, Pinterest, Telegram, Facebook, Substack, Medium, Patreon, Kick, Buffer, Hootsuite, Sprout Social, Later, Linktree, Kajabi
• Evidence ladder: conformance-register > own-docs > own-contract > own-blog > ae-structural. Degrees: full | declared-subset | declared-unqualified | interoperable-subset | same-vocabulary-own-path.