The models your users already trust, with your app’s context built in
Answers come from each user’s real data in your app, so they get more out of it. It reads only what a question needs, when they ask. Boop doesn’t store your app’s data.
Cart
4 items
Fettuccine 16 oz
$2.49
Chicken Breast 1.5 lb
$8.99
Heavy Cream 16 oz
$3.79
Salted Butter 1 lb
$4.99
Subtotal
$20.26
It can change things in your app, like filling a cart or loading a workout. Nothing changes until the user taps Confirm.
Memory is kept separately for each app. Users can see everything it remembers and delete any of it anytime. Only the question and the app data needed to answer it go to the model.
One swipe opens an assistant that knows your app and each user’s history in it. No switching to a chatbot. No re-explaining.
Claude or GPT included for every user, no AI subscription needed. Tools and memory carry over when they switch.
Model
Your memory and this conversation carry over when you switch.
Two sample apps with made-up data, running the same Boop script.
Ledger is a budgeting app. Try “When will I hit my emergency fund goal?” or “Set my dining budget to $300”
Tap the tab on the right edge to open the assistant.
We’ll help with the rest.
Tools run in your app.
<script src="/rail.js"></script>
<script>
Rail.init({
appId: "your-app",
appName: "Your App",
user: { id: user.id, name: user.name },
getContext: () => ({ screen: currentScreen }),
tools: [
{
name: "getWorkoutHistory",
description: "Returns the user's logged workouts, newest first.",
inputSchema: {
type: "object",
properties: { weeks: { type: "number" } },
},
run: ({ weeks }) => workouts.recent(weeks),
},
{
name: "loadWorkout",
description: "Loads a planned session into today's workout.",
inputSchema: {
type: "object",
properties: { exercises: { type: "array" } },
required: ["exercises"],
},
requiresConfirmation: true,
run: ({ exercises }) => today.load(exercises),
},
],
});
</script>