Early access — now onboarding builders

Your chatbot, living as a contact.

Write a system prompt, pick a model, wire in MCP servers. We pin the agent to a real phone number, keep conversation state, and ship every outbound message as iMessage.

System prompt "You are the concierge for Café Lindo. You can reserve tables, answer menu questions, and never promise what the kitchen can't…"
MCP servers reservations menu payments
can I get a table for 2 tonight?
Done — 7:30pm under your number. Want the quiet back room? 🪑

By the numbers

A whole agent stack, condensed to a config.

1

Phone number per bot

Every agent gets its own line on Loki Messages. Users save the contact and just text.

3

Model providers

Anthropic, OpenAI, or open models on Workers AI — pick per bot, switch any time.

1:1

Runtime per conversation

Each thread runs in its own isolated runtime with durable state. No shared memory, no leaks.

0

Servers for you to run

Inference, tool calls, state, and delivery all run on our edge. You write the prompt.

The idea

The best interface for an agent is a contact card.

Feels human

Texting it should feel like texting a person.

Loki Chat agents speak fluent iMessage because they ride on Loki Messages. They type before they answer, react to good news, send voice memos, and put choices to a vote.

  • Typing indicators while the model thinks
  • Tapbacks, images, and native polls
  • Replies thread naturally in the conversation
  • Knows when to speak in group chats — and when not to
movie tonight? something fun
Three options near you 🎬 Dune 9:40, the new Pixar 8:15, or a midnight classic. Tapback your pick!
pixar!! 🍿
Two tickets, 8:15pm, row F. Sending the confirmation here ✅

Acts on the world

Tools via MCP, so your bot can actually do things.

Wire in MCP servers — from our catalog or your own endpoint — and the agent can search, book, order, and pay on the user's behalf. When a tool needs the user's account, the bot sends an OAuth link right in the thread.

  • Any MCP server: ours, yours, or third-party
  • Per-user OAuth handled in-conversation
  • Tool results come back as rich replies, not JSON dumps
  • Catalog providers for movies, food, golf, and fintech
Connected MCP servers fandango sweetgreen golfnow your-server
book me a tee time saturday am
I can book with your GolfNow account — tap to connect, takes 10 seconds: golf.lokimessages.com/auth/…
Connected ✅ Saturday 8:10am at Bethpage Red, $64. Book it?

Never loses the thread

Memory and follow-through, built in.

Each conversation runs in its own durable, isolated runtime. The bot remembers the thread without you wiring up storage — and it can schedule its own future messages, so follow-through doesn't depend on the user texting first.

  • Durable per-conversation state, no database to manage
  • Scheduled tasks — reminders, check-ins, nudges
  • Cost tracking and rate limiting per bot
  • Full conversation history at your fingertips
remind me thursday to renew the passport
Will do — Thursday 9am, right here. 📅
Scheduled · Thu 09:00 "Passport renewal day! The office on Marszałkowska opens at 10 — want the checklist?"

The platform

Everything between your prompt and the blue bubble.

Your prompt, your bot

A chatbot starts as a system prompt and a model choice. Write the personality and the rules; we run the inference loop.

Pick your model

Claude from Anthropic, GPT from OpenAI, or open models on Workers AI. Choose per bot to fit your latency and cost budget — switch without rewriting anything.

MCP-native tools

Wire in any MCP server — ours or yours — and the bot can book, search, order, and fetch on the user's behalf.

Per-user OAuth

When a tool needs the user's GolfNow or Sweetgreen account, the bot drops an auth link into the thread. Tokens are stored per user, scoped per provider.

A real phone number

Every bot is pinned to its own number on Loki Messages. Users add it as a contact and text it like a friend — no app to install.

Conversation memory

Each conversation runs in its own isolated runtime with durable state. The bot remembers the thread without you wiring up storage.

Scheduled follow-ups

Bots can schedule their own future messages — reminders, check-ins, and nudges that fire without an inbound trigger.

Group-chat aware

Add the bot to a group and it understands the room: it answers when addressed, stays quiet when it isn't, and never double-replies.

Guardrails & cost control

Per-bot rate limiting and cost tracking out of the box, so a chatty user can't surprise you on the invoice.

MCP catalog

Tools your bot can pick up on day one.

Fandango

Movies

