This site is an independent third-party technical service provider. Claude™ and Anthropic® are trademarks of Anthropic, PBC. This site has no affiliation, endorsement, or partnership with Anthropic.

Claude API Service Delivery Terms

Last updated:May 24, 2026

  • Effective Date: May 24, 2026 (synchronized with the Terms of Service and Privacy Policy; to be confirmed prior to official release)
  • Version: v1.1
  • Operating Entity: NiceCloud LLC (a limited liability company organized in the State of Colorado, USA; registered and correspondence address: 1500 N Grant St Ste R, Denver, CO 80203, USA)

These Terms constitute the agreement between NiceCloud LLC (which operates ClaudeAPI.com, hereinafter the “Platform”) and the User concerning service delivery. They are to be used together with the Refund Policy, Terms of Service, and Privacy Policy, and form an integral part thereof pursuant to Section 1.2 of the Terms of Service. Please read and confirm these Terms in full before topping up or making calls.

Legal Notice: These Terms have been aligned with the current Terms of Service and Privacy Policy (both v1.1); matters involving specific payment channels, the User’s region, consumer protection, and taxation should still be reviewed by professional legal counsel in light of the actual circumstances prior to official release. This document does not constitute legal advice.

1. Platform Identity Statement (Please Read First)

  1. ClaudeAPI.com is an independent third-party API access and credit top-up platform that provides users with the interface access, credit billing, and technical support services required to call the relevant large language models.

  2. The Platform is not an official Anthropic platform, nor an official Claude top-up channel, and has no investment, agency, authorization, or affiliation relationship with Anthropic or Claude (unless otherwise stated in writing; see Section 2.4 of the Terms of Service). Names such as “Claude” and “Anthropic” are used solely to objectively describe the model capabilities to which the Platform connects, and the relevant trademark rights belong to their respective owners.

  3. What the User purchases and uses on the Platform is the third-party API call credits and corresponding technical services provided by the Platform, and not an official subscription membership such as Claude Pro or Claude Max, nor an official account balance or official top-up product of the Anthropic Console. The Platform balance may be used only within ClaudeAPI.com and the Base URL environment it provides.

  4. If the User requires an official membership, an official console balance, or official technical support, the User should proceed to the relevant official channel. Any discrepancy in expectations arising from mistaking the Platform for an official channel does not constitute a breach by the Platform, and the related refund matters shall be handled under the Refund Policy.

  5. Once the User tops up or initiates a call, the User shall be deemed to have read, understood, and accepted these Terms, the Terms of Service, the Privacy Policy, and the Refund Policy in their entirety.

2. Definitions

For ease of understanding, the core concepts in these Terms have the following meanings:

  • Service: a collective term for the digital services provided by the Platform, including API access, credit billing, key management, call routing, billing, and technical support.
  • Credits / Balance: a virtual billing unit that enters the User’s Platform account after a top-up and is used to deduct call fees on a usage basis; it has no cash value and does not possess the attributes of legal tender. Its legal nature is described in Section 8.2 of the Terms of Service.
  • Token: the unit of measurement by which a model processes text; call fees are generally calculated based on the number of input and output Tokens and the unit price of the selected model.
  • API Key (“Key”): the credential created by the User on the Platform for identity authentication and call billing.
  • Base URL / model ID: the interface address and model identifier provided by the Platform, on the basis of which the User initiates calls in its own program or a third-party client.
  • Pre-authorization (“pre-deduction”): to ensure billing accuracy for concurrent and asynchronous calls, the Platform may freeze the estimated fee when a call is initiated, and settle on an actual basis after the call ends, refunding or charging the difference.
  • Call logs: the metadata recorded by the Platform, including call time, model, Token usage, billing amount, status code, request ID, and source-IP digest, which is the primary basis for billing and dispute handling; its collection, storage, and retention period follow Sections 2.3 and 7 of the Privacy Policy.
  • Upstream service provider: the third-party model service providers that provide model capabilities or computing power to the Platform (primarily Anthropic, PBC and providers offering models through Amazon Bedrock (AWS)), together with their associated infrastructure.

