Last updated: 2026-08-10
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 every tier, and to all API keys issued under your account, including keys used by external clients you connect through the MCP server.
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 and wrappers with clear attribution to Zapi. • Educational content (tutorials, blog posts, videos) demonstrating API usage.
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 sexual abuse material, or other harmful material.
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, for example by flooding shared resources.
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. • Building a direct substitute product that merely proxies to Zapi without adding value.
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, for example mass posting automation. • Provide attribution to the original source when redisplaying public content to end-users, for example crediting the owner of a YouTube video. • Honour removal requests from the people whose public data you redisplay, and stop displaying data that is no longer public at the source. Responsibility for compliance with the original sources' ToS rests entirely with the User.
• 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, so a single key can be revoked without taking down everything else. Zapi is not responsible for quota consumption or charges resulting from a key leak on the User's side.
Each tier has a rate limit and monthly quota listed on the Pricing page at /pricing. In addition: • Avoid sudden traffic spikes. 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.
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. Refund treatment for a terminated paid period is set out in the Refund Policy at /refund.
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.
If you become aware of another User violating the AUP, for example reselling Zapi keys, abusing rate limits, or misusing data, use the form at /report or email [email protected]. Include supporting evidence such as screenshots, links, or a description of the behavioral pattern. The same channel handles copyright complaints and requests to remove personal data from an API response. Reports are handled confidentially.
The AUP may be updated at any time in response to new abuse patterns, regulatory changes, or the evolution of the Platform. Material changes are announced by email to registered users, and the revision date at the top of this page always reflects the current version. Your continued use of the Platform after such changes constitutes your acceptance of the latest version of the AUP.