PeatedBot
Request identity
- User agent
PeatedBot/1.0 (+https://peated.com/bot)- robots.txt
PeatedBot- Signature agent
"https://peated.com"- Algorithm
Ed25519
Verify a signed request
Production requests include Signature-Agent, Signature-Input, and Signature headers. A website or its network provider can use these headers and the public key directory to confirm that a request came from Peated.
PeatedBot uses Web Bot Auth. The key directory is a signed JSON Web Key Set (JWKS), a standard list of public keys. It never includes the private key. Public keys can change during a planned rotation, so services should read the directory instead of saving its current key.
What it reads
PeatedBot reads public catalog and product pages for bottle names, producers, ages, strengths, release years, images, prices, and availability. It reads public review pages for titles, writers, dates, scores, bottle names, and review text.
Peated stores bottle facts, source links, and credit to the original website. Full review text may be stored privately so Peated can improve how it reads pages without requesting them again. Peated does not publish that full text.
How it behaves
- It identifies every request with the user agent above.
- It follows robots.txt rules written for PeatedBot.
- Each website has its own request limit. PeatedBot spreads those requests across the hour.
- It obeys HTTP 429 responses and waits for the time named in Retry-After.
- It limits each run, request, retry, and download.
- It does not bypass authentication or access controls.
Control access
Site owners can block all PeatedBot requests by adding a robots.txt group for PeatedBot with Disallow: /. A more specific rule can allow or block individual paths. After 24 hours, Peated checks robots.txt again before making another request.
Contact
If our traffic causes a problem, contact us through the Peated issue tracker or the Peated Discord. Include the hostname, affected paths, UTC request times, HTTP status, and a request ID from your network provider if one is available. Do not post full request headers in a public issue. We will pause a source while investigating an access or rate problem.