Ephemeral key-value store

Store a value with one curl.
Get it back with another.

setget is a tiny HTTP key-value store. No signup, no API keys, no SDK. Useful for scripts, CI jobs, and moving small bits of data between machines.

bash

$curl -d "hello world" https://setget.net/set/my-key

{"id": "my-key", "status": "ok"}

$curl https://setget.net/get/my-key

{"id": "my-key", "value": "hello world"}

8,551 active keys 10 requests/second per IP expires after 3 months idle

Read the docs Open web console

API

Four endpoints cover almost everything. Any HTTP client works.

Method	Path	Description
POST	`/set/key`	Store the request body (text or JSON) under `key`.
GET	`/get/key`	Return the stored value.
POST	`/set/key?password=secret`	Store a value that requires a password to read.
GET	`/get/key?password=secret`	Read a protected value. Returns `401` on a wrong password.

Custom TTLs, JSON detection, and the rest are in the docs.

Details

No accounts

No registration and no API keys. Your key name is the only identifier.

Any text

Plain text, JSON, or base64-encoded binary. The value is stored as-is.

Automatic expiry

Keys expire after 3 months without access (max 1 year).

Backed by Redis

Reads and writes typically complete in a few milliseconds.

Rate limits

10 requests/second per IP. When limited, check the Retry-After header.

Pick unguessable keys

Anyone who knows a key can read it. Use UUIDs or random strings for anything sensitive.

What people use it for

CI/CD handoffs

Pass build status, artifact URLs, or deploy flags between pipeline stages.

Cross-device sync

Move a config snippet or clipboard text between machines without a cloud account.

Games and prototypes

Store session tokens, server lists, or simple leaderboards during development.

Home automation

Share sensor readings and device state between scripts and microcontrollers.

Store a value with one curl.Get it back with another.

API