Open Connectivity for Tours, Activities, and Attractions

OCTO (Open Connectivity for Tours, Activities, and Attractions) is an open standard API specification for the in-destination experiences sector of the travel industry. The standard defines agreed-upon schemas, endpoints, and capabilities commonly needed when connecting platforms, resellers, OTAs, and other technologies in tours, activities, and attractions. OCTO is open source.

Open Connectivity for Tours, Activities, and Attractions publishes 4 API contracts indexed on the APIs.io network, including Availability API, Bookings API, Products API, and 1 more. Tagged areas include Activities, Attractions, Open Standard, Tours, and Travel.

The Open Connectivity for Tours, Activities, and Attractions catalog on APIs.io includes 1 Spectral governance ruleset.

Open Connectivity for Tours, Activities, and Attractions’ developer surface includes authentication, documentation, getting-started guide, support, and 9 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

28.5/100 thin ▬ flat Agent 25/100 agent aware Front door AI 3/6 light Heartbeat 0/100 dormant Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract

Activities Attractions Open Standard Tours Travel

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 28.5/100 · thin

Contract Quality 9.0 / 19

Developer Ergonomics 5.7 / 15

Access Clarity 1.0 / 15

Operational Transparency 1.2 / 10

Contract Governance 1.2 / 9

Discoverability 4.8 / 8

Regulatory Posture 0.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/octo/"><img src="https://apis.io/badge/octo/card.svg" alt="Open Connectivity for Tours, Activities, and Attractions on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 6.4 — up to +18.7 composite points Ask about this →
Contract Quality scores 48.2 — up to +13.0 composite points Ask about this →
Developer Ergonomics scores 38.1 — up to +12.4 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/octo/apis.yml: open an issue on github.com/api-evangelist/octo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

Open Connectivity for Tours, Activities, and Attractions Availability API

The Availability API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for availability.

Open Connectivity for Tours, Activities, and Attractions Bookings API

The Bookings API from Open Connectivity for Tours, Activities, and Attractions — 5 operation(s) for bookings.

Open Connectivity for Tours, Activities, and Attractions Products API

The Products API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for products.

Open Connectivity for Tours, Activities, and Attractions Supplier API

The Supplier API from Open Connectivity for Tours, Activities, and Attractions — 1 operation(s) for supplier.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Open Connectivity for Tours, Activities, and Attractions OCTO API Specification Availability API

OPEN COLLECTION

Open Connectivity for Tours, Activities, and Attractions OCTO API Specification Availability Bookings API

OPEN COLLECTION

Open Connectivity for Tours, Activities, and Attractions OCTO API Specification Availability Products API

OPEN COLLECTION

Open Connectivity for Tours, Activities, and Attractions OCTO API Specification Availability Supplier API

OPEN COLLECTION

Open Connectivity for Tours, Activities, and Attractions API pricing

Not yet checked against Open Connectivity for Tours, Activities, and Attractions's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against Open Connectivity for Tours, Activities, and Attractions's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Open Connectivity for Tours, Activities, and Attractions Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Open Connectivity for Tours, Activities, and Attractions Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Open Connectivity for Tours, Activities, and Attractions Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Open Connectivity for Tours, Activities, and Attractions API Rules

49 rules · 47 error-severity 1 warn-severity 1 info-severity

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Open Connectivity for Tours, Activities, and Attractions Authentication

http · 1 scheme

SECURITY

Open Connectivity for Tours, Activities, and Attractions Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Open Connectivity for Tours, Activities, and Attractions Agentic Access

12 operations · 7 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LlmsText

LlmsText

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: octo
name: Open Connectivity for Tours, Activities, and Attractions
description: OCTO (Open Connectivity for Tours, Activities, and Attractions) is an open standard API specification for the
  in-destination experiences sector of the travel industry. The standard defines agreed-upon schemas, endpoints, and capabilities
  commonly needed when connecting platforms, resellers, OTAs, and other technologies in tours, activities, and attractions.
  OCTO is open source.
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/octo.png
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Activities
- Attractions
- Open Standard
- Tours
- Travel
url: https://raw.githubusercontent.com/api-evangelist/octo/refs/heads/main/apis.yml
created: '2024-06-07'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: octo:octo-availability-api
  name: Open Connectivity for Tours, Activities, and Attractions Availability API
  description: The Availability API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for availability.
  humanURL: https://docs.octo.travel/
  tags:
  - Availability
  properties:
  - type: OpenAPI
    url: openapi/octo-availability-api-openapi.yml
  - type: Documentation
    url: https://docs.octo.travel/