3. Service Content and Activation

  1. The delivery content that the Platform provides to the User generally includes:

    1. issuing the API call credits purchased by the User to the corresponding ClaudeAPI.com Platform account;
    2. providing an API Key that can be created and managed within the Platform;
    3. providing the Platform Base URL, model ID, interface documentation, call examples, balance records, and usage records;
    4. providing, in accordance with Platform rules, a billing-query function, an invoice-application portal, or manual invoicing support;
    5. providing technical support, troubleshooting, and ticket handling in accordance with the service plan or Platform description.

    The foregoing service content is consistent with Section 2 (Service Description) of the Terms of Service.

  2. This Service is provided in a digital, virtualized manner and does not involve physical logistics, courier signature, or offline delivery. Calling capability generally takes effect immediately after the top-up is credited and the key is created.

  3. The User shall be responsible for the configuration and compatibility of its calling program, runtime environment, and third-party clients. The Platform provides only public, standard interface documentation and public technical support, and makes no commitment or warranty as to the development, operational results, or adaptation effects of the User’s own system.

4. Top-Up and Credit Issuance

  1. The User may top up in the manner and currency displayed by the Platform. After a successful top-up, the corresponding credits will be issued to the User’s Platform account, where the User may query the balance and the details of its changes. A multi-dimensional description of the billing rules is set out in Section 8.1 of the Terms of Service.

  2. Credits are virtual billing units that have no cash value and may not be transferred, cashed out, inherited, or pledged, and may be used only to deduct call and related service fees on the Platform (consistent with Section 8.2 of the Terms of Service); under no circumstances may the User demand that credits be converted into cash or any other form of property.

  3. Unconsumed credits shall expire 365 calendar days after the most recent top-up; 30 days before expiration, the Platform will send a reminder by email (consistent with Section 8.5.5 of the Terms of Service). The specific usage rules for gift and promotional credits shall be as displayed in real time on the top-up page or in the User’s account, and the Platform shall be entitled to retain such rules for record; gift and promotional credits are not subject to the validity-period extension rule.

  4. If situations such as successful payment but credits not credited in time, duplicate charges, or an abnormal credited amount occur, the User should promptly contact Platform customer service. Where verified to be a Platform or payment-link anomaly, the Platform will provide re-issuance of credits, billing correction, re-crediting, or refund handling, as specifically handled under the Refund Policy.

5. Determination of Completed Delivery

  1. Unless otherwise expressly agreed on the page, in the order, or by the parties, the corresponding top-up service shall be deemed to have been delivered upon satisfaction of any of the following:

    1. after the User’s successful payment, the top-up credits have been issued to the User’s ClaudeAPI.com Platform account;
    2. the User’s account is already able to create an API Key, or is already able to view the Base URL, model ID, interface documentation, and call instructions provided by the Platform.

  2. Completion of service delivery is not conditioned on the User’s actual initiation of an API call or full consumption of the credits. The issuance of credits to the account signifies that the Platform has performed all of its delivery obligations for that top-up; except as otherwise provided by the Refund Policy and applicable law, the User may no longer claim a refund or compensation, or require us to bear liability for breach, on the grounds of not having actually used the service or not having consumed the credits.

  3. For non-credit services such as technical support, invoicing, and billing verification, where the Platform has already processed or responded through in-platform messages, email, tickets, online customer service, or other reasonable means, that service shall be deemed delivered.

  4. Completion of delivery does not mean that no refund is possible under any circumstances. The rules for refund, re-issuance, billing correction, and compensation shall be governed uniformly by the Refund Policy, Section 8.5 of the Terms of Service, the order-page description, and applicable law.

