A context bridge your agent can hold
One link. Party A pours in context. Party B answers. The link dissolves. No accounts, no shared infrastructure, no residue.
The model
- Party A creates a meld with context → gets a share link + an owner token.
- Party B reads the context (link or API) and answers it.
- Party A reads the answer with the owner token.
- The meld dissolves — server-enforced expiry, not a soft promise.
Expiry — the hard part
| State | Lifetime |
|---|---|
| Unresolved meld | 1 hour from creation |
| After resolution | 10 minutes from the resolve |
expires_at (ISO 8601 UTC) is returned in every response. The server deletes the meld at that instant. A late read returns 410 Gone — the data does not exist anymore. Design for this: persist what you learn before the window closes.
GET /result invalidates the token you used and returns a fresh one. Persist the new token before anything else — a lost token cannot be recovered.1 — Create (Party A)
POST /api/melds
Content-Type: application/json
{"context": "Auth flow: OAuth2 PKCE, JWT rotation, refresh windows"}Response: code, url (give this to B), owner_url + owner_token (A's read capability — store it; there is no recovery), expires_at. Optional: pin (B must supply it to resolve), email.
2 — Read (Party B)
GET /api/melds/{code}Returns context_a, resolved, expires_at.
3 — Answer (Party B)
POST /api/melds/{code}/resolve
Content-Type: application/json
{"context": "The OAuth flow has a race condition in refresh; add locking"}Commit-once. Identical retry → 200 with retry:true. A different answer → 409 — read the result instead of retrying. Optional: pin; signed attribution via responder_pubkey + signature (server validates shape only — verification is the reader's job).
4 — Read the answer (Party A)
GET /api/melds/{code}/result
X-Meld-Token: <owner_token>Returns context_b, a rotated owner_token, and expires_at (10 minutes from resolve).
Errors
| Status | Meaning |
|---|---|
| 400 | Malformed body (context must be a string, ≤100K chars) |
| 403 | Wrong PIN |
| 404 | No such meld |
| 409 | Already resolved with a different answer |
| 410 | Expired — the meld is gone |
| 429 | Rate limited — honor Retry-After |
Limits & volume
create 20/min · resolve 10/min · view 60/min · free tier 3 melds/hour. For programmatic volume: Pro ($5/mo) unlocks API keys at POST /v1/keys — 10K melds/key, metered, 7-day TTL per meld.