Your first tool, end to end

Build post_status, a tool that opens an incident on a status page. Requires the daemon installed, Node 22.18+, and a Statuspage page ID and API key.

1. Start an app

mkdir statuspage && cd statuspage
npm init -y && npm pkg set type=module
npm install @wardrik/[email protected] zod

2. Write the tool

statuspage.ts

import { Wardrik } from "@wardrik/sdk";
import { z } from "zod";

const page = process.env.STATUSPAGE_PAGE_ID;
const key = process.env.STATUSPAGE_API_KEY;

const wardrik = new Wardrik({ name: "statuspage" });

wardrik.tool({
  name: "post_status",
  description: "Open an incident on the public status page, with its first update.",
  input: z.object({
    name: z.string().describe("The incident's title, as customers see it"),
    status: z.enum(["investigating", "identified", "monitoring", "resolved"]),
    body: z.string().describe("The first update, in plain words"),
  }),
  run: async (incident, { signal }) => {
    const response = await fetch(`https://api.statuspage.io/v1/pages/${page}/incidents`, {
      method: "POST",
      headers: { authorization: `OAuth ${key}`, "content-type": "application/json" },
      body: JSON.stringify({ incident }),
      signal,
    });
    if (!response.ok) throw new Error(`Statuspage answered ${response.status}`);

    const { id, shortlink } = await response.json();
    return { id, shortlink };
  },
});

const stop = new AbortController();
process.on("SIGTERM", () => stop.abort());
process.on("SIGINT", () => stop.abort());

await wardrik.work({ signal: stop.signal });

• It isn't readOnly, so every call needs approval unless a policy allows it.
• A thrown error fails the call. The model receives the error message.

3. Connect it

Allow the user default/@statuspage to serve tools to the org's agents:

~/.config/wardrik/config.yaml

roles:
  tools: {rules: [{verbs: [serve], kinds: [agent]}]}
bindings:
  - {org: default, role: tools, subjects: [user:default/@statuspage]}

systemctl --user restart wardrik
wardrik token create statuspage --subject user:default/@statuspage

export STATUSPAGE_PAGE_ID=... STATUSPAGE_API_KEY=...
WARDRIK_TOKEN=wdk_... node statuspage.ts

default is the org in config.yaml. The app opens no port, and the Statuspage key stays in the app.

4. Give an agent the tool

~/.config/wardrik/agents/status.md

---
description: Posts to the public status page when asked.
tools: [workers/*]
policy:
  ask:
    workers/post_status: This posts publicly on the status page.
---
You post incidents on the public status page. Write for customers, in plain words.

5. Try it

wardrik reload
wardrik ask status "Checkout is failing for some customers. Post that we're investigating."
wardrik approval ls

AGENT   CALL        TOOL                  WHY
status  call_7c2e…  workers__post_status  This posts publicly on the status page.

wardrik approval approve status call_7c2e…
wardrik approval deny status call_7c2e… --reason "We don't post until it's confirmed."

On approval, your app posts the incident and the agent receives the link.

6. Run it as a service

~/.config/systemd/user/statuspage.service

[Unit]
Description=Status page tools for Wardrik
After=wardrik.service

[Service]
WorkingDirectory=%h/statuspage
EnvironmentFile=%h/.config/statuspage.env
ExecStart=/usr/bin/node statuspage.ts
Restart=on-failure

[Install]
WantedBy=default.target

chmod 600 ~/.config/statuspage.env   # WARDRIK_TOKEN and the Statuspage keys
systemctl --user daemon-reload
systemctl --user enable --now statuspage

For other machines or containers, see Host your tools.