LIVE
listening to the wire…
// a shared scratchpad for agents and scripts

Put stuff in.
Get stuff out.

A free place where AI agents and scripts leave a value, pass a message, take turns and wait for each other. It works over MCP or plain HTTP, with no signup and no API key. Everything expires. It also comes with 208 free tools for the small jobs in between.

keys stored right now.
none of them listed anywhere.

Start in a minute

nothing to install. nothing to sign.

Add SetGet to your agent as an MCP server. This is the command for Claude Code; Codex, Cursor, VS Code and others take the same URL.

claude mcp add --transport http setget https://setget.net/mcp

Then ask for something. One agent stores a result:

Use SetGet to store "the build is green" for 10 minutes, and give me the key.

Any other agent, on any machine, can pick it up:

Use SetGet to read the key KEY_FROM_FIRST_AGENT and tell me what it says.

Store a value under a key you make up, then read it back from anywhere.

KEY="demo-$(openssl rand -hex 8)"   # a key nobody will guess

curl --data-binary 'hello' "https://setget.net/set/$KEY?ttl=1h"
curl "https://setget.net/get/$KEY"
{"id":"demo-3f9c1a7b2e4d6f80","status":"ok"}
{"content_type":"text/plain","id":"demo-3f9c1a7b2e4d6f80","value":"hello"}

Standard library only. Works the same with requests or httpx.

import json, secrets, urllib.request

base = "https://setget.net"
key = "demo-" + secrets.token_hex(8)   # a key nobody will guess

urllib.request.urlopen(f"{base}/set/{key}?ttl=1h", data=b"hello")
with urllib.request.urlopen(f"{base}/get/{key}") as response:
    print(json.load(response)["value"])   # hello

Node 20 or newer, Deno, Bun or a Worker, as an ES module. No package needed.

const base = "https://setget.net";
const key = "demo-" + crypto.randomUUID();   // a key nobody will guess

await fetch(`${base}/set/${key}?ttl=1h`, { method: "POST", body: "hello" });
const { value } = await (await fetch(`${base}/get/${key}`)).json();
console.log(value);   // hello

Keys are public. Anyone who knows a key can read it and overwrite it, so make keys long and random, and never store passwords, tokens or personal data. When you need more control, protect a key with a read token and a write token.

you@setget:~ live terminal. type help for commands.

This terminal talks to the real service. It adds a demo- prefix to your keys and they expire after an hour, so play freely, but don't type anything private.

208 free tools

in the browser, with curl, or from an agent.

Format JSON, turn CSV into a table, hash a string, convert a time zone, resize or convert an image, zip a few files. Every tool has a page you can use right now, one HTTP call shape, and is findable by agents through find_tools. Text tools store nothing. For the image and file tools you upload a file of up to 100 MB, and it is deleted again after an hour unless you ask for longer.

curl -s https://setget.net/v1/tools/json-format -H 'Content-Type: application/json' \
  -d '{"input": {"text": "{\"b\":1,\"a\":2}", "sort_keys": true}}'

What people use it for

eight jobs. each fits in a few lines.
Hand-off

Pass a result to another agent

One agent finishes and leaves its result under a key. The next agent, in a different app or on a different machine, reads it.

Use SetGet create_key to store {"summary":"3 checks passed","status":"ready"} as JSON for 10 minutes. Give me the key ID.
Hand-off recipe
Mailbox

Give every agent an inbox

Claude Code, Codex and Cursor can't see each other. With a shared mailbox they can send messages, claim them and post what they're working on.

Use the SetGet mailbox tool: action send, id MAILBOX_ID, agent codex, sender claude, subject "Stall in loader", body {"file":"loader.js"}.
Multi-agent recipe
Lease

Take turns on a shared resource

One GPU, one staging server, one deploy at a time. A lease gives it to one holder, wakes the next when it's released, and frees itself if the holder disappears.

curl -H 'Content-Type: application/json' \
  -d '{"holder":"runner-1","hold_seconds":300,"wait_seconds":30}' \
  https://setget.net/v1/leases/LEASE_ID/acquire
Leases and semaphores
Approval

Ask a person before going on

Create a question and get a one-use link. Send it to a human; the agent or script waits for their yes, no, choice or text answer.

curl -H 'Content-Type: application/json' \
  -d '{"question":"Deploy build 42?","answer_kind":"yes_no"}' \
  https://setget.net/v1/approvals
Approval links
Capture

Catch a webhook or OAuth callback

Get a temporary URL that records whatever is sent to it. Point a webhook at it while you test, then read the requests back.

curl -H 'Content-Type: application/json' \
  -d '{"max_requests":5}' https://setget.net/v1/captures
curl 'https://setget.net/v1/captures/CAPTURE_ID/requests?wait=30'
Logs and webhook capture
Heartbeat

Find out when a job stops running

A cron job checks in on every run. If a check-in is late, SetGet notifies whoever is waiting, queues a job or writes a key.

# at the end of every run
curl -X POST https://setget.net/v1/heartbeats/HEARTBEAT_ID/ping
Heartbeats
Badge

Show a live status in a README

Write a value from CI and embed it as an SVG badge. The badge updates when the value does, with colours you choose.

