Peek

Peek is a San Francisco-based travel technology company founded in 2012 by Ruzwana Bashir and Oskar Bruening. It operates two connected surfaces: peek.com, a consumer marketplace of 300,000+ bookable tours, activities, rentals and attractions, and Peek Pro, the booking and back-office operating system used by tour, activity, rental and attraction operators for reservations, capacity and inventory, waivers, payments, dynamic pricing and reporting. Its public API surface is the Peek Reseller API — an implementation of the OCTO (Open Connectivity for Tourism) open standard for the experiences industry, covering products, availability, booking, pricing and booking webhooks — plus a free public remote MCP server at mcp.peek.com that gives AI assistants live experience search, detail and availability, and a Developer Hub with app SDKs, a CLI and an n8n connector for building apps embedded inside Peek Pro.

Peek is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Travel, Tourism, Booking, and Reservations.

The Peek catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Peek’s developer surface includes documentation, API reference, getting-started guide, signup flow, support, engineering blog, CLI, and 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

48.0/100 developing ▬ flat Agent 36/100 agent ready Front door AI 2/6 trace Heartbeat 97/100 alive saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

AccessOpen

2 APIs 1 MCP Servers

Company Travel Tourism Booking Reservations Experience Tours and Activities Payments Marketplace MCPOCTOSoftware-as-a-Service

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 48.0/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 13.4 / 17

Access Clarity 5.8 / 17

Operational Transparency 4.1 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 4.2 / 15

Agent readiness — 36/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 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 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/peek/"><img src="https://apis.io/badge/peek/card.svg" alt="Peek 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):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
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)

7 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

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.

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/peek/apis.yml: open an issue on github.com/api-evangelist/peek 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
OCTO Tours, Activities & Attractions Connectivity (members, known implementations, self-certification)	standard	44.1	1	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

APIs 2

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

Peek Reseller API (OCTO)

Peek Pro's implementation of the OCTO API specification, the open API standard for the experiences industry. Resellers list a supplier's products, check the availability calenda...

Peek Experiences MCP Server

A free, public, anonymous remote MCP server that gives AI assistants access to Peek.com's catalog of 300,000+ verified experiences with real-time availability and pricing. Six t...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Experiences MCP

Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Peek Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Peek Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Peek Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Peek Octo Webhooks

ASYNCAPI

Security Posture 3

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

Peek Authentication

0 schemes

SECURITY

Peek Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Peek Vulnerability Disclosure

Hackerone

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

WellKnown

WellKnown

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Webhooks

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 5

Authentication, authorization, and security posture

SecurityTxt

SecurityTxt

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 3

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

ChangeLog

ChangeLog

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: peek
name: Peek
description: 'Peek is a San Francisco-based travel technology company founded in 2012 by Ruzwana Bashir and Oskar Bruening.
  It operates two connected surfaces: peek.com, a consumer marketplace of 300,000+ bookable tours, activities, rentals and
  attractions, and Peek Pro, the booking and back-office operating system used by tour, activity, rental and attraction operators
  for reservations, capacity and inventory, waivers, payments, dynamic pricing and reporting. Its public API surface is the
  Peek Reseller API — an implementation of the OCTO (Open Connectivity for Tourism) open standard for the experiences industry,
  covering products, availability, booking, pricing and booking webhooks — plus a free public remote MCP server at mcp.peek.com
  that gives AI assistants live experience search, detail and availability, and a Developer Hub with app SDKs, a CLI and an
  n8n connector for building apps embedded inside Peek Pro.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-02'
  method: derived
