zapi.
APISPRICINGDOCSMCP
GitHub

Acceptable Use Policy

Last updated: 2026-05-23

01

1. Purpose & Scope

This Acceptable Use Policy (AUP) forms an integral part of the Zapi Terms of Service and sets out the limits on use of the Platform. The AUP applies to all tiers — Free, Pro, and Ultra — and to all API keys issued under your account.

02

2. Permitted Use

The Platform may be used for: • Consuming public data for research, experimentation, and side projects. • Building prototypes, MVPs, and product validation. • Internal dashboards, business intelligence, and analytics. • Legal automation integrations (n8n, Zapier, custom backends). • Developing open-source SDKs / wrappers with clear attribution to Zapi. • Educational content (tutorials, blog posts, videos) demonstrating API usage.

03

3. Prohibited Use — Content

You are PROHIBITED from using the Platform to: • Collect or process personal data (DMs, private contacts, an individual's real-time location) without the explicit consent of the data owner. • Build doxing databases, stalkerware, or surveillance tools targeting individuals. • Access content from non-public sources (private accounts, login-gated, paywall-gated). • Distribute copyrighted content without a valid license. • Distribute illegal content, hate speech, child pornography, or other harmful material.

04

4. Prohibited Use — Technical

You are PROHIBITED from: • Reverse-engineering, decompiling, or copying the Platform's internal architecture. • Bypassing rate limits through multi-accounting, automated IP rotation, or distributed keys. • Running DDoS attacks, request floods, or infinite loops against Platform endpoints. • Building bots that scrape the Platform for the purpose of mirroring content. • Opening accounts under a false identity or another person's name without authorization. • Disrupting other Users (e.g. by flooding shared resources).

05

5. Prohibited Use — Commercial

Unless there is a separate written commercial agreement with Zeative Labs, you are PROHIBITED from: • Reselling access to the Zapi API as your own product. • Rebranding the Zapi API as a third-party product. • Using the Free tier for large-scale commercial production that should be on a paid tier. • Opening multiple Free accounts to combine quotas (quota stacking). • Building a direct substitute product that merely proxies to Zapi without adding value.

06

6. Compliance with Data Sources

Zapi accesses public data from various platforms (Instagram, TikTok, YouTube, etc.). You must: • Comply with the Terms of Service of each original source when using data from the relevant endpoints. • Not use the data for purposes prohibited by the original source (e.g. mass posting automation prohibited by their ToS). • Provide attribution to the original source when redisplaying public content to end-users (e.g. crediting the owner of a YouTube video). Responsibility for compliance with the original sources' ToS rests entirely with the User.

07

7. API Key & Security

• Keep your API key confidential — do not commit it to public repositories or expose it in client-side JavaScript. • Use environment variables, a secrets manager, or a backend proxy for access from the frontend. • Rotate your key immediately if you suspect a leak. • One key per application is recommended — create separate keys to make revocation easier in the event of an incident. Zapi is not responsible for quota consumption or charges resulting from a key leak on the User's side.

08

8. Rate Limit & Fair Use

Each tier has a rate limit and monthly quota listed on the Pricing page. In addition: • Avoid sudden traffic spikes (e.g. 1000 requests in 1 second) — distribute requests with reasonable spacing. • Use application-side caching for data that rarely changes. • Respect the Retry-After header when you receive an HTTP 429 response. • Free-tier accounts showing fair-use abuse patterns will be throttled more aggressively.

09

9. Consequences of Violations

Depending on severity, an AUP violation may result in: • A written warning via email (for minor violations). • More aggressive rate-limit throttling. • Revocation of specific API keys without notice. • Temporary account suspension pending clarification. • Permanent termination of the account and all keys. • Infrastructure-level IP blocking. • Reporting to the competent legal authorities for criminal offenses. Zapi reserves the right to take these actions at its sole discretion without any obligation to refund fees already paid.

10

10. Exceptions & Appeals

If you believe your account was suspended in error, you can file an appeal via email to [email protected] with the subject "AUP APPEAL". Include your account name and registered email, a brief explanation of your use case, and evidence or clarification regarding the activity flagged as a violation. We will review the appeal within 5 business days.

11

11. Reporting Violations

If you become aware of another User violating the AUP — for example, reselling Zapi keys, abusing rate limits, or misusing data — report it to [email protected] with the subject "AUP REPORT" and include supporting evidence such as screenshots, links, or a description of the behavioral pattern. Reports are handled confidentially. We appreciate community contributions to keeping the Platform healthy.

12

12. Changes to the AUP

The AUP may be updated at any time in response to new abuse patterns, regulatory changes, or the evolution of the Platform. Material changes will be announced via email and a public changelog. Your continued use of the Platform after such changes constitutes your acceptance of the latest version of the AUP.

Major outage
zapi. — Public REST API catalog. No fabricated numbers.
TermsPrivacyAUP© 2026