API Usage and Fair Use

Purpose

This API Usage and Fair Use Policy explains how Squillify manages API access, rate limits, quotas, usage controls, automated traffic, and fair use.

It is designed to keep the platform reliable, secure, predictable, and fair for all customers.

This Policy applies to all access to Squillify through APIs, SDKs, MCP integrations, dashboards, scripts, agents, automations, command-line tools, and any other software acting under your account, tenant, organization, user session, or API keys.

Relationship with other policies

This Policy forms part of the Squillify legal and trust documentation. It should be read together with:

• the Terms of Service;
• the Acceptable Use Policy;
• the Tenant and API Key Responsibility Policy;
• the Billing and Refund Policy;
• the Service Availability Policy;
• the Support Policy;
• the Microskill Data Handling Policy;
• the Data Retention Policy.

If there is a conflict between this Policy and a signed written agreement between you and Squillify, the signed written agreement controls to the extent of that conflict.

Customer responsibility

You are responsible for all activity performed through your tenant, account, API keys, access tokens, users, agents, applications, scripts, automations, integrations, and third-party tools.

You are responsible for designing your systems so that they:

• stay within applicable rate limits, quotas, concurrency limits, file limits, and execution limits;
• handle rejected, failed, delayed, throttled, or rate-limited requests safely;
• do not overload Squillify or degrade the experience of other customers;
• do not retry failed requests in a way that creates abusive or unstable traffic;
• do not submit data that your application, users, agents, or policies are not authorized to submit;
• comply with applicable laws, regulations, contracts, and internal policies.

You are also responsible for monitoring the behavior of any agentic system or automated workflow that uses Squillify.

Rate limits

Squillify may apply rate limits at one or more levels, including:

• API key level;
• tenant or organization level;
• user level;
• IP address or network level;
• endpoint level;
• skill or capability level;
• plan level;
• infrastructure protection level.

Rate limits may include requests per second, requests per minute, requests per hour, requests per day, burst limits, concurrent request limits, file upload limits, execution time limits, and other technical controls.

Published limits may differ by plan, endpoint, skill, feature, capability, region, account status, beta program, or commercial agreement.

Quotas

Squillify may apply usage quotas to your plan, tenant, organization, account, API keys, skills, or feature access.

Quotas may include:

• monthly or billing-period request allowances;
• successful execution allowances;
• billable operation allowances;
• file processing allowances;
• temporary storage allowances;
• premium or high-cost skill allowances;
• free-tier usage limits;
• trial limits;
• tenant-level aggregate limits;
• per-key limits configured by tenant administrators.

Usage beyond your included plan allowance may be rejected, throttled, restricted, or billed as overage where your plan allows overage billing.

Where applicable, billing treatment is governed by the Billing and Refund Policy and your applicable plan terms.

High-cost and restricted capabilities

Some Squillify capabilities may be more expensive, resource-intensive, security-sensitive, or abuse-sensitive than others.

Squillify may apply stricter controls to such capabilities, including:

• lower rate limits;
• lower quotas;
• additional validation;
• file size restrictions;
• execution time restrictions;
• concurrency restrictions;
• plan restrictions;
• tenant-level enablement;
• API-key-level skill access controls;
• temporary suspension or manual review;
• paid-plan-only access.

High-cost or restricted capabilities may include, without limitation, document processing, file conversion, OCR, media processing, large payload processing, network-facing capabilities, security-sensitive capabilities, and any capability that materially affects infrastructure cost or abuse exposure.

Free tier and trial usage

Free tiers, free credits, trial plans, preview plans, promotional allowances, and evaluation access are provided for genuine testing, development, evaluation, and low-volume use.

You may not use free-tier, trial, or promotional access to:

• operate production workloads without an appropriate paid plan;
• avoid payment by creating multiple tenants, accounts, API keys, identities, or organizations;
• resell, proxy, sublicense, or expose Squillify access to third parties;
• run bulk workloads, scraping, benchmarking, load testing, or stress testing without written authorization;
• consume disproportionate infrastructure resources;
• bypass plan restrictions, quotas, or billing controls;
• simulate paid-plan capacity through distributed accounts or keys.

