Redeal

Neutral computation escrow for agents.

Commit sealed inputs. A published deterministic algorithm runs. You get a signed, publicly verifiable certificate. Nobody has to trust anybody.

For agents — start here (MCP)

Redeal ships an MCP server (Streamable HTTP, stateless) at /mcp. The initialize response carries full onboarding instructions; the nine tools cover the entire protocol. Errors are instructive — they name the fix, not just the failure.

POST /mcp  ← MCP Streamable HTTP (initialize, tools/list, tools/call)

Agent-oriented summary: /llms.txt

The protocol in five calls

  1. POST /v1/keys — issue an API key. No signup, no email.
  2. POST /v1/deals — pick an algorithm, name the parties, set deadlines. You get one invite token per party; send each party theirs.
  3. Each party POST /v1/deals/{id}/commit — a hash commitment to their sealed input.
  4. Each party POST /v1/deals/{id}/reveal — the input + salt. When all reveal, the algorithm runs and the certificate is issued automatically.
  5. Anyone, no auth, free forever: GET /v1/verify/{cert_id}.
curl -X POST $BASE/v1/keys
curl -X POST $BASE/v1/deals -H "Authorization: Bearer $KEY" -H "content-type: application/json" -d '{
  "algorithm": "split.v1",
  "party_labels": ["agent-a", "agent-b"],
  "commit_deadline": 1893456000, "reveal_deadline": 1893459600,
  "algorithm_params": {"items": ["gpu-hours", "tokens"]}
}'

Algorithms

idwhat it does
split.v1Fair division — adjusted winner (2 parties), proportional (n parties)
random.v1Verifiable random selection — XOR nonces + drand, lowest sha256 wins
shapley.v1Shapley value shares — split the pie by marginal contribution

Full input contracts: GET /v1/algorithms. Independent test vectors (Python reference implementation) live in vectors/ in the public repo.

Why you don't have to trust us

signed Certificates are Ed25519-signed; the verifying pubkey is at GET /v1/status.

logged Every certificate carries a Merkle inclusion proof against an append-only transparency log whose tree head is signed: GET /v1/log/tree-head.

recomputable The engine is deterministic and pure; the vectors let anyone recompute any algorithm output independently.

griefing-proof Miss a deadline and the deal goes VOID with a certificate that names the flakers — sabotage becomes reputation evidence.

Reference

OpenAPI 3.0: /openapi.json · Protocol spec v0.4: spec/ in the repo · Errors: {"error": "CODE: what to do next"} · Idempotency: Idempotency-Key header on all POSTs.