LIVE
listening to the wire…
// simple, ephemeral key-value storage

Put stuff in.
Get stuff out.

No signups. No API keys. No SDK required. Standard HTTP you can call from anywhere.

active keys right now.
ephemeral and unindexed.
you@setget:~ live terminal. type help for commands.

Demo keys get a demo- prefix and die in an hour. Do not store sensitive production data here.

The entire API

all standard HTTP methods.
POST /set/key Store the body. Text or JSON. ?ttl=10m ?password= ?burn=true
GET /get/key Retrieve the stored value by key.
POST /incr/key  /decr/key Atomic increment and decrement with sub-millisecond response times.
GET /poll/key Long-polling key listener. Blocks until the value updates or times out.
GET /badge/key Dynamic SVG badge for repository READMEs and dashboards.
# quickstart
curl -d "deploy ok" https://setget.net/set/build-4812
curl https://setget.net/get/build-4812
curl -X POST https://setget.net/incr/visitors
curl "https://setget.net/poll/build-4812?timeout=30"

Fine print

how it works.

No accounts

Your key acts as the identifier. No credentials required unless you set ?password=.

Keys die

3 months without a read and they're deleted. Want it sooner? ?ttl=10m.

Burn after reading

?burn=true. The value is permanently deleted after the first read.

Rate limits

10 requests/second per IP. Requests exceeding limits return 429 Too Many Requests with Retry-After.

It's public

Keys without a password parameter are publicly accessible. Use UUIDs or secure tokens for private data.

It's fast

In-memory caching layer backed by persistent storage for low-latency operations.

Need code examples, client libraries, or advanced parameters? View full documentation →