Showtimes, theaters, and ticket deals. Your bot finds the 7pm screening and the discount in one turn.

showtimestheatersdeals

Sweetgreen

Food

Menu, custom bowls, rewards, and order-ahead. "The usual, 12:30" becomes a placed order.

menuorderrewards

GolfNow

Golf

Tee-time search and booking with the user's own account — OAuth and payment handled in the thread.

searchbookaccount

Super

Fintech

Account, cash advance, earnings, and gift cards — everyday money actions over text.

accountadvancegift cards

Bring your own

Custom

Point the bot at any MCP endpoint you run. Tools show up automatically — no plugin format, no review queue.

your serveryour tools

More coming

Catalog

The catalog grows where conversations want to go: dining, travel, tickets. Tell us what your bot needs.

request a provider

How it works

Three steps from idea to a number people can text.

Write the prompt

Define who the bot is, what it can promise, and where the lines are. Pick the model that fits your latency and cost budget.

Connect MCP servers

Choose from the catalog or point at your own MCP endpoint. Tools show up to the bot automatically, auth flows included.

Give it a number

We pin the bot to a phone number on Loki Messages. Share the contact — every text from a user becomes a conversation.

What people build

From "what if" to a contact card.

Finance

A money copilot

Connect accounts once, then ask anything: spending this week, the biggest expense, what's safe to spend. Answers in seconds, in the thread.

You spent $127 on food this week — 12% less than last. 📉

Hospitality

A restaurant concierge

Takes reservations, answers menu questions, and never promises what the kitchen can't. The host stand that answers at midnight.

Done — 7:30pm under your number. Want the quiet back room? 🪑

Food

An ordering assistant

Knows the menu, remembers the usual, surfaces the deals. From craving to confirmed order without opening an app.

Your usual bowl + the free-delivery deal. Order it? 👍

Commerce

A shop-and-pay agent

Browse products, check limits, manage payments — guided purchasing over text, with the catalog as a conversation.

AirPods Pro — $24.90/mo over 10 months. Add to cart?

Leisure

A weekend planner

Movies, tee times, tables — one bot with three MCP servers becomes the friend who always knows what's on.

Dune 9:40pm + ramen after. Want me to book both? 🎬

Yours

The one you're thinking of

If you can write the system prompt and stand up (or pick) the tools, Loki Chat turns it into a contact people text.

Hey! I'm live — text me anything to get started ✨

Beside, our consumer concierge, is a Loki Chat bot — same runtime, same MCP servers, same number-per-bot architecture we hand to you.

Loki Labs · Warsaw

FAQ

The questions everyone asks.

Do I need to host anything?

No. Inference, conversation state, scheduling, and message delivery all run on our infrastructure. You provide a system prompt and configuration — and optionally your own MCP server, hosted wherever you like.

Which models can my bot use?

Claude models from Anthropic, GPT models from OpenAI, and open models running on Cloudflare Workers AI. The model is a per-bot setting, so you can prototype cheap and ship premium — or the reverse.

How does the bot actually do things?

Through MCP — the open Model Context Protocol. Connect servers from our catalog (Fandango, Sweetgreen, GolfNow, Super) or any endpoint you run, and their tools become available to the bot's reasoning loop automatically.

What if a tool needs the user's account?

The bot sends an OAuth link directly in the conversation. The user taps, signs in with the provider, and comes back to the thread. Tokens are stored per user and per provider — one user's login never bleeds into another's.

Does it work in group chats?

Yes. The bot understands group dynamics: it responds when addressed or clearly useful, stays quiet otherwise, and coordinates so it never sends twice for one message.

Can the bot message first?

It can schedule its own future messages — reminders, check-ins, follow-ups — that fire without an inbound trigger. Proactive, but anchored to conversations users started.

How is this different from Loki Messages?

Loki Messages is the transport: a REST API for sending and receiving iMessage. Loki Chat is the managed agent on top — we run the model, the tools, and the memory, and use Loki Messages for delivery. If you want to build your own bot logic, use Messages; if you want a bot from a prompt, use Chat.

What does it cost?

Loki Chat is in early access and pricing is being shaped with early customers. Tell us what you're building and we'll set you up with a bot and a line.

Give your agent a phone number.

Loki Chat is in early access. Tell us what you're building and we'll set you up with a bot and a line.