Terms of Service
Krawlet depends on Kromer and Krawlet API. API keys are optional, but no-key requests have stricter ratelimits and fewer features.
By using Krawlet, you agree to these Terms.
Service scope and third parties
Krawlet is primarily a frontend for Kromer API data. Krawlet API provides app-specific features such as key management endpoints, public ender storage item requests, and transfer/helper services.
Kromer is a separate service. Kromer-side usage is governed by Kromer's own terms and privacy practices where available.
Keys, abuse prevention, and enforcement
- API key use is optional, but lower/stricter rate limits may apply without a key.
- Keep your key private and do not share it publicly.
- You are responsible for activity performed with your key.
Raw API keys are not stored in plaintext on the Krawlet API server; hashed key representations are stored.
- Do not abuse, overload, scrape, or disrupt Krawlet API infrastructure.
- Do not bypass authentication, tier limits, or abuse controls.
- Do not use the service for unlawful activity.
Abuse controls include rate limiting and IP abuse blocking.
We may suspend or restrict access for abuse, security issues, or policy violations.
Availability, liability, and updates
Services may change or be discontinued at any time. Terms may be updated at any time.
To the maximum extent permitted by law, Krawlet maintainers are not liable for indirect, incidental, consequential, special, or punitive damages.
You agree to indemnify maintainers for claims arising from misuse or violation of these Terms.
For questions, contact maintainers through the project repository/support channels.