image: https://cdn.prod.website-files.com/63c9874aa33ce9a6f0ab0e91/63c9874aa33ce95c4eab0ecc_peek-pro-logo.svg
url: https://raw.githubusercontent.com/api-evangelist/peek/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Travel
- Tourism
- Booking
- Reservations
- Experience
- Tours and Activities
- Payments
- Marketplace
- MCP
- OCTO
- Software-as-a-Service
tags_raw:
- Company
- Travel
- Tourism
- Booking
- Reservations
- Experiences
- Tours and Activities
- Payments
- Marketplace
- MCP
- OCTO
- SaaS
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Peek Reseller API (OCTO)
  description: Peek Pro's implementation of the OCTO API specification, the open API standard for the experiences industry.
    Resellers list a supplier's products, check the availability calendar and per-departure availability, reserve and confirm
    bookings with QR-coded vouchers, update, extend, cancel and look up bookings, and register booking webhooks. Two optional
    OCTO capabilities are implemented — octo/pricing and octo/webhooks. Access is by an OCTO API Key issued by Peek on request.
  humanURL: https://octodocs.peek.com/
  baseURL: https://octo.peek.com/integrations/octo
  tags:
  - Booking
  - Reservations
  - Availability
  - Pricing
  - Webhook
  - OCTO
  tags_raw:
  - Booking
  - Reservations
  - Availability
  - Pricing
  - Webhooks
  - OCTO
  properties:
  - type: Documentation
    url: https://octodocs.peek.com/
  - type: GettingStarted
    url: https://octodocs.peek.com/getting-started/basics
  - type: LLMsTxt
    url: llms/peek-llms.txt
  - type: Authentication
    url: authentication/peek-authentication.yml
  - type: ErrorCatalog
    url: errors/peek-problem-types.yml
  - type: Conventions
    url: conventions/peek-conventions.yml
  - type: Webhooks
    url: asyncapi/peek-octo-webhooks.yml
  - type: DataModel
    url: data-model/peek-data-model.yml
- name: Peek Experiences MCP Server
  description: A free, public, anonymous remote MCP server that gives AI assistants access to Peek.com's catalog of 300,000+
    verified experiences with real-time availability and pricing. Six tools cover experience search with region/category/tag/date/geo
    filters, experience detail, availability, region search, tag listing and an embeddable activity-tile widget. Streamable
    HTTP transport; no authentication required.
  humanURL: https://peek.com/mcp
  baseURL: https://mcp.peek.com
  tags:
  - MCP
  - Artificial Intelligence
  - Agents
  - Experience
  - Search
  tags_raw:
  - MCP
  - AI
  - Agents
  - Experiences
  - Search
  properties:
  - type: MCPServer
    url: mcp/peek-mcp.yml
  - type: Documentation
    url: https://github.com/peek-travel/mcp-intro
common:
- type: Website
  url: https://www.peek.com/
- type: DeveloperPortal
  url: https://octodocs.peek.com/
- type: Documentation
  url: https://octodocs.peek.com/
- type: APIReference
  url: https://octodocs.peek.com/booking-flow/products
- type: GettingStarted
  url: https://octodocs.peek.com/getting-started/basics
- type: SignUp
  url: https://www.peekpro.com/get-started
- type: Support
  url: https://www.peekpro.com/support
- type: Blog
  url: https://www.peekpro.com/blog
- type: GitHubOrganization
  url: https://github.com/peek-travel
- type: TermsOfService
  url: https://www.peekpro.com/terms
- type: PrivacyPolicy
  url: https://www.peekpro.com/privacy-policy
- type: LLMsTxt
  url: llms/peek-llms.txt
- type: MCPServer
  url: mcp/peek-mcp.yml
- type: Packages
  url: packages/peek-packages.yml
- type: SDKs
  url: packages/peek-packages.yml
- type: CLI
  url: cli/peek-cli.yml
- type: WellKnown
  url: well-known/peek-well-known.yml
- type: SecurityTxt
  url: well-known/peek-security.txt
- type: Security
  url: security/peek-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/peek-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/peek-domain-security.yml
- type: Conformance
  url: conformance/peek-conformance.yml
- type: Authentication
  url: authentication/peek-authentication.yml
- type: ErrorCatalog
  url: errors/peek-problem-types.yml
- type: Lifecycle
  url: lifecycle/peek-lifecycle.yml
- type: Conventions
  url: conventions/peek-conventions.yml
- type: Webhooks
  url: asyncapi/peek-octo-webhooks.yml
- type: Plans
  url: plans/peek-plans-pricing.yml
- type: RateLimits
  url: rate-limits/peek-rate-limits.yml
- type: DataModel
  url: data-model/peek-data-model.yml
- type: ChangeLog
  url: changelog/peek-changelog.yml
- type: Sandbox
  url: sandbox/peek-sandbox.yml
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Peek API — frequently asked questions

Does Peek have an API?

Yes. APIs.io lists 2 APIs from Peek, including Peek Reseller API (OCTO) and Peek Experiences MCP Server.

How do I authenticate with the Peek API?

Peek uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Peek Authentication.

Does Peek have an MCP server?

Yes. APIs.io lists 1 MCP server for Peek: Build travel itineraries with Peek's 300k+ experiences. Search, details, and availability.

Is the Peek API ready for AI agents?

Peek has a Kin Score of 48.0 out of 100 (developing) and an Agent Readiness score of 35.5 (agent-ready), scored by API Evangelist on 2026-11-02.

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/peek"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.