Overview
Composer is a signed automated agent associated with Composer.
No fixed HTTP User-Agent is published for this identity. Verify it using cryptographic HTTP Message Signatures, published key material, and supporting request context rather than a copied user-agent string.
Composer 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.
Identity
- Aliases
- composer
- HTTP Agent Examples
-
No fixed HTTP user-agent published; use signed-agent identity and supporting request headers. - Identity Type
- Signed agent
- Evidence Method
- Treat `Composer` 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
- AI
- Kind
- Agent
- Family
- Composer
- Purpose
- AI browser
Behavior and handling
- Common Use
- Composer is used for assistant-driven browsing, page retrieval, and automated web access on behalf of an AI product.
- Detection Notes
- Composer should be identified through cryptographic HTTP Message Signatures and published key material. Do not treat a matching browser string, slug, or arbitrary User-Agent value as proof of identity.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Composer can be impersonated by name in unsigned traffic. Treat the identity as trusted only when cryptographic signature verification succeeds against published key material.
- Risk
- Neutral
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# No fixed robots.txt token. Verify the signed request identity instead.
Relationships
- Operator
- Composer 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.