Engine website screenshot

Engine

Engine (formerly Hotel Engine, rebranded in 2024) is a Denver, Colorado business travel and spend platform for booking and managing lodging, flights, rental cars, group travel, and meeting and event spaces, with travel policy enforcement, trip approvals, consolidated DirectBill invoicing, and the Engine X charge card. Engine says it serves 25,000+ businesses and 1.2 million travelers with negotiated rates across 1,000,000+ hotel properties. Its API product is Omni — a partner-facing lodging inventory API offered over gRPC and HTTP/JSON, authenticated with mutual TLS, that covers property content, real-time rate shopping, booking, folio generation, and cancellation. Omni is protobuf-first: the proto contracts are published under Apache 2.0 on GitHub and the Swagger document, descriptor set, and JVM client bindings are generated from them and released per version.

Engine publishes 4 API contracts indexed on the APIs.io network, including Catalog Service API, Lodging Booking Service API, Lodging Shopping Service API, and 1 more. Tagged areas include Company, Travel, Business Travel, Lodging, and Hotels.

The Engine catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Engine’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 83 more developer resources.

62.9/100 strong ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent Heartbeat 81/100 alive open core · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessApproval
1 published contract 4 Agent Skills
CompanyTravelBusiness TravelLodgingHotelsBookingTravel ManagementExpense ManagementPaymentsgRPCProtobufPartner API

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
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 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. Kin Score badge preview for Engine It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/hotel-engine/"><img src="https://apis.io/badge/hotel-engine/card.svg" alt="Engine 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
  • 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
  • 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)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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/hotel-engine/apis.yml: open an issue on github.com/api-evangelist/hotel-engine 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.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Travel and Airline Distribution builds-on 17.2 (thin) - -
Buf Schema Registry (public Protocol Buffers modules, gRPC / ConnectRPC schema publishers) builds-on 17.2 (thin) - -

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 3

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.

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified
measured — observed by APIs.io (published)
measured — observed by APIs.io (declared)

APIs 4

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

Engine Catalog Service API

The CatalogService API from Engine — 1 operation(s) for catalogservice.

Engine Lodging Booking Service API

The LodgingBookingService API from Engine — 5 operation(s) for lodgingbookingservice.

Engine Lodging Shopping Service API

The LodgingShoppingService API from Engine — 2 operation(s) for lodgingshoppingservice.

Engine Content Service API

The Content Service API from Engine — 2 operation(s) for content service.

Open Collections 4

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

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Engine API pricing

Prices published by Engine, read 2026-10-28 from engine.com/pricing.

PlanPrice
Engine Engine is free. Not a free trial. Actually free.
Includes: No membership fees, no contracts, no minimum spend; hotels pay Engine a commission

Plan details, limits and sources →

Rate limits

All 16 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hotel Engine Rate Limits

16 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Engine

SLA

FinOps 1

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

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Hotel Engine Context

100 classes · 176 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Engine API Rules

60 rules · 51 errors 7 warnings 2 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Hotel Engine Omni Partner Api Overlay

9 actions · update · hotel-engine-omni-partner-api-openapi.yml

DERIVED

JSON Schema 15

Standalone JSON Schema definitions for this provider's data models.

apiHttpBody

3 properties

JSON SCHEMA

Book_Lodging_Service_BookRequest_v1

4 properties

JSON SCHEMA

GetPropertiesRequest_v1

1 properties

JSON SCHEMA

GetPropertiesResponse_v1

2 properties

JSON SCHEMA

ListPropertiesResponse_v1

2 properties

JSON SCHEMA

ListPropertyCatalogRequest_v1

2 properties

JSON SCHEMA

ListPropertyCatalogResponse_v1

2 properties

JSON SCHEMA

Scroll for all 15

Security Posture 4

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

Hotel Engine Authentication

mutualTLS · 1 scheme

SECURITY

Hotel Engine Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Hotel Engine Vulnerability Disclosure

Hackerone · contact published

SECURITY

Hotel Engine Trust Center

SOC 2 Type II

SECURITY

Agentic Access 1

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

Hotel Engine Agentic Access

11 operations · 7 acting

11 operations · 7 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 6

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 48

Properties that don't map to a standard resource type

Scroll for all 48

Source (apis.yml)