Squillify may limit, throttle, suspend, or terminate free-tier, trial, or promotional access where use is abusive, excessive, misleading, or inconsistent with its intended purpose.

Automated and agentic traffic

Automated traffic is expected and supported by Squillify when it complies with this Policy, the Acceptable Use Policy, and your plan limits.

Agentic systems can generate high-volume, recursive, repeated, or unexpected traffic. You must design and supervise agents so that they:

• use scoped API keys;
• respect rate limits and quotas;
• implement backoff and retry limits;
• avoid uncontrolled loops;
• avoid repeated failed executions;
• avoid unnecessary catalog scans;
• avoid excessive discovery calls;
• stop safely when limits are reached;
• do not submit unauthorized, personal, confidential, regulated, or sensitive data unless you have determined that such submission is lawful and permitted;
• do not perform actions that would violate the Acceptable Use Policy if performed by a human user.

Squillify may treat traffic generated by agents, scripts, applications, or automations as traffic generated by you.

Handling rate-limit and quota responses

When a request exceeds an applicable limit, Squillify may reject it with a rate-limit, quota, authorization, billing, or policy error.

Your integration should handle limit responses safely. You should:

• use exponential backoff or another controlled retry strategy;
• avoid immediate infinite retries;
• respect retry-after or rate-limit headers where provided;
• avoid retrying non-idempotent operations unless safe;
• distinguish between temporary rate limits, hard quota limits, authorization errors, validation errors, and policy denials;
• surface limit errors clearly to your users or operators;
• monitor repeated failures and stop unsafe workflows.

Repeated retries that ignore limits, generate excessive errors, or threaten platform stability may be treated as abuse.

Catalog, discovery, and search usage

Squillify may provide catalog, discovery, search, or skill-resolution capabilities to help agents and applications find appropriate skills.

You may not use catalog, discovery, or search endpoints to:

• scrape the catalog beyond documented or permitted access;
• reconstruct, clone, or bulk-extract Squillify's catalog, ranking logic, metadata, pricing logic, or internal classification;
• run excessive discovery traffic instead of caching appropriate results;
• bypass plan limits or skill access controls;
• benchmark Squillify without written authorization;
• build a competing service using unauthorized extraction of Squillify content or metadata.

Squillify may require caching, pagination, access tokens, scoped access, or other controls for catalog and discovery features.

Benchmarking, load testing, and stress testing

You may not conduct benchmark tests, load tests, stress tests, capacity tests, availability tests, abuse simulations, vulnerability scans, or similar high-impact testing against Squillify without prior written authorization.

This restriction does not prevent normal development testing within your plan limits.

Authorized testing may be subject to:

• a defined time window;
• agreed traffic volume;
• specific test accounts or tenants;
• restricted endpoints;
• notification requirements;
• safety limits;
• post-test reporting.

Unauthorized testing that degrades, threatens, or probes Squillify infrastructure may result in throttling, suspension, termination, or other enforcement action.

Resale, proxying, and service wrapping

Unless expressly authorized in writing by Squillify, you may not:

• resell Squillify as a standalone API service;
• proxy Squillify access for unrelated third parties;
• sublicense API access;
• pool multiple customers behind one tenant in a way that avoids plan terms;
• expose Squillify credentials or execution capacity as a public or semi-public service;
• use Squillify as hidden infrastructure for a competing API platform;
• remove or obscure Squillify usage limits, attribution, or contractual controls where those controls apply.

This does not prohibit normal use of Squillify inside your own application for your own users, provided that your use complies with your plan, agreement, and this Policy.

Fair use

Fair use means using Squillify in a way that is consistent with:

• your plan;
• your documented limits;
• normal development, testing, or production usage;
• platform stability;
• security;
• cost predictability;
• the rights and experience of other customers.

Use may be considered unfair, excessive, or abusive even if it does not technically exceed a published numeric limit, including where it:

• creates disproportionate infrastructure load;
• generates excessive errors or retries;
• exploits gaps in enforcement logic;
• circumvents limits through multiple keys, tenants, accounts, identities, IP addresses, proxies, or distributed systems;
• uses low-cost or free-tier access for high-cost workloads;
• interferes with service reliability;
• causes abnormal operational, security, support, or compliance burden.

Platform protection controls

