Platform status

View .md

Kismet’s Developer API and SDK are in account-scoped beta. The API is hosted at https://api.ksmt.app/v1, and the reference is published at developers.kismet.travel. Authorized collection administrators and developers can create TEST and LIVE installations in Kismet.

Choose an integration path

Surface	What you can use	Where to start
Developer API	Collection-scoped catalog and group reads, group availability and pricing, natural-language search, published content, calendars, fixture manifests, and branded guest accounts	API reference
TypeScript SDK	Typed clients and server/browser entry points for supported operations	SDK installation and exports
Developer MCP	Public recipes and validation; OAuth-based collection setup; API-key capability inspection and authorized telemetry tools	Connect and choose authentication
Managed Fixtures	Published WordPress plugin delivery and supported JavaScript embeds; checkout depends on the collection’s commerce setup	Installation targets and manifests
TEST booking requests	Sandbox reservation, guest journey, and telemetry behavior without charges or production reservations	Booking-request reference

Integration limits

Unpublished catalog previews require explicit approval. The source-pinned staging extension adds TEST-only views to group and room list/detail reads. Both the API deployment and installed SDK must support it; two independent approvals limit unpublished-room access. This is content preview, not dated availability or checkout. Preview setup and examples.
Access is scoped. An installation fixes the collection, TEST or LIVE environment, grants, and browser origins. Credential settings support issuance, inventory, last-used information, and revocation. Rotation uses an issue → verify → revoke workflow, not an automatic rotation service.
Group pricing does not yet provide a complete minimum. Current coverage is base-rate-only, so lowestStay remains null. Show Check availability; do not promote an observed estimate to a lowest qualifying stay price or a checkout quote. Pricing guide.
The SDK beta npm tag is not published. Use a source-pinned evaluation tarball and manifest; older npm tags do not provide the current candidate contract. SDK installation.
Developer API booking requests remain TEST-only. Kismet Checkout and reviewed partner checkouts are separate integrations, not LIVE versions of that operation. Kismet Checkout supports your own payment processor or Stripe and is designed to work with Agent Pay, which lets agents book directly with managers. Choose and test a checkout integration.
The public Fixture npm package is not published. This does not affect existing WordPress artifact delivery or supported embeds. Check the manifest and installation target before choosing a component.
Local fixtures are for development and testing. They are not evidence that your collection has live published data, semantic search coverage, or working checkout. Validate those behaviors against the intended environment before switching a site to live data.
MCP sign-in is builder access. It does not sign in your visitors or replace the site’s guest-account BFF. Authentication and access.

Support and compatibility

For beta access, installation, or integration help, contact [email protected]. Use the OpenAPI artifact, your installed SDK’s exports, and each Fixture’s manifest to check the contract your integration consumes.

The guides and generated Markdown twins describe the same supported paths. Use llms.txt to give coding agents the current documentation index.