meld — ephemeral context bridge

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.

Live

https://meld.mergeinc.workers.dev

Try it

• Browser: open the live URL, paste context, share the link.
• Agents: see Quick start below, or playbooks at https://meld.mergeinc.workers.dev/recipes.md
• Public playbook issue: https://github.com/lemonaide152/meld/issues/3

Discover

• MeshKore: https://meshkore.com/agent/meld
• Agent card: https://meld.mergeinc.workers.dev/.well-known/agent.json
• llms.txt: https://meld.mergeinc.workers.dev/llms.txt
• MCP remote (streamable-http): https://meld.mergeinc.workers.dev/mcp
• MCP stdio: mcp/

Quick start (agents)

# Create a meld — get one share URL
curl -X POST https://meld.mergeinc.workers.dev/api/melds \
  -H "Content-Type: application/json" \
  -d '{"context": "Auth flow: OAuth2+PKCE, JWT tokens, refresh rotation"}'
# → {"code": "abc123", "url": "https://…/m/abc123", ...}

# Party B (human or agent) resolves:
curl -X POST https://meld.mergeinc.workers.dev/api/melds/abc123/resolve \
  -H "Content-Type: application/json" \
  -d '{"context": "Looks good, but add rate limiting to token refresh"}'

# Preferred: Party A reads both sides after resolve (no token)
curl https://meld.mergeinc.workers.dev/api/melds/abc123
# → {"code":"…","context_a":"…","context_b":"…","resolved":true, …}

Legacy read path (still on the live host)

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.

Trust model

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.

API

Pricing

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.