Terms

Service terms for AnyCap

These baseline terms explain what AnyCap provides, what you remain responsible for in agent workflows, and when AnyCap may change, limit, or protect the service.

April 9, 2026

How to read these terms

This page summarizes the legal baseline for using the AnyCap site, CLI, and related workflows. It is structured so readers can understand what is being offered, where the usage boundaries sit, and how the product's operating context connects to the terms.

Rather than acting only as a compliance document, the page also works as a practical reference for operators and buyers who want usage, billing, support, and policy context aligned in one place.

The practical baseline

Authorized workflows only

Use AnyCap only with prompts, files, URLs, and instructions you are authorized to process through the requested agent workflow.

You own the decisions

You remain responsible for submitted inputs, downstream use of outputs, and whether the workflow fits your policies, contracts, and compliance needs.

Capabilities can evolve

Models, routes, limits, interfaces, and provider availability may change as AnyCap and upstream systems evolve.

We may protect the service

AnyCap may meter, rate-limit, queue, reject, or suspend use when needed for abuse prevention, billing enforcement, legal compliance, platform stability, or security.

The operating rules around AnyCap

Scope

What these terms cover

AnyCap provides an AI agent capability runtime, related web surfaces, installation paths, billing surfaces, and support materials for agent-led workflows.
Using any part of the service means you agree to these baseline public terms and to the pricing or product notices shown when a workflow, plan, or paid surface is used.
If you have a separate signed agreement with AnyCap, that written agreement controls to the extent it conflicts with this public page.

Access

Accounts, credentials, and local environments

Keep accounts, API keys, agent credentials, and connected local environments secure and reasonably controlled.
You are responsible for activity occurring through your account or credentials unless caused directly by AnyCap.
Do not bypass quota controls, access restrictions, plan limits, billing logic, or security safeguards.

Inputs

Prompts, files, URLs, and authority to use them

You remain responsible for the prompts, files, URLs, instructions, and third-party data you submit through AnyCap.
Only submit content you are authorized to process and that is lawful to send through the requested workflow.
Before sending production data, confirm that using AnyCap fits your own internal policies, customer commitments, and regulatory obligations.

Outputs

Review, verification, and downstream use

Outputs may be incomplete, inaccurate, offensive, delayed, unavailable, or unsuitable for a given use without human review and validation.
You are responsible for how outputs are used, stored, published, shared, or relied on in downstream systems.
AnyCap does not guarantee that the same prompt, route, provider, or model choice will remain available or produce identical results over time.

Providers

Third-party routing and capability changes

AnyCap may rely on third-party model, hosting, storage, authentication, analytics, payment, or other infrastructure providers to fulfill requests.
To run a workflow, relevant request data may be sent to those upstream providers when needed for processing, delivery, or service operations.
Capabilities may be added, removed, revised, paused, or deprecated, including changes to models, routes, limits, UI surfaces, and availability.

Billing

Credits, pricing, and usage controls

Paid usage is governed by the pricing, credit-pack, and plan information shown at the time of purchase or access.
Promotional credits, free usage, feature availability, and packaging may change over time and may be subject to plan-specific limits or eligibility rules.
AnyCap may meter, throttle, queue, cap, or reject requests based on credits, plan level, provider constraints, operational load, or abuse and risk signals.

Protection

Acceptable use and enforcement

You may not use AnyCap to violate law, abuse third-party services, interfere with platform stability, probe for weaknesses without authorization, or support clearly harmful, deceptive, or unauthorized activity.
AnyCap may investigate suspected misuse and may limit, suspend, or terminate access when reasonably necessary for service protection, abuse prevention, legal compliance, or security response.
We may remove or decline workflows, accounts, or access paths that create disproportionate operational, legal, financial, or trust risk for the platform.

Limits

Disclaimers and liability boundaries

AnyCap is provided on an as-available and as-evolving basis, without a guarantee of uninterrupted operation, provider continuity, or fitness for a specific workflow.
To the maximum extent permitted by law, AnyCap disclaims implied warranties and is not responsible for indirect, incidental, special, consequential, or exemplary damages arising from use of the service.
Nothing on this page is legal advice, and teams with procurement, contractual, or regulated-use requirements should complete their own review before scaling production use.

Make sure the workflow fits your team

AnyCap is built for agent workflows, not as a guarantee that every model, provider, or route will remain fixed forever. Teams using the platform in production should review their data handling assumptions, output review standards, billing expectations, and any procurement or compliance requirements before they scale usage.

Read this page together with the privacy policy, pricing, and about pages so the legal baseline matches the product and operating context. privacy policy, pricing, and about pages so the legal baseline matches the product and operating context.

If your team needs clarification before broader rollout, email the AnyCap team or use the contact page. or use the contact page.