- aid: octo:octo-bookings-api
  name: Open Connectivity for Tours, Activities, and Attractions Bookings API
  description: The Bookings API from Open Connectivity for Tours, Activities, and Attractions — 5 operation(s) for bookings.
  humanURL: https://docs.octo.travel/
  tags:
  - Booking
  tags_raw:
  - Bookings
  properties:
  - type: OpenAPI
    url: openapi/octo-bookings-api-openapi.yml
  - type: Documentation
    url: https://docs.octo.travel/
- aid: octo:octo-products-api
  name: Open Connectivity for Tours, Activities, and Attractions Products API
  description: The Products API from Open Connectivity for Tours, Activities, and Attractions — 2 operation(s) for products.
  humanURL: https://docs.octo.travel/
  tags:
  - Product
  tags_raw:
  - Products
  properties:
  - type: OpenAPI
    url: openapi/octo-products-api-openapi.yml
  - type: Documentation
    url: https://docs.octo.travel/
- aid: octo:octo-supplier-api
  name: Open Connectivity for Tours, Activities, and Attractions Supplier API
  description: The Supplier API from Open Connectivity for Tours, Activities, and Attractions — 1 operation(s) for supplier.
  humanURL: https://docs.octo.travel/
  tags:
  - Supplier
  properties:
  - type: OpenAPI
    url: openapi/octo-supplier-api-openapi.yml
  - type: Documentation
    url: https://docs.octo.travel/
common:
- type: Plans
  url: plans/octo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/octo-rate-limits.yml
- type: FinOps
  url: finops/octo-finops.yml
- type: Website
  url: https://www.octo.travel/
- type: AgenticAccess
  url: agentic-access/octo-agentic-access.yml
- type: DomainSecurity
  url: security/octo-domain-security.yml
- type: Authentication
  url: authentication/octo-authentication.yml
- type: GitHubOrganization
  url: https://github.com/OctoConsulting
- type: Documentation
  url: https://docs.octo.travel/
- type: GettingStarted
  url: https://docs.octo.travel/getting-started/
- type: Authentication
  url: https://docs.octo.travel/getting-started/authentication
- type: Support
  url: https://docs.octo.travel/getting-started/development-support
- type: LlmsText
  url: https://docs.octo.travel/llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Open Connectivity for Tours, Activities, and Attractions API — frequently asked questions

Does Open Connectivity for Tours, Activities, and Attractions have an API?

Yes. APIs.io lists 4 APIs from Open Connectivity for Tours, Activities, and Attractions, including Open Connectivity for Tours, Activities, and Attractions Availability API, Open Connectivity for Tours, Activities, and Attractions Bookings API and Open Connectivity for Tours, Activities, and Attractions Products API, and 1 more.

Is there an OpenAPI specification for the Open Connectivity for Tours, Activities, and Attractions API?

Yes. APIs.io indexes 4 OpenAPI specifications for Open Connectivity for Tours, Activities, and Attractions, each linked for download from this page.

How do I authenticate with the Open Connectivity for Tours, Activities, and Attractions API?

Open Connectivity for Tours, Activities, and Attractions uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Open Connectivity for Tours, Activities, and Attractions Authentication.

How much does the Open Connectivity for Tours, Activities, and Attractions API cost?

APIs.io lists 3 pricing plans for Open Connectivity for Tours, Activities, and Attractions, with each plan's price, limits and inclusions under Pricing on this page.

Is the Open Connectivity for Tours, Activities, and Attractions API ready for AI agents?

Open Connectivity for Tours, Activities, and Attractions has a Kin Score of 28.5 out of 100 (thin) and an Agent Readiness score of 25.4 (agent-aware), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/octo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/octo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/octo/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.