Overview
Potions is an ecommerce crawler used for product discovery, catalog checks, marketplace crawling, price monitoring, and merchant data review.
Its primary user-agent pattern is Potions; related patterns include Potions/; a representative HTTP user-agent is Potions/1.0.0.
Potions is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
Potions can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
Potions - Aliases
- Potions/
- HTTP Agent Examples
-
Potions/1.0.0 - Robots Token
- Potions
- Identity Type
- Observed
- Evidence Method
- Treat `Potions` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Ecommerce
- Kind
- Fetcher
- Family
- Potions
- Purpose
- Ecommerce
Behavior and handling
- Common Use
- Potions is used for product discovery, catalog checks, marketplace crawling, price monitoring, and merchant data review.
- Detection Notes
- Potions traffic is primarily detected by the `Potions` user-agent pattern; related patterns include `Potions/`; a representative HTTP user-agent is `Potions/1.0.0`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Potions has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Potions Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.