Autoura website screenshot

Autoura

Autoura is a UK digital experience platform (DXP) for real-world tourism and travel experiences, operated by The Spontaneous Travel Company Limited. It structures and maintains experience data — venues, attractions, tours, routes, stops, accessibility and dietary signals, AI guide characters and storytelling — so travel companies, destination management organizations and, increasingly, AI agents can act on it. Autoura is agent-native rather than agent-adjacent: it advertises its own agent skill from a link rel="ai-skill" element in its homepage head, runs a hosted remote MCP server behind OAuth 2.1 with PKCE and dynamic client registration, exposes the same tool set as WebMCP on its PlanMyVisit consumer product, and addresses consumer profiles by DID with DIDComm v2 messaging. A REST API over api.autoura.com serves routes, stops, visits, characters, MoveMe audio and a consent-brokered consumer preference graph, with dietary requirements keyed on IATA airline special-meal codes.

Autoura publishes 2 APIs on the APIs.io network. Tagged areas include Tourism, Tours, Travel, Destination, and Experience.

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

Autoura’s developer surface includes documentation, authentication, changelog, sandbox, API reference, getting-started guide, pricing, and 24 more developer resources.

33.2/100 thin ▬ flat Agent 51/100 agent ready saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
AccessPaidSelf serve⚡ Free to try
2 APIs 1 MCP Servers 5 Features 4 Use Cases
TourismToursTravelDestinationExperienceDigital Tourism

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
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 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/.
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 github.com/api-evangelist/autoura: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

Autoura Experience API

The Autoura Experience API provides access to tourism content including cuisine guides, destination information, tour itineraries, local activities, and points of interest. Deve...

Autoura MCP Server

Autoura's hosted remote Model Context Protocol server, the surface it builds for AI agents first. One endpoint carries two permission-scoped tool sets: a B2B set for brands, att...

MCP Servers 1

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

Autoura MCP Server

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Autoura Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Autoura Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Features 5

Notable capabilities this provider offers.

Destination Content API

Access rich destination content including local attractions, points of interest, neighborhood guides, and cultural highlights for tourism applications and travel content platforms.

Cuisine and Food Guide API

Comprehensive cuisine data including local dishes, restaurant types, food tours, and gastronomic experience recommendations for culinary tourism applications.

Tour Itineraries

Pre-built tour itineraries and self-guided tour content for destinations, enabling travel apps to offer structured sightseeing experiences.

Activity Recommendations

Activity and experience data for destinations including outdoor activities, cultural experiences, adventure tourism, and seasonal events.

Personalized Recommendations

Context-aware recommendation engine for suggesting local experiences based on traveler preferences, location, and time of visit.

Event Specifications 1

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

Security Posture 2

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

Autoura Authentication

apiKey/http/oauth2/openIdConnect · 6 schemes

SECURITY

Autoura Domain Security

TLSv1.3 · HSTS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Autoura Scopes

3 scopes · authorizationCode

3 scopes

SCOPES

Use Cases 4

What developers build with this provider.

Travel App Integration

Integrate Autoura destination content into travel booking apps and tourism portals to enhance destination discovery and trip planning.

Destination Marketing

Destination management organizations embed Autoura experience content into tourism websites to promote local attractions and activities.

Culinary Tourism

Food and travel platforms use the Cuisine API to build gastronomic guides and food tour features for culinary travelers.

Digital Tour Guide Apps

Build digital tour guide applications with self-guided audio tours, interactive maps, and Autoura destination content.

Integrations 3

Pre-built integrations with other platforms and tools.

Booking Platforms

Integration with travel booking platforms to surface Autoura activity and experience content alongside accommodation and transport bookings.

Mapping Services

Combine Autoura POI and destination content with Google Maps, Mapbox, or Apple Maps for location-aware tourism applications.

CMS Platforms

