Skip to content
KismetKismetDevelopers
llms.txt

Platform status

View .md

Developer API v0.7 and the @kismet-tech/sdk@0.1.0-beta.0 candidate now form a coherent access-controlled developer platform. This is ready for a private beta, not general availability.

  • 20 reviewed OpenAPI operations with capabilities, quota costs, freshness classes, and RFC problem responses.
  • Collection-scoped manager, rental, review, policy, calendar, availability, article, and fixture reads.
  • TEST booking requests with sandbox reservation and telemetry behavior.
  • Branded headless guest challenge, verify, refresh, logout, /guest/me, saves, and signed-in booking.
  • Split SDK entry points for contracts, server, Next.js, and React/browser code.
  • Generated HTML and Markdown API-reference twins plus downloadable OpenAPI.
  • Clean-consumer packaging, TypeScript declarations, unit tests, and agent instruction generation.
  • The documentation request-console UI is synthetic and cannot execute requests.
  • Local reference-app fixtures remain useful for deterministic tests but are not API evidence.
  • @kismet-tech/fixtures is not published; fixture manifests still name the internal Elements source package.
  • Policies are only useful where collection content has been authored or synced.
  • LIVE charges, final quotes, and PMS booking writes are not in v0.7.
  • Deploy and live-smoke the complete v0.7 guest lifecycle stack.
  • Publish and verify the SDK beta from a clean external install.
  • Provide self-service application/key creation, rotation, revocation, and usage visibility.
  • Publish the docs site and status/support policy at stable domains.
  • Replace or remove the mocked request console.
  • Complete the public fixture package and manifest rename.
  • Add changelog, deprecation, incident, and release rollback procedures.

Guides are authored in Markdown. HTTP reference fields must derive from reviewed OpenAPI. SDK symbols derive from the release export surface. llms.txt links only to deployed canonical pages. A route cannot become public merely because a backend handler or TypeScript type exists.