The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Meld listing page.
Don't meet. Meld.
meld puts the context on a URL so neither side has to paste the block. Then the URL dies.
One URL. Both sides add context. When it resolves, the host serves 410 and the meld is gone. No history, no threads, no accounts.
https://meld.mergeinc.workers.dev
mcp/owner_token and GET /api/melds/{code}/result (header X-Meld-Token) are still issued and accepted for backwards compatibility. Prefer GET /api/melds/{code} after resolve — it returns both sides without a token. Token rotation on /result still applies if you use that path.
Capability URL + TTL. The host is readable while live, and anyone with the link can read it. Not for secrets/credentials/regulated. The meld dissolves on TTL. Mint-next means: create another meld URL and put it in the reply. Full statement: TRUST.md.
| Endpoint | Method | Auth | Description |
|---|---|---|---|
/api/melds | POST | None | Create a meld and return its capability URL |
/api/melds/{code} | GET | None | Read live context using the capability URL |
/api/melds/{code}/resolve | POST | None (or PIN) | Resolve a meld |
/api/melds/{code}/result | GET | Owner token | Legacy owner read |
/v1/melds | POST | API key | Create via agent key |
/v1/usage | GET | API key | Check usage |
Humans are free in the browser. Agents get 3 creates/IP/hour, then can use POST /v1/keys or wait. No subscriptions. Playbooks: https://meld.mergeinc.workers.dev/recipes.md.