OCTO Tours, Activities & Attractions Connectivity (members, known implementations, self-certification)

Where this market publishes its structure

• OCTO member directory (octo.travel/members; the page's own public JSON octo.travel/api/members) machine-readable, 124 members (77 technology, 47 industry), 92 with a website; 8 linked
• OCTO Known Implementations (docs.octo.travel/additional-resources/known-implementations; public Google Sheet CSV export, 3 tabs) machine-readable, 267 rows: reseller 176 (155 live), supplier 71 (49 live), connected systems 21 (12 live); 59 powered-by rows held as platform customers; 6 linked
• OCTO self-certification directory (certify.octo.travel/verify; public JSON api/certification/public + api/accounts/names) machine-readable, 226 certifications (157 approved, 39 of them inactive = lapsed; 69 requested) over 147 accounts; 4 linked
• OCTO OpenAPI (app.swaggerhub.com/apis-docs/OCTO-API/OCTO-API/1.0, linked from docs.octo.travel) machine-readable, the specification itself, recorded as spec_url on every edge; not a register
• OCTO Implementation Directory (member benefit on octo.travel) not machine-readable: behind member login (octo.travel/login, robots-disallowed); not attempted
• certify.octo.travel certificate detail / validation runs not machine-readable: validationRuns empty in the public JSON; per-certificate pages need sign-in
• OCTO Slack #implementation-support not machine-readable: members only

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

undeclared 42 · declares nothing we can read: no number