apis.yml Raw ↑
aid: hotel-engine
name: Engine
description: 'Engine (formerly Hotel Engine, rebranded in 2024) is a Denver, Colorado business travel and spend platform for
  booking and managing lodging, flights, rental cars, group travel, and meeting and event spaces, with travel policy enforcement,
  trip approvals, consolidated DirectBill invoicing, and the Engine X charge card. Engine says it serves 25,000+ businesses
  and 1.2 million travelers with negotiated rates across 1,000,000+ hotel properties. Its API product is Omni — a partner-facing
  lodging inventory API offered over gRPC and HTTP/JSON, authenticated with mutual TLS, that covers property content, real-time
  rate shopping, booking, folio generation, and cancellation. Omni is protobuf-first: the proto contracts are published under
  Apache 2.0 on GitHub and the Swagger document, descriptor set, and JVM client bindings are generated from them and released
  per version.'
deliveryModel:
  model: open-core
  license: Apache-2.0
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://engine.com/_astro/engine-og-default.BAjJjAAC.png
url: https://raw.githubusercontent.com/api-evangelist/hotel-engine/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-source-url: https://forgeglobal.com/hotel-engine_stock/
x-tier: profiled
x-tier-reason: enrichment
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Travel
- Business Travel
- Lodging
- Hotels
- Booking
- Travel Management
- Expense Management
- Payments
- gRPC
- Protobuf
- Partner API
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: FinOps
  url: finops/hotel-engine-finops.yml
- type: Spectral
  url: rules/hotel-engine-rules.yml
- type: JSONLD
  url: json-ld/hotel-engine-context.jsonld
- type: Vocabulary
  url: vocabulary/hotel-engine-vocabulary.yml
- type: TrustCenter
  url: security/hotel-engine-trust-center.yml
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-v1-room.proto
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-v1-offer.proto
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-service-v1-service.proto
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-service-v1-find_best_offers_streaming.proto
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-service-v1-find_best_offers.proto
- type: Protobuf
  url: grpc/hotel-engine-shop-lodging-service-v1-find_availability.proto
- type: Protobuf
  url: grpc/hotel-engine-service-common-v1-error.proto
- type: Protobuf
  url: grpc/hotel-engine-content-v1-lodging-room.proto
- type: Protobuf
  url: grpc/hotel-engine-content-v1-lodging-property.proto
- type: Protobuf
  url: grpc/hotel-engine-content-service-v1-service.proto
- type: Protobuf
  url: grpc/hotel-engine-content-service-v1-list_property_catalog.proto
- type: Protobuf
  url: grpc/hotel-engine-content-service-v1-list_properties.proto
- type: Protobuf
  url: grpc/hotel-engine-content-service-v1-get_properties.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-traveler.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-sell_type.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-refund.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-price.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-postal_address.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-payment_info.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-payment_card.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-media.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-loyalty.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-image.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-geo.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-engine_direct_bill.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-currency.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-contact.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-conditions.proto
- type: Protobuf
  url: grpc/hotel-engine-common-v1-actions.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-status.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-reservation.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-quote.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-metadata.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-guests.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-v1-booking.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-submit_cancellation.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-service.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-preview_cancellation.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-get_bookings_streaming.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-get_bookings.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-generate_folio.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-confirm_offer.proto
- type: Protobuf
  url: grpc/hotel-engine-book-lodging-service-v1-book.proto
- type: Protobuf
  url: grpc/hotel-engine-book-common-v1-applied_payment_info.proto
- type: Protobuf
  url: grpc/hotel-engine-book-common-service-v1-error.proto
- type: WellKnown
  url: well-known/hotel-engine-well-known.yml
- type: Hosts
  url: hosts/hotel-engine-hosts.yml
- type: IntegrationEdges
  url: integrations/hotel-engine-integration-edges.yml
- type: Vendors
  url: vendors/hotel-engine-vendors.yml
- type: Newsroom
  url: https://engine.com/press
- type: Plans
  url: plans/hotel-engine-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hotel-engine-rate-limits.yml
- type: Overlay
  url: overlays/hotel-engine-omni-partner-api-overlay.yaml
- type: License
  name: Apache-2.0
  url: https://github.com/engine-public/engine-partner-api/blob/main/LICENSE
- type: Website
  url: https://www.engine.com/
- type: DeveloperPortal
  url: https://omni.engine.com/
- type: Documentation
  url: https://engine-public.github.io/engine-partner-api/
