An agent inside your own app.

Calendars, bookings, payments, files, settings. Your app can do all of it, through buttons and screens your customers have to learn. With the SDK they can ask instead.

Plain words as the interface

People say what they want. A job that took three screens becomes one sentence.

Nothing new to design

The agent is the interface. You describe a function once and the conversation is taken care of.

It combines things for you

Give it your calendar and your contacts and it can book lunch with Sarah, though you never wrote that.

Your code stays as it is

You add small wrappers around functions you already have. Your models and your logic do not change.

For each thing your app can do, you write a short description: its name, what it is for and what it needs. The SDK does the rest: showing the agent, carrying the conversation, calling your function and showing the result.

It scales. An app can offer a hundred functions without the agent losing its way, because you group them and the agent is shown the right group at the right moment.

People can talk to the agent in your app and hear it answer, with nothing extra for you to build.

It wears your app's colours and type, and a new look can reach people from a server, without a new release.

A customer taps Get Help in your app and reads you a six-digit code. You see their screen and can point at things on it. They sign in to nothing and install nothing.

With the SDK in a development build, an agent on your Mac can see your app on a real phone, press its buttons, type into it and read its logs. It is how Ripul itself is built.

We can work with your team to choose what your agent should do first, wrap those functions, and get a build in front of your testers.