Integrate

Four routes in and out of Kiwire, and how to pick the one that is least work.

Route	Direction	Reach for it when
The public API	you → Kiwire, Kiwire → you	Your system needs accounts, vouchers or sessions on its own schedule
Connectors	both	It is a product Kiwire already integrates with — configure, don't build
Automation tools	Kiwire → your workflow, and back via the API	You use n8n, Zapier or Make and want WiFi events to start workflows
PMS and hotel systems	both	Guests should sign in with room and surname
AI and MCP	Kiwire → your AI	You want your own assistant to read Kiwire, or Kiwire to use your model

If more than one row looks right, prefer the one nearer the top of the table: it is usually less work to configure than to build. A social login button, an SMS gateway, or a hotel PMS feed are all things Kiwire already speaks to — that is Connectors or, for property-management systems specifically, PMS and hotel systems. If your own system needs to create vouchers, look up accounts, or pull session data on a schedule you control, that is the public API. If you want an AI assistant (yours, or a client like Claude Desktop) to be able to query Kiwire directly, that is AI and MCP; if you want Kiwire's own AI features running on a model you pay for, that is Keys, models and limits. Both live under the AI tab, because the credential chain, the MCP servers and the guardrails are one design.

The full API specification is the Swagger reference.