- type: APIReference
  name: HTTP/JSON reference (Swagger UI)
  url: https://engine-public.github.io/engine-partner-api/swagger-ui/index.html
- type: APIReference
  name: gRPC reference
  url: https://engine-public.github.io/engine-partner-api/api/grpc/index.html
- type: GettingStarted
  url: https://engine-public.github.io/engine-partner-api/getting-started.html
- type: Support
  url: https://engine-public.github.io/engine-partner-api/support.html
- type: HelpCenter
  url: https://www.engine.com/faqs
- type: Blog
  url: https://www.engine.com/blog
- type: GitHubOrganization
  url: https://github.com/engine-public
- type: SourceCode
  url: https://github.com/engine-public/engine-partner-api
- type: Pricing
  url: https://www.engine.com/pricing
- type: SignUp
  url: https://www.engine.com/sign-up
- type: TermsOfService
  url: https://www.engine.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.engine.com/privacy-policy
- type: ChangeLog
  url: https://github.com/engine-public/engine-partner-api/releases
- type: ChangeLog
  name: Structured changelog
  url: changelog/hotel-engine-changelog.yml
- type: Deprecation
  url: https://engine-public.github.io/engine-partner-api/versioning.html#support-for-deprecated-versions
- type: Lifecycle
  url: lifecycle/hotel-engine-lifecycle.yml
- type: Security
  url: https://www.engine.com/responsible-disclosure
- type: VulnerabilityDisclosure
  url: security/hotel-engine-vulnerability-disclosure.yml
- type: TrustCenter
  url: https://trust.engine.com/
- type: Compliance
  url: security/hotel-engine-trust-center.yml
- type: Conformance
  url: conformance/hotel-engine-conformance.yml
- type: Packages
  url: packages/hotel-engine-packages.yml
- type: SDKs
  url: packages/hotel-engine-packages.yml
- type: Sandbox
  url: sandbox/hotel-engine-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/hotel-engine-llms.txt
- type: AgenticAccess
  url: agentic-access/hotel-engine-agentic-access.yml
- type: DomainSecurity
  url: security/hotel-engine-domain-security.yml
apis:
- aid: hotel-engine:hotel-engine-catalogservice-api
  name: Engine Catalog Service API
  description: The CatalogService API from Engine — 1 operation(s) for catalogservice.
  humanURL: https://engine-public.github.io/engine-partner-api/
  baseURL: https://partner-api.engine.com
  tags:
  - CatalogService
  properties:
  - type: OpenAPI
    url: openapi/hotel-engine-catalogservice-api-openapi.yml
  - type: Protobuf
    url: grpc/_index.yml
  - type: Authentication
    url: authentication/hotel-engine-authentication.yml
  - type: Conventions
    url: conventions/hotel-engine-conventions.yml
  - type: ErrorCatalog
    url: errors/hotel-engine-problem-types.yml
  - type: DataModel
    url: data-model/hotel-engine-data-model.yml
  - type: RateLimits
    url: rate-limits/hotel-engine-rate-limits.yml
  - type: X-MCPServerCandidate
    url: mcp/hotel-engine-mcp.yml
    note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list
      derived from the published API contracts, not an existing server. The scorer already read the manifest and reported
      mcp_server correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
  - type: Documentation
    url: https://engine-public.github.io/engine-partner-api/
  - type: APIReference
    url: https://engine-public.github.io/engine-partner-api/swagger-ui/index.html
  - type: GettingStarted
    url: https://engine-public.github.io/engine-partner-api/getting-started.html
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-list-property-catalog-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-list-property-catalog-request-schema.json
- aid: hotel-engine:hotel-engine-lodgingbookingservice-api
  name: Engine Lodging Booking Service API
  description: The LodgingBookingService API from Engine — 5 operation(s) for lodgingbookingservice.
  humanURL: https://engine-public.github.io/engine-partner-api/
  baseURL: https://partner-api.engine.com
  tags:
  - LodgingBookingService
  properties:
  - type: OpenAPI
    url: openapi/hotel-engine-lodgingbookingservice-api-openapi.yml
  - type: Protobuf
    url: grpc/_index.yml
  - type: Authentication
    url: authentication/hotel-engine-authentication.yml
  - type: Conventions
    url: conventions/hotel-engine-conventions.yml
  - type: ErrorCatalog
    url: errors/hotel-engine-problem-types.yml
  - type: DataModel
    url: data-model/hotel-engine-data-model.yml
  - type: RateLimits
    url: rate-limits/hotel-engine-rate-limits.yml
  - type: Documentation
    url: https://engine-public.github.io/engine-partner-api/
  - type: APIReference
    url: https://engine-public.github.io/engine-partner-api/swagger-ui/index.html
  - type: GettingStarted
    url: https://engine-public.github.io/engine-partner-api/getting-started.html
  - type: JSONSchema
    url: json-schema/hotel-engine-api-http-body-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-book-request-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-confirm-offer-request-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-preview-cancellation-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-confirm-offer-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-get-bookings-request-schema.json
