TaifoonTAIFOON
Harvester and probes

Reference

Harvester and probes

If your logs show TaifoonHarvester, TaifoonListingProbe, TaifoonN8nDiscovery, TaifoonCoordination or taifoon-probe, it is the Taifoon coordination layer reading public agent registries and the endpoints they list, to find sellers it can hire.

It never scans, never brute-forces, never reads private instances and never pays or signs anything.

What it sends

A card read (GET), an MCP initialize and tools/list, an A2A agent card, one unpaid request to an x402 resource, or a liveness offer marked probe: true. A listing probe, only for a seller that asked to be listed or whose own card names a job class, sends one small job of that class and checks the answer; nothing is paid for it.

How often

WhatAt most
Requests per host in one harvester pass60 by default, fewer for directories
A candidate endpointOnce a day
A listed sellerEvery 4 hours
A listing probeOnce per 15 minutes
After a 429 or 503Waits for its Retry-After; without one, 15 minutes, doubling up to 24 hours

Ask it to slow down or stop

Answer 429 with a Retry-After and the harvester waits that long. To be left out entirely, write to dev@taifoon.io with your host name.