6. Metering and Billing of API Call Services

  1. The Platform’s call service is a digital service metered by actual usage. When the User calls a model through the Platform, the system may incur fees based on the model, input and output Tokens, context length, tool calls, caching, retries, searches, images, or other capabilities. The specific billing shall be based on the pricing rules displayed on the Platform pages, the metering system, the call logs, and the upstream settlement records; the billing dimensions are consistent with Section 8.1 of the Terms of Service.

  2. For calls using the pre-authorization mechanism, the Platform freezes the estimated fee when the call is initiated and settles on an actual basis after the call ends: where the actual fee is lower than the pre-authorized amount, the difference is immediately returned to the account balance; where higher, it is settled on an actual basis and the additional amount is charged. The freezing and actual-basis settlement of the pre-authorization are part of the normal billing process and do not constitute a refund matter.

  3. If a request has already been received by the Platform and forwarded to the upstream model service, or has already incurred model processing, Token generation, a partial response, tool calls, retries, caching, searches, bandwidth, storage, risk-control review, or other irrevocable costs, then even if the User’s client did not fully display the result or the User unilaterally claims not to have received a response, that portion of the fee shall still be charged to consumed credits on an actual basis, and the User shall bear that portion of the fee in full.

  4. The Platform’s call logs are the primary basis for determining whether a call was completed, the Token usage, and the billing amount. If the User disputes the billing of a particular call, the User may query the logs within the account and apply for manual verification under the Refund Policy (the collection and retention of log data follow Sections 2.3 and 7 of the Privacy Policy).

  5. If, upon Platform verification, a request was not actually processed, was not forwarded upstream, or did not incur upstream costs, or if a Platform billing-system error caused an overcharge, the Platform will perform billing correction, credit return, compensation, or refund handling.

7. Third-Party Clients and User Configuration

  1. The Platform supports users in accessing the Platform interface through compatible third-party clients, SDKs, plugins, proxy tools, or their own programs. The User shall confirm on its own whether the client used supports the Base URL, API Key, model ID, request format, context length, streaming output, timeout settings, and error handling provided by the Platform. The rules on bearing the risk of third-party tools are set out in Section 6 of the Terms of Service.

  2. Where the Platform has already provided a usable API Key, Base URL, model ID, and interface documentation, problems caused by the User’s code errors, client incompatibility, incorrect parameter configuration, erroneous model selection, network environment, proxy settings, timeout settings, key disclosure, automatic retries, looping calls, or third-party client restrictions generally do not constitute non-delivery by the Platform; the corresponding fees incurred shall be settled in full on an actual basis, the Platform has no obligation to return or reduce that portion of the fees, and it bears no liability therefor. The User’s credential-safekeeping obligations are set out in Sections 4.2–4.3 of the Terms of Service.

  3. The following situations likewise shall not be regarded as non-delivery by the Platform: the User selected a model or parameters that do not match its own needs; or the model returned, within its capability boundaries, a normal result that is inconsistent with the User’s subjective expectations. The refund handling for the foregoing situations shall be conducted under Section 5 (Situations Generally Not Eligible for Refund, including user-caused situations) of the Refund Policy.

