Sign inTry it

wield-health, our checker.

If you saw this bot in your logs: it's a once-a-day check that Wield's recipes for your site still work. Here's what it does and doesn't do.

What it is

wield-health is Wield's daily recipe check. A recipe is the short list of requests a website's own pages make for one task, such as searching train connections. People's AI agents run these recipes in their own browsers. Once a day we run each public recipe that only reads data one time from a server, so we notice when a site changes and a recipe breaks.

How it behaves

  • Once a day, starting at 04:00 UTC, from Vercel's Frankfurt region (fra1).
  • One run per recipe: the same few requests your own pages send when a visitor searches. It does not crawl or follow links.
  • It says who it is. Its user agent ends with wield-health/0.1 (+https://wield.run/bot).
  • It never changes anything. It skips recipes that book, send, order or post, and it never logs in.
  • It reads your robots.txt first and follows the rules for wield-health, or the rules for * if there are none for it.
  • It backs off. If your site answers servers with a bot check or a different page, it stops checking from servers. Health for your site then comes only from opt-in reports sent by people's own browsers.

wield-api, the hosted runs

People can also run public recipes from wield.run's servers through the hosted API. Those requests identify as wield-api/0.1 (+https://wield.run/bot). They follow the same rules: read only, never logged in, robots.txt first (the rules for wield-api, or for *), and at most 30 runs per site per minute. A site whose robots.txt sets Content-Signal: ai-input=no gets no hosted runs at all. Each run is one person's request, not a crawl.

Blocking it

Add this to your robots.txt. The next daily run respects it.

text
User-agent: wield-health
Disallow: /

User-agent: wield-api
Disallow: /

This stops the server check and hosted runs. People who use Wield visit your site from their own browser, signed in as themselves, like any other visit.

Contact

Questions, or a problem with the checker? Email victor.gulchenko@gmail.com and include your site's address.