From e9549b91c91a1d85d959976e8f2f18365817c3e9 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 11 Feb 2026 06:27:12 +0000
Subject: [PATCH 1/2] Initial plan


From fc23a68812f7a0323a82ab5d7de109cb87c383f3 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Wed, 11 Feb 2026 06:29:18 +0000
Subject: [PATCH 2/2] docs(http): add output variables documentation for
 dependsOn checks

Co-authored-by: moshloop <1489660+moshloop@users.noreply.github.com>
---
 canary-checker/docs/reference/1-http.mdx | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/canary-checker/docs/reference/1-http.mdx b/canary-checker/docs/reference/1-http.mdx
index 43f21f9d..15269002 100644
--- a/canary-checker/docs/reference/1-http.mdx
+++ b/canary-checker/docs/reference/1-http.mdx
@@ -138,6 +138,27 @@ Eg: In the following spec, the var `db`, defined in `env`, is available as `{{.d
 </div>
 </details>
 
+### Referencing Outputs from Dependent Checks
+
+When using `dependsOn` to create dependencies between checks, you can access outputs from other checks by name. This enables <CommonLink to="request-chaining">request chaining</CommonLink> for multi-step workflows.
+
+| Variable | Description | Scheme |
+| -------- | ----------- | ------ |
+| `outputs.<checkName>.json` | Parsed JSON response body from the named check | `map[string]any` |
+| `outputs.<checkName>.code` | HTTP response status code from the named check | `int` |
+| `outputs.<checkName>.headers` | Response headers from the named check | `map[string][]string` |
+| `outputs.<checkName>.body` | Raw response body from the named check | `string` |
+
+<details summary="Example: Using outputs from dependent checks">
+
+<div>
+```yaml title="http-depends-on.yaml" file=<rootDir>/modules/canary-checker/fixtures/minimal/http_depends_on_pass.yaml
+```
+
+In this example, the `get-profile` check depends on the `login` check and uses the token from the login response via `$(.outputs.login.json.token)`.
+</div>
+</details>
+
 See <CommonLink to="gotemplate" anchor="escaping">Escaping variables</CommonLink>
 
 ## Metrics