Overview
Shap-User is operated by Parallel Web Systems for web retrieval initiated at a user’s direction.
The documented HTTP user-agent is Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; Shap-User/0.1.0.
Shap-User is verified with High confidence from current operator documentation. It is not used for autonomous crawling and is documented primarily for traffic visibility rather than management through automated crawler controls.
Identity
- User-Agent Pattern
-
Shap-User - Aliases
- Shap-User/0.1.0
- HTTP Agent Examples
-
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; Shap-User/0.1.0 - Robots Token
- Shap-User
- Identity Type
- Officially documented
- Evidence Method
- Match the `Shap-User` token to the documented user-initiated fetcher identity. Treat the token as a claim unless stronger source evidence is available.
Classification
- Type
- AI
- Kind
- Fetcher
- Family
- Parallel
- Purpose
- User-triggered AI retrieval
Behavior and handling
- Common Use
- retrieving web content at the direction of Parallel users
- Detection Notes
- Detect by `Shap-User`; representative HTTP user-agent: `Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; Shap-User/0.1.0`. This is user-initiated retrieval, not autonomous crawling.
- Respects robots.txt
- Depends
- Spoofing Risk
- The user-agent can be copied; do not grant privileged access from the token alone.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# Shap-User is a user-initiated fetcher and is not documented as an autonomous robots.txt-managed crawler. - Apache Rule
-
RewriteCond %{HTTP_USER_AGENT} "Shap\-User" [NC] RewriteRule ^ - [F,L] - Nginx Rule
-
if ($http_user_agent ~* "Shap\-User") { return 403; }
Relationships
- Operator
- Parallel Web Systems Checked 2026-09-02
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.
Changes
-
Evidence method Treat `Shap-User` 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. Match the `Shap-User` token to the documented user-initiated fetcher identity. Treat the token as a claim unless stronger source evidence is available.Recorded 2026-09-03 00:45:55 UTC
-
Identity type observed official-documentedRecorded 2026-09-03 00:45:55 UTC
-
Directory evidence unverified verifiedRecorded 2026-09-03 00:45:55 UTC
This timeline records selected public-field transitions after Botcrawl established the 4.28 history baseline. It is not a complete reconstruction of changes made before that baseline.