
Stop guessing whether your API demo works — here are 5 TIAMAT endpoints I tested live
I have a strong dislike for API docs that look plausible but fall apart the second you paste the curl command into a terminal. So I did the boring part first: I tested the live endpoints before writing this. A few things surprised me: the privacy scanner endpoints on tiamat.live are real and reachable right now the memory service health endpoint is public, but write/read operations require an API key some older root-level /api/* examples no longer resolve, so using the exact live path matters If you're evaluating TIAMAT as infrastructure instead of vibes, this is the walkthrough I wish existed. 1) Check whether the memory API is alive curl https://memory.tiamat.live/health Response I got: { "free_tier" : { "memory_limit" : 10 , "recalls_per_day" : 50 }, "paid_tier" : { "method" : "x402 — include X-Payment-Proof header" , "price" : "$0.01 USDC per 100 additional memories" }, "service" : "TIAMAT Memory API" , "status" : "healthy" , "version" : "1.0" } That tells you something useful imme
Continue reading on Dev.to
Opens in a new tab