8. Upstream Services and Model Changes

  1. The Platform’s services depend on third parties such as upstream model service providers, cloud service providers, payment service providers, and network service providers. The User understands and agrees that model availability, model name, model ID, pricing, multipliers, context length, rate limits, concurrency limits, regional policies, risk-control policies, interface policies, output capabilities, and service stability may change for upstream policy, cost, technical, or compliance reasons, and may affect the availability, pricing, or call performance of the Platform’s corresponding services. The rules on service availability and changes are set out in Section 9 of the Terms of Service.

  2. When the User calls an upstream model through the Platform, in addition to these Terms, the User must also comply with the then-effective terms of service and acceptable use policies of the relevant upstream service provider (such as Anthropic or AWS); such upstream terms are incorporated pursuant to Section 2.3 of the Terms of Service and are binding on the User. Where the upstream terms conflict with these Terms, the stricter provision of the upstream terms shall prevail with respect to that upstream model. The User shall bear all liability arising from its violation of the upstream terms; if this causes loss to the Platform, the User shall fully indemnify the Platform for all of its losses (including but not limited to damages, attorneys’ fees, notarization fees, and travel expenses).

  3. When the foregoing upstream changes occur, the Platform will adjust the service on an actual basis within a reasonable scope, update its documentation and pricing descriptions, and notify the User via in-platform announcements, documentation updates, or account notices; where feasible, it will provide an alternative model or migration instructions. For material changes such as price adjustments or model retirement, the Platform will give advance notice as far as possible in accordance with Sections 8.3 and 9.3 of the Terms of Service (material price changes notified at least 14 days in advance; non-experimental model retirement provided with a transition period of no less than 14 days).

  4. For service changes caused by upstream factors, the Platform in principle passes them through on an actual basis, which under no circumstances constitutes a breach by the Platform; however, if the Platform is itself at fault in execution (e.g., erroneous billing, mis-routing, or a Platform-side failure that causes a failed call to nonetheless be charged), the Platform will bear the corresponding refund, re-issuance, or billing-correction responsibility under the Refund Policy. Except for the liability expressly provided in these Terms, the Platform need not bear any additional compensation or indemnity to the User for service changes caused by upstream factors.

  5. Where the service is temporarily unavailable due to force majeure, upstream interruption, network failure, or other causes beyond the Platform’s reasonable control, the Platform will use its best efforts to restore it, and will handle the portion genuinely attributable to Platform responsibility under the Refund Policy. Unless the Platform has expressly committed otherwise, the Platform does not warrant that any particular upstream model, price, rate, context length, or interface capability will be permanently available.

9. User’s Obligation to Confirm

Before topping up, purchasing, creating an API Key, or initiating a call, the User shall confirm that:

  1. the User is aware that the Platform is a third-party platform and not an official Anthropic or Claude top-up channel;
  2. the User understands that what is purchased is the Platform’s API call credits, and not an official Anthropic Console balance or an official membership such as Claude Pro or Claude Max;
  3. the User has read and agreed to the pricing, billing methods, and model descriptions displayed by the Platform, these Service Delivery Terms, the Refund Policy, the Terms of Service, the Privacy Policy, and the relevant service rules;
  4. the User has confirmed that its use case, client, code, and configuration are able to adapt to the Platform interface;
  5. the User has properly safeguarded its API Key and is responsible for the calls generated by its account, key, and program;
  6. the User is aware that this Service is intended only for developers, enterprises, and organizational users with full legal capacity, and is not directed at natural persons under 18 years of age, and is not offered to the mainland region of the People’s Republic of China; and that neither the User itself nor the entity actually using the service falls within the foregoing prohibited scope, failing which the Platform shall be entitled to terminate the service immediately, freeze the entire account balance, and bear no refund or compensation liability. The specific eligibility, geographic, and sanctions restrictions are set out in Section 3 of the Terms of Service.

If the User breaches any of the confirmations in this Section, all losses arising therefrom (including but not limited to claims and penalties imposed on the Platform by upstream service providers) shall be borne by the User, and the fees already incurred shall not be refunded. The Platform shall be entitled to suspend or terminate the service immediately.

10. Platform Responsibility and Fault Handling

  1. The Platform will safeguard the stability of the service and the accuracy of billing through reasonable technical and management measures.

  2. If credits are not credited, a duplicate charge occurs, billing is clearly abnormal, a Platform failure occurs, an API Key cannot be created, a model is unavailable, or a call-record dispute arises, the User may contact Platform customer service and provide the account email, order number, payment voucher, call time, request ID, error message, and relevant screenshots.

  3. For problems genuinely caused by Platform responsibility (such as successful payment not credited, duplicate charges, abnormal charges or charged-but-failed calls caused by a Platform system failure, or obvious billing errors), the Platform will provide a refund, re-issuance of credits, or billing correction under the Refund Policy. Where verified to be attributable to user-caused reasons, third-party client reasons, the User’s network environment, upstream policy changes, or other factors not attributable to the Platform, the Platform may assist in troubleshooting but does not thereby bear a refund obligation.

  4. To the maximum extent permitted by applicable law, the Platform’s aggregate total liability to the User under these Terms or this Service shall not exceed the higher of (a) the service fees actually paid by the User to the Platform and consumed within the 12 months preceding the event giving rise to liability, and (b) US$100, as specifically governed by Section 14 (Disclaimer and Limitation of Liability) of the Terms of Service; however, this Section does not relieve the Platform of liability it must bear under the law, nor does it exclude the rights to which the User is entitled under mandatory law.

