public beta

the easiest way to pair any two clients.

three words whispered over voice, chat, or QR → both sides get a shared session. mishear a word? fuzzy matching handles it. no accounts, no infra to build.

✦ get started free see pricing
3 words → shared session 0 servers to build fuzzy matched
built for: ✓ webrtc signaling ✓ device pairing ✓ multiplayer game lobbies ✓ multi-agent systems ✓ temporary collaboration sessions
Why Talkie Sync

no infra to build. just the handshake.

🗣️

three words

share over voice, chat, or QR code. the other person doesn't need an account — they just get the session.

⚡

no websockets

we handle the connection layer. your app just posts and polls messages — long-polling built in.

🔒

no user accounts

only you need a project and API key. the other side is anonymous — they just need the words.

How it works

three words → shared session

1

create

hit the API with your project credentials. you get three random words and a session_id.

→
2

share

say "aardvark absurd acme" over a call, drop it in chat, or flash a QR code.

→
3

claim

the other party posts the same three words and gets the same session_id. now both sides share a secret.

→
4

talk

post and poll messages on the session channel. or use the session_id for WebRTC signaling — it's up to you.

⚠ Messages are stored as plaintext by default. For end-to-end encryption, consider using the shared session_id as an AES-256-GCM key via our client helpers — the server never has access to the key.

We provide encryptPayload() / decryptPayload() in the TypeScript client to do this automatically.

pair and messages expire together, cleaned by the sweeper.

What people build

any two parties need to find each other

🎮

game lobbies

pair two players into the same session. drop the words in discord — both join the same lobby, no friend list needed.

curl • js • unity
🎛

creative tool sync

sync session context between two DAWs or VJ instances. the shared session_id is your handshake for whatever protocol comes next.

curl • python • max/msp
📟

iot pairing

pair a phone to a device by scanning a QR code that reveals three words. no bluetooth menus, no wifi credentials to type.

http • embedded
📡

webrtc signaling

use the session channel to exchange SDP offers, answers, and ICE candidates for SimplePeer. no signaling server to deploy — the channel is your transport. recommended: Pro tier for lower latency on SDP/ICE exchanges.

simple-peer • webrtc • js
Cloud API

pay for convenience, not for pairs

no per-message fees, no hidden costs. the cloud option is for when you want zero ops. same API, same code, just someone else's problem.

Free

$0 / month
  • — projects
  • — channels
  • — pairs / day
  • — TTL
  • community support
get started

Creator

$5 / month
  • loading...
  • loading...
  • loading...
  • loading...
  • email support
subscribe

Pro

$12 / month
  • loading...
  • loading...
  • loading...
  • loading...
  • priority support
subscribe

everything includes the full api, fuzzy matching, and ssl. billing by Creem — no lock-in, cancel anytime.

The boring but important stuff

specs

endpoints POST /api/pair · POST/GET /api/pair/:ch/messages
auth Basic (project id + secret) · Bearer (JWT, HS256)
words pgp wordlist (512 words)
fuzzy match levenshtein ≤ 2
session 16-byte random id
expiry 1 hour (configurable)
edge cloudflare workers, global
encryption session exchange only. messages are plaintext by default
word storage hmac-sha256 lookup only
ephemeral cleaned by sweeper after TTL
client TypeScript SDK on npm
distribution cloud API
license mit
FAQ

questions? probably answered.

three words. one session.

three words. one session. your app.

✦ get started free

no credit card required.