Bot documentation
zentureBot
zentureBot is the crawler zenture uses to check the public sources behind AI answers. This page lists its identity, how it verifies its requests and how to control its access.
How to recognise zentureBot.
- Bot name
- zentureBot
- Operator
- zenture
- Contact
- [email protected]
- Robots token
zentureBot
User-Agent1 line
Mozilla/5.0 (compatible; zentureBot/1.0; +https://www.zenture.app/bot)Block or allow it with robots.txt.
zentureBot reads your robots.txt before it fetches a page and honours what it finds there. Add a group for its token to change what it may access; changes apply from its next visit.
Block everywhere2 lines
User-agent: zentureBotDisallow: /
Allow, except one area3 lines
User-agent: zentureBotAllow: /Disallow: /private/Every request is signed.
zentureBot signs its requests with Web Bot Auth (HTTP Message Signatures, Ed25519). The public keys are published in a signed key directory, so you can verify that a request really comes from zenture.
- Active key
Vv4uv--vx1jv1eXXXmx6Mcls40QPuhgXLYJkvRjc1js- Standby key
u7sm-smimUaY5mcW3Wl287gQZq1qWYuwwDF6AHYZTts- Machine-readable profile
- https://www.zenture.app/bot.json
What it does, and what it never does.
- Public sources only. Fetches public HTTPS pages cited in an answer. It never logs in or reads private content.
- Honours robots.txt. Checks robots.txt before every fetch and follows the rules for zentureBot and for all crawlers.
- No challenge bypass. Does not solve CAPTCHAs or attempt to bypass bot challenges.
- Conservative rate. Backs off and cools down on 403 and 429 responses.
Questions or a problem with zentureBot? Write to [email protected].