11. Billing, Logs, and Billing Disputes

  1. The User may query top-up records, call logs, and billing details within the account (the handling of the relevant logs and personal information follows Sections 2.3 and 7 of the Privacy Policy).

  2. If the User disputes the billing or the billing of a particular call, the User shall raise the objection in writing within 30 days of the date the transaction occurs, providing complete supporting materials (including but not limited to account information, call time, request identifier, and other necessary documentation); if not raised within the period or if complete supporting materials are not provided, the User shall be deemed to have no objection to the billing of that transaction, all billing shall be valid, the User may no longer make any claim regarding that transaction, the Platform has no obligation to verify it, and the Platform bears no refund or compensation liability.

  3. The Platform will verify based on call logs and system records; where verified to be genuinely attributable to the Platform, the matter will be handled under the Refund Policy; where verified that the fee was genuinely and accurately incurred, it shall be settled on an actual basis.

12. Amendment of Terms

  1. The Platform may revise these Terms in accordance with laws and regulations, upstream policies, and business adjustments, and will publish revisions via website announcements, console notices, in-platform messages, or email.

  2. Material changes involving the User’s principal rights and obligations take effect 14 days after the notice is issued; other changes take effect upon publication (consistent with Section 17 of the Terms of Service). A User who continues to top up or make calls after a change takes effect shall be deemed to have accepted the revised content; a User who does not accept it should cease use and may apply, under the Refund Policy, for the handling of its qualifying unused balance.

13. Governing Law and Dispute Resolution

  1. The formation, validity, interpretation, and performance of these Terms are governed by the substantive law of the State of Colorado, United States of America, excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods. The parties shall first seek to resolve disputes through good-faith negotiation of no less than 30 days; if negotiation fails, the dispute shall be submitted, pursuant to Section 18 of the Terms of Service, to mandatory individual arbitration before the American Arbitration Association (AAA) in Denver, Colorado (including a class-action / class-arbitration waiver, a jury-trial waiver, and a 30-day arbitration opt-out right after first accepting the agreement). The complete dispute-resolution mechanism is detailed in Section 18 of the Terms of Service.

  2. These Terms, together with the Refund Policy, Terms of Service, and Privacy Policy, constitute the complete agreement; in the event of any inconsistency, the Terms of Service shall prevail, except that matters concerning the processing of personal information shall be governed by the Privacy Policy (consistent with Section 1.2 of the Terms of Service).

  3. The matters addressed in these Terms — including consumer protection, cross-border payments, and taxation — still require further review and confirmation by professional legal counsel in light of the Platform’s actual payment methods, the User’s region, and specific business processes.

14. Notices and Service

  1. The various notices issued by the Platform to the User may be made through any of the following: Platform website announcements, console notices, in-platform messages, the User’s registered email, or customer-service messages; a notice takes effect on the date it is published or successfully sent.

  2. The User shall ensure that the contact information on file is true and valid, and shall promptly update it and notify the Platform of any change; the User shall bear the corresponding consequences of being unable to receive notices due to incorrect or untimely updated information.

These Terms are intended to clearly explain the manner of service delivery and the boundaries of responsibility, and are not used to unilaterally relieve the Platform of its due obligations. Within the scope of Platform responsibility, the rights to which the User is entitled by law, and the refund, re-issuance, and billing-correction mechanisms agreed in the Refund Policy, are not affected by these Terms.