Squillify may use technical and operational controls to protect the platform, including:

• rate limiting;
• quota enforcement;
• throttling;
• request rejection;
• API key restriction or revocation;
• temporary access suspension;
• tenant-level restriction;
• capability-specific restriction;
• IP or network blocking;
• abuse detection;
• anomaly detection;
• logging and metadata analysis;
• manual review;
• plan enforcement;
• billing enforcement.

These controls may be applied automatically or manually.

Squillify may apply stricter controls during incidents, attacks, degraded platform conditions, abnormal traffic, abuse investigations, beta periods, or infrastructure protection events.

Limit changes

Squillify may change rate limits, quotas, capability limits, file limits, concurrency limits, execution limits, free-tier limits, and fair-use controls.

Where reasonably possible, Squillify aims to provide notice of material reductions to generally available paid-plan limits.

Squillify may make immediate changes without prior notice where needed to:

• protect the platform;
• prevent abuse;
• respond to security risks;
• comply with law;
• avoid infrastructure harm;
• preserve service availability;
• correct technical or billing defects;
• protect other users or third parties.

Beta, preview, free-tier, trial, promotional, experimental, or high-risk capabilities may change at any time.

Billing impact

Usage may be measured for billing, quota enforcement, abuse prevention, reliability, security, analytics, and operational purposes.

Unless otherwise stated in your plan or agreement:

• successful executions may count toward quotas;
• billable operations may count toward billing;
• rejected requests may count toward rate limits or abuse monitoring;
• failed requests may count toward operational metrics;
• retries may create additional requests and may consume quota or trigger rate limits;
• use of high-cost capabilities may be priced, limited, or metered differently.

Billing disputes, refunds, cancellations, failed payments, taxes, invoices, and overage charges are governed by the Billing and Refund Policy and your applicable plan terms.

Data handling and telemetry

Squillify's API usage controls rely on operational metadata.

Squillify may collect and process metadata necessary for:

• authentication;
• authorization;
• rate limiting;
• quota enforcement;
• billing;
• abuse prevention;
• security monitoring;
• service reliability;
• debugging;
• performance measurement;
• product analytics;
• customer support.

Squillify's handling of submitted payloads, temporary files, telemetry, and retention is governed by the Microskill Data Handling Policy, File Handling Policy, Telemetry and Analytics Policy, and Data Retention Policy.

This Policy does not authorize Squillify to use submitted payloads for model training.

Customer monitoring

You should monitor your API usage and investigate unusual activity.

At minimum, you should monitor:

• request volume;
• error rate;
• rate-limit responses;
• quota consumption;
• failed executions;
• unusual API key usage;
• unexpected agent loops;
• unexpected geography or network sources;
• abnormal file processing;
• high-cost capability usage;
• billing anomalies.

You should promptly rotate or revoke API keys that are exposed, compromised, misused, or no longer needed.

Support and debugging

Because Squillify is designed not to permanently store raw submitted payloads, support may be unable to reconstruct execution issues from raw input data.

When reporting API issues, you may be asked to provide:

• request identifiers;
• timestamps;
• endpoint or skill names;
• error codes;
• non-sensitive metadata;
• sanitized payload examples;
• reproduction steps;
• relevant client-side logs.

Do not send secrets, passwords, production API keys, personal data, confidential information, regulated data, or sensitive data to support unless Squillify has specifically instructed you to use an approved secure channel and you are authorized to provide that data.

Enforcement

If Squillify reasonably believes that your use violates this Policy, your plan, the Terms of Service, the Acceptable Use Policy, or applicable law, Squillify may take action including:

• issuing a warning;
• rejecting requests;
• throttling traffic;
• reducing limits;
• restricting specific API keys;
• restricting specific capabilities;
• requiring key rotation;
• requiring remediation;
• suspending access;
• terminating access;
• preserving relevant metadata where legally permitted and necessary;
• reporting unlawful activity where legally required or appropriate.

Squillify may act immediately where necessary to protect the platform, other users, infrastructure, providers, or third parties.

Reporting usage issues or abuse

To report suspected abuse, contact [email protected].

To report a security vulnerability, contact [email protected].

For billing or plan-limit questions, contact [email protected].

Questions

For questions about this Policy, contact [email protected].