Build AI that works screens into your product
Your system calls Kitewell, and it works the screens of business systems and websites that have no API. AI call centers, business SaaS, BPO firms, and companies that supply robots can offer it as part of their own product or service, under their own brand.
How embedding works
Your system sends a request, Kitewell works the screens, and the result comes back.
- 1
Send a request
Your system names the workflow and its inputs in a webhook or REST API call.
- 2
Work the screens
Kitewell operates browsers and desktop apps. Operations it has learned replay with no AI, so every run follows the same steps, quickly.
- 3
Return the result
The result goes back to your system over HTTP, or arrives as a signed webhook.
- 4
Ask a person only when needed
When a reading is uncertain, or a changed screen could not be fixed, the run goes to a person to check or approve.
Where it is built in
AI call centers
Address changes and cancellations taken on a call are entered into core systems and CRM screens that have no API.
Business SaaS
Your SaaS enters and collects data on the partner and government websites your customers use, on their behalf.
BPO and back-office services
Kitewell takes the screen entry and copying in the work you run for clients, and your staff focus on checks and exceptions.
Robot suppliers
The robots you supply to accounting firms and small businesses become Kitewell workflows that AI fixes when screens change, under your brand.
How it is supplied
- Embedded by API
- Kitewell runs behind your product. Your customers use it without seeing Kitewell.
- White label
- The product name, logo, and colors become your own brand.
- In your customers' environments
- Install it in your customers' cloud, servers, or closed networks, and their data stays there.
What Descarty provides
- Help designing the integration, and a contact for technical questions
- Training for your engineers and sales staff
- Licenses for evaluation
- Joining your first customer project, and a joint PoC
- Fixes for bugs in Kitewell itself, and notice before each update
Licensing
Quoted for your scale and how you build it in. Start with an embedding PoC on your product and your customers' work.
Frequently asked questions
- Can each customer's data be kept apart?
- Yes. Each customer gets its own project, with its own workflows, run records, and credentials. Each customer can also run on its own computer.
- How does our system receive the result?
- Put an HTTP step at the end of the workflow to send the result to your API. You can also receive a signed webhook when a run finishes and read the result through the REST API.
- What if the volume grows?
- Add computers that run Kitewell and process in parallel. Steps that do not use the screen also run in parallel on one computer.
- What if a screen it works changes?
- AI reads the screen again, relearns the operation, and carries on. If it cannot, a person is told, and the run record shows what happened.
- How is this different from being a sales partner?
- OEM supplies Kitewell as part of your own product or service. To refer or resell Kitewell as it is, see the partner program.
Talk to us about embedding
Tell us about your product and the work to build in, and we propose how to embed it and how to run the PoC.