API & MCP fair-use policy

API and MCP access is included in every aclipp plan for the features you have purchased, subject to this fair-use policy. We want you to automate your work while keeping aclipp reliable for everyone.

What is included

Everyday integrations, AI assistants and routine automation are included. For example, you can:

  • Ask an AI assistant to analyze your coverage or prepare a weekly summary.
  • Synchronize new clippings with your internal tools.
  • Create and update projects, dashboards and reports through automated workflows.

Your plan's existing allowances still apply, regardless of whether you use the app, API or MCP. Creating clippings uses your clipping allowance; running AI visibility prompts uses your AI Visibility credits. This policy introduces no separate monthly API request quota or automatic usage charges.

Rate limits and responsible use

Technical rate limits apply to API and MCP traffic. Integrations must respect rate-limit responses, wait before retrying and avoid uncontrolled retry loops. Do not bypass limits by rotating credentials, distributing requests across accounts or using another access method.

Use incremental synchronization where possible. Repeatedly downloading an entire archive when only a few records have changed creates avoidable load. A one-off import, export or temporary burst does not by itself mean your use is unfair; technical rate limits still apply.

Sustained high-volume usage

A separate capacity agreement may be needed for sustained workloads that place a disproportionate demand on shared capacity. We assess request frequency, concurrency, the processing required by the operations and the duration and impact of the workload. Request count alone does not determine fair use.

Examples include continuously exporting large archives, running many resource-intensive operations in parallel or polling at a frequency that degrades service for other customers.

Before restricting legitimate usage on fair-use grounds, we will contact you, explain the workload and its impact, and give you a reasonable opportunity to adjust it. We will work with you on a more efficient integration or offer a separate capacity agreement. Any additional fees require your agreement in advance. If the workload remains excessive, we may limit the affected automation to protect shared capacity.

Existing technical rate limits continue to apply automatically. If traffic poses an immediate risk to service stability, we may temporarily throttle or suspend the affected traffic without advance notice. We will inform you promptly and remove the restriction once the risk is resolved.

Your agreement and questions

Individually agreed capacity and contract terms take precedence. Publishing this policy does not by itself change existing contracts. Any contractual changes follow the applicable agreement and notice requirements.

Planning a high-volume integration, or unsure whether your workflow fits? Contact us so we can agree on suitable capacity before you depend on it.