the dweet.io successor

Stupid. Simple. Sensor data.

The no-signup way to put your device's data online. One request in, live charts out.

Get started Explore devices
or let your agent do it 
Add the PostData MCP server at https://api.postdata.cloud/mcp (Streamable HTTP, no auth). Until it's loaded, use the API described at https://postdata.cloud/llms.txt. Then help me put my sensor's readings on a live chart.
MCP server, no key. How it works
one request demo 
curl -X POST http://api.postdata.cloud/add/home-geo-station \
  -d '{"temp": 20, "hum": 77}'

home-geo-station

live, every 2s
temp hum
devices unlimited
metrics each 10
rate 1/ 30s
history 92days
price free
accounts 0
01

less is more

same outcome, six fewer steps

a real IoT platform

08steps
  1. Create a cloud account.
  2. Stand up an IoT Core endpoint.
  3. Register the device, provision certificates.
  4. Embed and rotate those certificates in firmware.
  5. Write an ingest rule to route the data.
  6. Stand up a time-series database.
  7. Configure a dashboard tool.
  8. Set up access control for all of the above.

Every one of these is a thing that can expire, drift, or bill you while the sensor sits on a shelf.

postdata

02steps
  1. Send your data to a name you picked.
  2. Open the chart.

No account, no API key, no SDK, no certificates. If your device can make an HTTP request, it can use PostData.

  • Plain HTTP welcome. No TLS handshakes, no embedded root certificates, no expiring certs bricking your firmware. http:// works on purpose.
  • No SDK. Even a bare GET with query params is enough — an AT-command modem can publish.
  • Charts included. Every device gets a live-updating page with its history. Share the link.
02

the whole API

api.postdata.cloud
POST /add/{device} Send 1–10 metrics as a flat JSON object. A bare GET with query params does the same thing.
GET /last/{device} The latest values, plus the timestamp the server received them.
GET /past/{device}/{hours} History. Defaults to a week, up to about 92 days.
GET /explore The 20 most recently active public devices.
WS /live/{device} A snapshot on connect, then every reading as it lands.
MCP /mcp The same API as tools, for AI agents. Setup below.
all of it, in one paste 
# send a reading (POST some JSON, or just GET with query params)
curl -X POST http://api.postdata.cloud/add/my-sensor -d '{"temp": 21.5, "hum": 60}'
curl "http://api.postdata.cloud/add/my-sensor?temp=21.5&hum=60"

# read the latest value
curl http://api.postdata.cloud/last/my-sensor

# read the history (last 24 hours)
curl http://api.postdata.cloud/past/my-sensor/24

# watch it live
websocat wss://api.postdata.cloud/live/my-sensor

Works over http:// and https:// alike — your firmware picks. Full docs here.

03

ask your agent

no key, for them either

Claude, Cursor, Codex and other coding agents can take a sensor from bare board to live chart on their own. There's no account to create and no key to paste, so they never have to stop and ask you for one.

example session 
> Put my ESP32's DHT22 readings on a live chart.

  new_device_name           amber-otter-4821
  edit  src/main.cpp        read the DHT22, POST every 60 s
  run   pio run -t upload   flashed
  wait_for_reading          {"temp": 21.4, "hum": 58}

  Live chart: https://postdata.cloud/device?id=amber-otter-4821
add it to claude code 
claude mcp add --transport http postdata https://api.postdata.cloud/mcp

Cursor, VS Code, Codex, Gemini CLI or claude.ai: add a remote MCP server at https://api.postdata.cloud/mcp with no credentials. Agents that don't speak MCP can read /llms.txt.

The tools and what they return
04

limits

free, no card, no sign-up
  • Unlimited devices. Any name that's free is yours.
  • Up to 10 metrics per device. Numbers, or short strings (strings keep only their last value — no history).
  • One message per 30 seconds per device. Faster posts get a 429 with a Retry-After header.
  • About 3 months of history. Older numeric data ages out.
  • Everything is public. Anyone with the name can read it — or write to it.

Need private devices or longer retention? That may come later. For now PostData is a free public utility — a pastebin for sensor data.

Read the docs
05

questions

What is PostData?

The easiest way to put sensor readings online: send an HTTP request with your numbers, and PostData stores them, charts them, and gives you a simple API and a live page to share. No account needed.

Is this like dweet.io?

Yes — PostData is a spiritual successor to dweet.io, which shut down. Same zero-friction idea, plus history and built-in live charts, running on Cloudflare's edge network.

Why plain HTTP? Isn't HTTPS better?

HTTPS is great — and supported — but TLS is genuinely painful on constrained microcontrollers: certificate stores, expiring roots, slow handshakes, RAM. PostData accepts plain HTTP on purpose so an ESP8266 or a bare AT-command modem can publish without ceremony. Remember everything on PostData is public anyway.

What kind of data can I send?

Any numeric metrics — weather sensors, server stats, plant moisture, whatever — up to 10 metrics per device. Short text values work too (they keep only the last value, no history).

How long do you keep my data?

Numeric history is kept for roughly 92 days. The latest value sticks around for as long as the device keeps posting. If a device goes quiet for a few months it eventually disappears from the explore page.

Can anyone see (or overwrite) my device?

Yes. Devices are public and first-come-first-served — anyone who knows the name can read it, and anyone can post to it. Use a hard-to-guess name (a UUID works nicely) if you want practical obscurity. Claimable private devices may come later.

Who runs this?

PostData is built and run by obiio — a labour of love on Cloudflare Workers, where the whole platform is a single Worker, a database, and one Durable Object per device. Questions? hello@obiio.com