Idempotency
“Idempotency keys for your anecdotes. Every story you tell gets hashed and tagged. When your uncle asks about the Frankfurt layover for the fourth time, we recognize the retry and return the cached response in 40 ms — without you having to move your face.”
The Problem
A conversation is a REST API where nobody implemented Idempotency-Key. Your dad hits POST /anecdotes/frankfurt at every dinner. You process it. Every time. The system has been up for 34 years and has never once returned a 304.
The Solution
We sit in front of your mouth. Every incoming request — “so did I tell you about…”— is normalized (embeddings, don’t worry about it), hashed, and looked up against the recipient’s Story Cache. Cache hit: we short-circuit with a warm “yeah you told me, the sandwich was crazy” in your own voice. Cache miss: we let you cook.
last delivered: 3 days ago
TTL: forever
Cache Hit Rate by Relationship
Six months of beta data. Bars are hit rate — higher means we spared them more repeats.
Pricing
TAM
The Ask
$3M seed. All of it into the embeddings pipeline that can tell “the Frankfurt one” apart from “the OTHER Frankfurt one”. This is much harder than it sounds.
Series A pitch:“Stripe for stories. The 304 is the product.”