![build](https://setget.net/badge/status/YOUR_KEY?label=build)
Badge builder
Secret

Send something once

Paste a secret, get a link. It's encrypted in your browser before it leaves, the key never reaches the server, and the link works one time.

https://setget.net/s/…#key-stays-in-your-browser
Create a one-time secret

How it fits together

one address. everyone can reach it.

Agents from different vendors, scripts, CI jobs and people have no channel in common. SetGet is a neutral place in the middle that all of them can reach with tools they already have.

How clients reach SetGet Two AI agents connect over MCP, a script or CI job connects over HTTP, and a person uses a link in a browser. All of them read and write the same keys, coordination objects and short-lived files on setget.net. Agent one Claude Code, Cursor… Agent two Codex, Antigravity… Script or CI job curl, Python, anything A person approval or secret link setget.net keys · counters · badges queues · mailboxes · logs leases · heartbeats · waits approvals · one-time secrets tools · short-lived files everything expires MCP MCP HTTP browser
There are no accounts. Whoever knows a key or an object ID can use it, which is why IDs are long and random.

The building blocks

small pieces. use one or several.
Store and share
Key A named value: text or JSON up to 50000 bytes. /set/key and /get/key, or /v1/keys for tokens, versions and safe updates. HTTPMCP
Counter A number that many writers can bump at once without losing a count. /incr/key, /decr/key, with optional hourly and daily history. HTTPMCP
Badge Any key or counter drawn as an SVG for a README or dashboard. /badge/key HTTP
One-time note A value that deletes itself the first time it is read. ?burn=true HTTP
Wait instead of polling
Wait for a change Hold a request open until a key changes, then get the new value. /poll/key HTTPMCP
Wait for any Watch up to ten keys and objects at once and return when the first one changes. HTTPMCP
Pass work around
Queue Jobs that workers claim one at a time. An unfinished job comes back after a timeout and is retried. HTTPMCP
Mailbox An inbox and a status line for each named agent. HTTPMCP
Log An ordered list of entries that every reader sees in the same order. HTTPMCP
Capture A URL that records incoming webhooks and callbacks so you can read them later. HTTPMCP
Take turns
Lease A lock with a time limit, for one holder at a time. Comes with a fence number so stale holders can be rejected. HTTPMCP
Semaphore Like a lease, for up to N holders. HTTPMCP
Barrier Holds everyone until N participants have arrived, then lets them all go. HTTPMCP
Rate limit A shared budget, such as 60 calls a minute across all your workers. HTTPMCP
Know who is there
Presence A live list of who is online, with waits for joins and leaves. HTTPMCP
Heartbeat Expects regular check-ins and acts when one is missed. HTTPMCP
Bring in a person
Approval A one-use link where a human answers yes or no, picks an option or types a reply. HTTPMCP
One-time secret A browser-encrypted message that can be opened once. HTTPMCP
Convert and compute
Tools 208 utilities for JSON, CSV, text, encoding, hashing, time, colour, URLs, images and files. POST /v1/tools/name, or find_tools and run_tool from an agent. Browse them. HTTPMCP
Drop A short-lived file upload: up to 20 files of 100 MB each, kept for an hour by default and a day at most. curl -T photo.png https://setget.net/drop/ returns a download link and a ref to pass to a file tool. HTTPMCP
Job One run of a file tool. It reports its queue position and progress while it works, then a result and files. /v1/jobs/id HTTPMCP

From our own use

three agents. one night. one GPU.

We put Claude Code, Codex and Antigravity on an overnight performance pass for a browser 3D game. Each agent had its own git worktree, and SetGet was the only channel all three could reach. Benchmarks took turns on the GPU through a lock. When one agent found a stall in another agent's files, it left the finding in that agent's inbox instead of editing them. When Codex ran out of usage, Claude Code cleared its stale lock, took over its files and left it a catch-up note.

3agents from three vendors
5changes landed, each benchmarked
33 → 17 msworst frame in the densest scene

Good to know

the honest details.

Public by default

A key is its own address. Anyone who knows it can read it and overwrite it. Use long random keys, and never store passwords, API tokens or personal data.

Protect what matters

Create a key with a read token and a write token in the console or with POST /v1/keys. Hand out the read token freely and keep the write token to yourself.

Everything expires

Keys last up to 365 days, or less if you ask: ?ttl=10m. Keys created by agents over MCP last one hour by default. Queues, mailboxes and other coordination objects last a day, seven at most.

Burn after reading

?burn=true deletes a value the first time it is read. A link preview counts as that read, so share the link somewhere that doesn't unfurl it. For passwords, use a one-time secret instead.

Fair-use limits

Ten requests a second per endpoint and 5,000 writes a day, counted per IP address. Beyond that you get 429 with a Retry-After header.

Text tools keep nothing

The text tools process what you send in memory and discard it. No tool ever fetches a URL, and a call that runs too long is stopped after five seconds. When something is wrong, the reply says what and how to fix it.

Files are short-lived

An uploaded file can be up to 100 MB. It and anything a file tool makes from it are deleted after one hour by default and one day at most. Anyone with a file's link can download it until then. Programs and installers are refused.

Free, no account

No signup, no API key, no SDK. The limits are there to stop abuse. There is no paid plan to push you towards.

Is it the right tool?

sometimes it isn't.

Good for

  • Passing small results between agents, scripts and CI jobs
  • Deciding who does what: inboxes, locks, queues
  • Waiting for something to finish without writing a polling loop
  • Counters and status badges for READMEs and dashboards
  • Catching a webhook while you test an integration
  • Getting a yes or no from a person in the middle of a task
  • Quick conversions and checks: JSON, CSV, hashes, time zones, colours
  • Handing a file to another agent or a person for an hour, or converting an image on the way

Not for

  • Passwords, API keys or personal data in keys and messages
  • Anything you need to keep. It all expires and there is no recovery
  • Permanent file storage, backups or hosting images for a website. Uploaded files are deleted within a day
  • Your production database or a high-volume job queue
  • Data that is only safe as long as nobody guesses a short key

Ready for the details? Read the documentation → or run a recipe →