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 is listed with 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 engineering blog, documentation, authentication, changelog, sandbox, API reference, getting-started guide, and 27 more developer resources.
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/.
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/autoura/"><img src="https://apis.io/badge/autoura/card.svg" alt="Autoura 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):
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)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
3 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
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 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.
The Autoura Experience API provides access to tourism content including cuisine guides, destination information, tour itineraries, local activities, and points of interest. Deve...
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...
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.
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: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
probe_state: gated
source:
- plans
- authentication
- scopes
- rate-limits
- security
- sandbox
generated: '2026-11-06'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/autoura.png
access: 3rd-Party
created: '2025-03-01'
modified: '2026-10-06'
url: https://raw.githubusercontent.com/api-evangelist/autoura/refs/heads/main/apis.yml
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
common:
- type: Deprecation
url: lifecycle/autoura-lifecycle.yml
- type: Hosts
url: hosts/autoura-hosts.yml
- type: Vendors
url: vendors/autoura-vendors.yml
- type: FinOps
url: finops/autoura-finops.yml
- url: https://www.autoura.com/blog/
type: Blog
- 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: 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: 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
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
x-coverage:
state: gated
reason: partner-login
method: derived
generated: '2026-10-20'
generator: derive-coverage.py (pre-flight evidence)
detail: the company serves an API surface but requires credentials before any description of it can be read
evidence:
- url: https://api.autoura.com/api/mcp
status: 401
- url: https://www.autoura.com/api/mcp
status: 401
- url: https://www.autoura.com
status: 200
x-enrichment:
date: '2026-10-20'
status: enriched
artifacts_added: 0
pass: local-v5
Autoura API — frequently asked questions
Does Autoura have an API?
Yes. APIs.io lists 2 APIs from Autoura, including Autoura Experience API and Autoura MCP Server.
How do I authenticate with the Autoura API?
Autoura documents its authentication (apiKey/http/oauth2/openIdConnect · 6 schemes). The details are profiled on APIs.io as Autoura Authentication.
How much does the Autoura API cost?
APIs.io lists 3 pricing plans for Autoura, with each plan's price, limits and inclusions under Pricing on this page.
Does Autoura have an MCP server?
Yes. APIs.io lists 1 MCP server for Autoura: Remote MCP server at api.autoura.com over HTTP requiring OAuth; 21 tools listed.
Is the Autoura API ready for AI agents?
Autoura has a Kin Score of 33.2 out of 100 (thin) and an Agent Readiness score of 48.4 (agent-ready), scored by API Evangelist on 2026-11-06.
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.