Embed Autoura destination content into CMS-based tourism websites using API integrations for dynamic content delivery.

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: autoura
name: Autoura
description: 'Autoura is a UK digital experience platform (DXP) for real-world tourism and travel experiences, operated by
  The Spontaneous Travel Company Limited. It structures and maintains experience data — venues, attractions, tours, routes,
  stops, accessibility and dietary signals, AI guide characters and storytelling — so travel companies, destination management
  organizations and, increasingly, AI agents can act on it. Autoura is agent-native rather than agent-adjacent: it advertises
  its own agent skill from a link rel="ai-skill" element in its homepage head, runs a hosted remote MCP server behind OAuth
  2.1 with PKCE and dynamic client registration, exposes the same tool set as WebMCP on its PlanMyVisit consumer product,
  and addresses consumer profiles by DID with DIDComm v2 messaging. A REST API over api.autoura.com serves routes, stops,
  visits, characters, MoveMe audio and a consent-brokered consumer preference graph, with dietary requirements keyed on IATA
  airline special-meal codes.'
tags:
- Tourism
- Tours
- Travel
- Destination
- Experience
- Digital Tourism
tags_raw:
- Tourism
- Tours
- Travel
- Destinations
- Experiences
- Digital Tourism
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Commercial SaaS with a callable hosted API and MCP server
  confidence: high
  source:
  - plans
  - probe
  generated: '2026-09-13'
  method: derived
  note: Published subscription tiers (30/125/250 USD per month) with Creem.io as merchant of record, and a live callable host
    — https://api.autoura.com/api returns a structured 401 on every documented endpoint and https://api.autoura.com/api/mcp
    returns an RFC 9728 challenge.
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: true
  public: true
  label: Paid subscription, with a published public test API key for evaluation
  confidence: high
  source:
  - plans
  - docs
  generated: '2026-09-13'
  method: derived
  note: No free tier — the entry plan is 30 USD/month. Autoura does publish a shared read-only test API key in its public
    authentication documentation, so the read surface can be exercised with no account, which is what try_now records here.
    Sign-up is self-serve through the pricing page; changing account level is not.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/autoura.png
access: 3rd-Party
created: '2025-03-01'
modified: '2026-09-13'
url: https://raw.githubusercontent.com/api-evangelist/autoura/refs/heads/main/apis.yml
specificationVersion: '0.23'
apis:
- aid: autoura:autoura-api
  name: Autoura Experience API
  description: The Autoura Experience API provides access to tourism content including cuisine guides, destination information,
    tour itineraries, local activities, and points of interest. Developers can integrate Autoura content into travel applications,
    tourism websites, and experience booking platforms to provide personalized local recommendations.
  humanURL: https://www.autoura.com/docs/api
  tags:
  - Tourism
  - Tours
  - Travel
  - Destination
  - Activities
  - Cuisine
  tags_raw:
  - Tourism
  - Tours
  - Travel
  - Destinations
  - Activities
  - Cuisine
  baseURL: https://api.autoura.com/api
  properties:
  - type: Documentation
    url: https://www.autoura.com/docs/api
  - type: APIReference
    url: https://www.autoura.com/docs/api
  - type: Authentication
    url: https://www.autoura.com/docs/api/authentication
  - type: GettingStarted
    url: https://www.autoura.com/docs/api/authentication
  - type: ChangeLog
    url: https://www.autoura.com/docs/api/changelog
  - type: Website
    url: https://www.autoura.com
- aid: autoura:autoura-mcp
  name: Autoura MCP Server
  description: 'Autoura''s hosted remote Model Context Protocol server, the surface it builds for AI agents first. One endpoint
    carries two permission-scoped tool sets: a B2B set for brands, attractions, tour operators, destinations, designers and
    suppliers managing experience data, and a consumer set (PlanMyVisit) for agents helping a person plan and carry out a
    single real-world visit. Authorization is OAuth 2.1 with PKCE and dynamic client registration, advertised through a conformant
    RFC 9728 protected-resource document; Autoura also documents an email-verification-code path to a 48-hour bearer token
    for agents onboarding a human account. The same tool set is exposed as WebMCP on PlanMyVisit pages.'
  humanURL: https://www.autoura.com/docs/api/mcp
  baseURL: https://api.autoura.com/api/mcp
  tags:
  - MCP
  - AI Agents
  - Tourism
  - Travel
  - Experience
  - Visit Planning
  tags_raw:
  - MCP
  - AI Agents
  - Tourism
  - Travel
  - Experiences
  - Visit Planning
  properties:
  - type: MCPServer
    url: mcp/autoura-mcp.yml
  - type: ToolCrosswalk
    url: mcp/autoura-tool-crosswalk.yml
  - type: Documentation
    url: https://www.autoura.com/docs/api/mcp
  - type: AgentSkill
    url: skills/_index.yml
  - type: Authentication
    url: authentication/autoura-authentication.yml
