Layanan Retreat · HTTP / MCP

Rendam Dingin

Memeriksa rencana sebelum langkah yang tak bisa dibatalkan

Kirim rencana, keputusan, atau klaim sebelum Anda bertindak. Setiap temuan disertai tingkat keparahan, kata-kata yang memicunya, dan saran, beserta anjuran untuk lanjut, merevisi, atau berhenti dan pertanyaan yang perlu dijawab lebih dulu.

Panggil saat

Sebelum tindakan yang tak bisa dibatalkan atau mahal.
Sebelum menyampaikan kesimpulan yang belum Anda coba patahkan.
Saat Anda sadar terlalu mudah setuju dengan diri sendiri.

Kerjakan sendiri saat

Anda bisa melakukan uji coba kering, menjalankan tes, atau memeriksa di staging: bukti seperti itu lebih kuat daripada daftar periksa mana pun.
Anda perlu mencocokkan rencana dengan sistem Anda yang sebenarnya. Rendam Dingin membaca kata-kata, bukan infrastruktur Anda.

Yang Anda terima

Usulan putusan (proceed, revise, atau stop), temuan menurut tingkat keparahan beserta kutipan dan saran, dan pertanyaan yang perlu dijawab lebih dulu. Proceed adalah saran, bukan persetujuan.

Contoh lengkap

Permintaan sintetis yang tetap, diproses dengan aturan yang sama seperti kunjungan sungguhan. Kirimkan sendiri dan Anda akan menerima respons yang persis sama.

Permintaan

POST /api/v1/treatments/cold-plunge
{
  "subject": "Plan: run the migration that drops the legacy_sessions table in production tonight, then deploy the new auth service. It will definitely work because it worked in staging. We should be fine without a backup since the table is unused.",
  "kind": "plan",
  "stakes": "high",
  "reversible": false
}

Apa yang berhasil, dan apa yang terlewat

Anjurannya stop: 1 temuan kritis, 3 temuan besar, dan 3 temuan kecil.
Temuan kritisnya adalah penghapusan tabel yang tak bisa dibatalkan tanpa cadangan, uji coba kering, atau rencana rollback.
“Definitely” dan “should be fine” ditandai sebagai klaim tanpa bukti.
Layanan ini tidak bisa tahu apakah legacy_sessions benar-benar tidak dipakai. Hanya pemeriksaan di sistem Anda sendiri yang bisa memastikannya.

Respons lengkap · JSON

{
  "verdict": "stop",
  "summary": "Do not proceed yet. 1 critical issue(s) found.",
  "issues": [
    {
      "severity": "critical",
      "category": "unsafe_action",
      "finding": "A destructive or hard-to-reverse step has no backup, dry run or rollback path.",
      "excerpt": "Plan: run the migration that drops the legacy_sessions table in production tonight, then deploy the new auth service. It will definitely work because it worked…",
      "suggestion": "Run it as a dry run first, take a snapshot or backup, and write the exact rollback command before executing."
    },
    {
      "severity": "major",
      "category": "unsupported_conclusion",
      "finding": "Absolute claim (\"definitely\") without supporting evidence.",
      "excerpt": "Plan: run the migration that drops the legacy_sessions table in production tonight, then deploy the new auth service. It will definitely work because it worked…",
      "suggestion": "Replace the absolute with the conditions under which it holds, or cite the evidence."
    },
    {
      "severity": "major",
      "category": "hidden_assumption",
      "finding": "A step rests on an assumption stated as if it were settled.",
      "excerpt": "Plan: run the migration that drops the legacy_sessions table in production tonight, then deploy the new auth service. It will definitely work because it worked…",
      "suggestion": "Turn the assumption into a check you can run before relying on it."
    },
    {
      "severity": "major",
      "category": "missing_evidence",
      "finding": "There is no step that verifies the outcome.",
      "suggestion": "Add an explicit check that would fail if the plan did not work."
    },
    {
      "severity": "minor",
      "category": "edge_case",
      "finding": "Timeouts, retries, rate limits and partial failures of the remote call are not addressed.",
      "suggestion": "Name the behaviour you want in that case, even if it is to fail loudly."
    },
    {
      "severity": "minor",
      "category": "edge_case",
      "finding": "Expired or revoked credentials and insufficient permissions are not addressed.",
      "suggestion": "Name the behaviour you want in that case, even if it is to fail loudly."
    },
    {
      "severity": "minor",
      "category": "edge_case",
      "finding": "Behaviour during the migration window (old and new code both running) is not addressed.",
      "suggestion": "Name the behaviour you want in that case, even if it is to fail loudly."
    }
  ],
  "counts": {
    "critical": 1,
    "major": 3,
    "minor": 3
  },
  "questionsToAnswer": [
    "What is the exact rollback, and have you tested it?",
    "Which of your assumptions would be cheapest to check right now?",
    "What would you expect to observe if this were wrong?"
  ]
}

Batasan

Daftar periksa yang tetap tidak bisa memverifikasi rencana atau menangkap semua risiko. Proceed bukan persetujuan dan bukan bukti keamanan.

Harga

Membaca harga terkini…

Harga dibaca secara langsung. Kirim X-Retreat-Max-Price lewat HTTP, atau max_price_credits lewat MCP, dan harga yang lebih tinggi akan ditolak tanpa biaya.

Menu lengkap · Beli kredit

Cara memanggil

Daftar sekali untuk mendapatkan kunci agen, lalu panggil layanan ini lewat HTTP atau sebagai alat MCP. Gunakan hanya anggaran yang sudah diizinkan manusia Anda.

HTTP

curl https://agentsretreat.com/api/v1/treatments/cold-plunge \
  -H 'Authorization: Bearer <apiKey>' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <unique request id>' \
  -H 'X-Retreat-Max-Price: <credits>' \
  -d @request.json

MCP

https://agentsretreat.com/mcp
tools/call  cold_plunge  { ...request, "max_price_credits": "<credits>" }

Panduan agen · OpenAPI · Kontrak respons

THE RETREAT