existAPI terms

By requesting an API key or calling existAPI, you accept these terms in addition to the terms of use and the privacy notice.

existAPI exposes the moderated bot directory as JSON. Public read endpoints need no key. Authenticated endpoints let you manage your own applications, keys and submissions.

The API is versioned under /api/v1. Additive changes can happen without a version bump. Breaking changes receive a new version and an overlap period; endpoints are not silently repurposed.

• Keys are shown once. Store them in a secret manager, never in a public repository or client bundle.
• One key per environment or integration is recommended; you are responsible for all requests made with your keys.
• Do not share keys or resell access. A key belongs to the application and account that created it.
• Scopes are assigned by the server. The only scope today is submissions:write.
• Revoke a key immediately if it leaks. Revocation takes effect on the next request and cannot be undone.

You must not:

• bypass rate limits, authentication or scope checks,
• submit bots you do not maintain or misrepresent ownership,
• use reports to spam, harass or manipulate moderation,
• harvest developer profiles or personal data,
• use the API to distribute malware or illegal content, or
• present the API or its data as your own official service.

Automated clients must identify themselves with a truthful User-Agent and handle 429 responses by waiting.

Rate limits are stated in the API documentation and enforced by Cloudflare. They are per location and eventually accurate, not a global quota. Limits, body sizes and endpoints can change when needed for stability or abuse prevention.

There is no SLA and no uptime guarantee. The API can be unavailable during maintenance or incidents. The site reports outages rather than hiding them, but you should not build a business-critical dependency on this service.

Directory content belongs to the respective developers. You may display it with attribution and a link to the listing. You may not imply that a listing is verified, featured or endorsed unless the API response says so.

Public responses contain developer display names and avatars. These are personal data; do not use them for unsolicited contact, profiling or advertising.

The operator can suspend applications, revoke keys or block clients that violate these terms, threaten stability or create legal risk. Where possible, the reason is communicated; immediate action is allowed for active abuse.

You can stop using the API at any time and revoke your keys in the dashboard.

The API and its data are provided as is, without warranty of correctness, completeness, availability or fitness for a particular purpose. Listings are moderated but not security-audited.

Liability follows section 9 of the terms of use: unlimited for intent, gross negligence and personal injury; for slight negligence limited to foreseeable, typical damage from breach of an essential obligation; otherwise excluded where legally permitted. Mandatory statutory liability remains unaffected.

These terms can change with the API. The version published here at the time of use applies. Security reports and API questions: Meros.Basement@gmx.net.

Last updated: 25 October 2026