common:
- type: DomainSecurity
  url: security/autoura-domain-security.yml
- type: GitHubOrganization
  url: https://github.com/Autoura
- type: LinkedIn
  url: https://www.linkedin.com/company/autoura
- type: Website
  url: https://www.autoura.com
- type: Documentation
  url: https://www.autoura.com/docs/api
- type: Features
  data:
  - name: Destination Content API
    description: Access rich destination content including local attractions, points of interest, neighborhood guides, and
      cultural highlights for tourism applications and travel content platforms.
  - name: Cuisine and Food Guide API
    description: Comprehensive cuisine data including local dishes, restaurant types, food tours, and gastronomic experience
      recommendations for culinary tourism applications.
  - name: Tour Itineraries
    description: Pre-built tour itineraries and self-guided tour content for destinations, enabling travel apps to offer structured
      sightseeing experiences.
  - name: Activity Recommendations
    description: Activity and experience data for destinations including outdoor activities, cultural experiences, adventure
      tourism, and seasonal events.
  - name: Personalized Recommendations
    description: Context-aware recommendation engine for suggesting local experiences based on traveler preferences, location,
      and time of visit.
- type: UseCases
  data:
  - name: Travel App Integration
    description: Integrate Autoura destination content into travel booking apps and tourism portals to enhance destination
      discovery and trip planning.
  - name: Destination Marketing
    description: Destination management organizations embed Autoura experience content into tourism websites to promote local
      attractions and activities.
  - name: Culinary Tourism
    description: Food and travel platforms use the Cuisine API to build gastronomic guides and food tour features for culinary
      travelers.
  - name: Digital Tour Guide Apps
    description: Build digital tour guide applications with self-guided audio tours, interactive maps, and Autoura destination
      content.
- type: Integrations
  data:
  - name: Booking Platforms
    description: Integration with travel booking platforms to surface Autoura activity and experience content alongside accommodation
      and transport bookings.
  - name: Mapping Services
    description: Combine Autoura POI and destination content with Google Maps, Mapbox, or Apple Maps for location-aware tourism
      applications.
  - name: CMS Platforms
    description: Embed Autoura destination content into CMS-based tourism websites using API integrations for dynamic content
      delivery.
- type: MCPServer
  url: mcp/autoura-mcp.yml
- type: ToolCrosswalk
  url: mcp/autoura-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/autoura-well-known.yml
- type: Authentication
  url: authentication/autoura-authentication.yml
- type: OAuthScopes
  url: scopes/autoura-scopes.yml
- type: Conventions
  url: conventions/autoura-conventions.yml
- type: ErrorCatalog
  url: errors/autoura-problem-types.yml
- type: Lifecycle
  url: lifecycle/autoura-lifecycle.yml
- type: ChangeLog
  url: changelog/autoura-changelog.yml
- type: Conformance
  url: conformance/autoura-conformance.yml
- type: DataModel
  url: data-model/autoura-data-model.yml
- type: Webhooks
  url: asyncapi/autoura-webhooks.yml
- type: Sandbox
  url: sandbox/autoura-sandbox.yml
- type: Components
  url: components/autoura-components.yml
- type: Plans
  url: plans/autoura-plans-pricing.yml
- type: RateLimits
  url: rate-limits/autoura-rate-limits.yml
- type: LLMsTxt
  url: llms/autoura-llms.txt
- type: APIReference
  url: https://www.autoura.com/docs/api
- type: DeveloperPortal
  url: https://www.autoura.com/docs/api
- type: GettingStarted
  url: https://www.autoura.com/docs/api/authentication
- type: Pricing
  url: https://www.autoura.com/pricing
- type: SignUp
  url: https://www.autoura.com/pricing
- type: TermsOfService
  url: https://www.autoura.com/legal/terms
- type: PrivacyPolicy
  url: https://www.autoura.com/legal/privacy
- type: Support
  url: https://www.autoura.com/contact
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
x-enrichment:
  date: '2026-09-13'
  status: enriched
  artifacts_added: 36
  pass: local-v3

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/autoura"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/autoura/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/autoura/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.

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