Channel · AI agents
Your agent finds the experience. We book it.
Search is the easy part. What breaks an agent is supply that sits in no system, and a confirmation that depends on a person.
Today
What happens now
What isn't inventory can't be queried
The terms, the options and the real availability live in conversations, not behind an endpoint.
A shared calendar lies
Availability for an experience depends on context; it isn't a value you can read.
Without a close, the task is half done
An agent that finds but can't book has done half the job, and the user does the other half.
With Duxenia
What changes
What isn't inventory, made queryable
We ask the provider through whichever channel they use and return a structured answer.
The same flow every time
Request → options → choice → confirmation → voucher → the day. With statuses that tell the truth.
An actual close
Confirmation with the provider, payment and paperwork. Not a redirect somewhere else.
What's in it for you
Tasks that get finished, not left halfway.
We share the commission
Every booking your agent closes earns you your share.
Your product
The user stays inside your agent. We don't take them anywhere else.
Statuses you can program against
“Waiting on provider” and “no availability” are answers, not errors.
The flow is always the same, from the request to the day itself, and you always know where your request stands. See how it works, step by step.
Getting started
Through the channels you already use
Through the API: your agent sends us the request and gets back options, statuses and confirmation in a format it can read.
We handle the booking and the payment. We don't answer for the service.
The provider is the one delivering the experience. We don't refund what they don't refund, and their cancellation terms are visible before you book.