- aid: hotel-engine:hotel-engine-lodgingshoppingservice-api
  name: Engine Lodging Shopping Service API
  description: The LodgingShoppingService API from Engine — 2 operation(s) for lodgingshoppingservice.
  humanURL: https://engine-public.github.io/engine-partner-api/
  baseURL: https://partner-api.engine.com
  tags:
  - LodgingShoppingService
  properties:
  - type: OpenAPI
    url: openapi/hotel-engine-lodgingshoppingservice-api-openapi.yml
  - type: Protobuf
    url: grpc/_index.yml
  - type: Authentication
    url: authentication/hotel-engine-authentication.yml
  - type: Conventions
    url: conventions/hotel-engine-conventions.yml
  - type: ErrorCatalog
    url: errors/hotel-engine-problem-types.yml
  - type: DataModel
    url: data-model/hotel-engine-data-model.yml
  - type: RateLimits
    url: rate-limits/hotel-engine-rate-limits.yml
  - type: Documentation
    url: https://engine-public.github.io/engine-partner-api/
  - type: APIReference
    url: https://engine-public.github.io/engine-partner-api/swagger-ui/index.html
  - type: GettingStarted
    url: https://engine-public.github.io/engine-partner-api/getting-started.html
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-find-best-offers-request-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-find-availability-request-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-find-availability-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-find-best-offers-response-schema.json
- aid: hotel-engine:hotel-engine-content-service-api
  name: Engine Content Service API
  description: The Content Service API from Engine — 2 operation(s) for content service.
  humanURL: https://engine-public.github.io/engine-partner-api/
  baseURL: https://partner-api.engine.com
  tags:
  - Content Service
  properties:
  - type: OpenAPI
    url: openapi/hotel-engine-content-service-api-openapi.yml
  - type: Protobuf
    url: grpc/_index.yml
  - type: Authentication
    url: authentication/hotel-engine-authentication.yml
  - type: Conventions
    url: conventions/hotel-engine-conventions.yml
  - type: ErrorCatalog
    url: errors/hotel-engine-problem-types.yml
  - type: DataModel
    url: data-model/hotel-engine-data-model.yml
  - type: RateLimits
    url: rate-limits/hotel-engine-rate-limits.yml
  - type: Documentation
    url: https://engine-public.github.io/engine-partner-api/
  - type: APIReference
    url: https://engine-public.github.io/engine-partner-api/swagger-ui/index.html
  - type: GettingStarted
    url: https://engine-public.github.io/engine-partner-api/getting-started.html
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-list-properties-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-get-properties-response-schema.json
  - type: JSONSchema
    url: json-schema/hotel-engine-v1-get-properties-request-schema.json
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 74
  pass: local-v1

Engine API — frequently asked questions

Does Engine have an API?

Yes. APIs.io lists 4 APIs from Engine, including Engine Catalog Service API, Engine Lodging Booking Service API and Engine Lodging Shopping Service API, and 1 more.

Is there an OpenAPI specification for the Engine API?

Yes. APIs.io indexes 4 OpenAPI specifications for Engine, each linked for download from this page.

How do I authenticate with the Engine API?

Engine uses bearer-token authentication (mutualTLS · 1 scheme). The details are profiled on APIs.io as Hotel Engine Authentication.

How much does the Engine API cost?

Engine publishes its prices; its Engine plan is Engine is free. Not a free trial. Actually free. as of 2026-10-28. APIs.io lists 1 pricing plan for Engine, with each plan's price, limits and inclusions under Pricing on this page.

Is the Engine API ready for AI agents?

Engine has a Kin Score of 62.9 out of 100 (strong) and an Agent Readiness score of 27.2 (agent-aware), scored by API Evangelist on 2026-11-06.

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

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