Next step
Agentic AI for hotels
A live walkthrough mapped to how you operate — not a generic pitch.
Book a demoField notes
Stay on the operator brief.
Hospitality and Agentic AI updates — no sales sequences.
Agentic AI for hotels
Marketplace
NISKA Marketplace is how hotels and vendors attach the stack around Agentic AI HMS — distribution, payments, locks, messaging, accounting, and more — through APIs and events, with a human confirm before high-impact writes go live.
Why this desk
Enterprise hospitality marketplaces often catalogue hundreds of turnkey connects. We respect that model. We will not invent a 350-partner count or paste vendor marks we have not shipped. This page publishes the lanes we are building toward, the connect surfaces that matter on an Indian property, and how partners attach without a second property truth.
Connect model
Same rails the hotel OS already uses — no side-door database shares.
Synchronous business actions — check-in posts, payment captures, lock unlocks — call owned service APIs with tenant and property scope.
Cross-module updates fan out as events. Partners consume projections; PMS, revenue, and finance stay source of truth.
Non-CM partners, gateways, locks, accounting, and webhooks land through the hub — adapters, not shared write DBs.
Agents may draft and recommend. High-impact writes — rates, guest PII, money — stay behind operator confirm until policy says otherwise.
Software & hardware lanes
Twelve hospitality categories — the same shape operators expect from a marketplace — with honest status. Partner marks publish when a connect is live.
Priority
Channel managers, OTA/GDS mapping, ARI sync, and booking-engine handoffs — inventory and rates stay one book.
Priority
Deposit, folio settle, and gateway rails that post cleanly to the guest folio without a shadow ledger.
Priority
WhatsApp-first and omnichannel guest paths that sit on the same reservation and profile record agents already use.
Building
Exports, e-invoice, and GST compliance for India-first desks — finance owns posting; partners consume exports.
Open for partners
Door and access systems that encode or revoke keys from reservation state — never from a disconnected spreadsheet.
Building
Review ingest and response workflows tied to stay truth — agents draft; operators confirm before publish.
Building
RMS, rate shop, and restriction partners that recommend against canonical ARI — confirm before live sell rates move.
Open for partners
Profiles, consent, and loyalty that extend Guest / CRM — campaigns stay permissioned to property scope.
Open for partners
Check-in identity capture that writes into the guest record with audit — not a USB island at the desk.
Open for partners
In-room controls, IPTV, and guest Wi-Fi that can key off stay status without inventing a second occupancy truth.
Open for partners
Group blocks, banquet, and proposal tools that respect inventory owned by PMS — not a parallel book.
Open for partners
Tax, tourism authority, and regional compliance interfaces — listed when we can name the market and the owner.
For hotels
Connects project onto the property model. Channels do not invent a second inventory or folio.
Each lane shows Priority, Building, or Open — so you know what is live versus inviting partners.
Agents and connectors can draft. Money, rates, and guest-impacting writes stay confirm-gated by default.
For vendors
If you build channel, payments, locks, messaging, accounting, or adjacent hospitality software, we want a clear surface — OpenAPI or events — and a named owner on both sides. No DB shares. No logo-for-logo theatre.
How listing works
Reach the desk
Email hello@niskagroup.com with Marketplace in the subject. Include your product, category, markets, and whether you are an operator or a vendor.
