Help

Terms of service

Last updated: October 28, 2026

By signing up for or using CoreCode, you agree to the terms of service, acceptable use policy, refund rules and privacy notice on this page. Continuing to use the service after the terms change means you accept the updated version.

Terms of service

The service

CoreCode provides an API relay for Claude models: it forwards the Anthropic Messages requests Claude Code sends to official Anthropic Claude and bills by actual usage. Available models and unit prices are listed on the Pricing page.

CoreCode is an independent third-party service. It is not an official Anthropic product and has no authorization, partnership or agency relationship with Anthropic.

Accounts and keys

• You sign up with an email or a third-party account and are responsible for everything done under your account.
• An API key is the payment credential of your account. Keep it safe, do not commit it to a code repository, and do not share it. If a key leaks, delete it on the console's API Keys page right away and create a new one. Usage while it was leaked is billed as usual.
• Code, files and other content you submit must be content you have the right to process. Do not submit other people's personal information, trade secrets or keys without authorization.

Credit and billing

• The service runs on prepaid credit: a ¥1 top-up buys $1 of credit.
• Each request is billed by its input, output, cache read and cache write tokens at the prices on the Pricing page. Every charge is listed in the Usage Logs.
• Once your credit is used up, requests are refused; they resume automatically after a top-up.
• Price changes are announced on the website in advance; completed requests are billed at the price in effect at the time.
• Bonus credit, such as top-up bonuses, the new-user pack and referral rewards, can only pay for the service. It cannot be withdrawn or transferred.
• Refunds are covered in Refunds below; invoice rules are published separately.

Availability

We do our best to keep the service stable but do not promise it will never be interrupted. Upstream failures, network problems, maintenance and force majeure can make it temporarily unavailable. When the service fails, retry; failed requests are not charged.

Upstream changes

The available models, context lengths and rate limits depend on Anthropic. When Anthropic changes models, prices or limits, or retires a model, we follow, and announce it in advance where we can. Such changes do not affect your balance, which remains usable on other models.

Suspension and termination

We may limit, suspend or terminate accounts that violate these terms or the acceptable use policy, without notice in serious cases. The balance of an account suspended or terminated for a violation is frozen and not refunded. If you believe the decision is wrong, contact us within 30 days to appeal; if it was a mistake, we restore the account and its balance. You may stop using the service at any time and close your account in the console.

Disclaimer

• Model output is generated by Claude and may be inaccurate or incomplete. Check it yourself before use, especially code, commands, and anything about security, law, medicine or finance.
• Claude Code reads and writes files and runs commands on your computer. Set its permissions yourself, confirm irreversible actions such as deleting, publishing or transferring money before they run, and review and test generated code before it goes to production.
• To the extent permitted by law, CoreCode is not liable for losses caused by using model output, generated code or commands it runs, nor for indirect losses such as lost profit, data or business. CoreCode's total liability is capped at the fees you actually paid in the 30 days before the dispute.
• If your breach of these terms or of the law causes CoreCode claims, penalties or losses, you bear them.
• Nothing here excludes liability that the law does not allow to be excluded.

Acceptable use policy

Requests you send through CoreCode are ultimately processed by Anthropic, so Anthropic's usage policy also applies. In addition, the following are not allowed:

• Generating or spreading illegal content, or using the service for illegal activity.
• Sharing, renting or reselling API keys, or packaging CoreCode as a service sold to third parties.
• Disguising the client, tampering with requests, or otherwise bypassing the Claude Code-only rule or the rate, concurrency and credit limits.
• Writing or deploying malware, or intruding into, scanning or attacking systems without authorization. Authorized security testing and vulnerability research are allowed.
• Generating pornographic or sexually explicit content. Sexual content involving minors is prohibited without exception.
• Bypassing the model's safety measures with jailbreaks, prompt injection or similar techniques.
• Fraud, spam, impersonating others, or collecting or processing other people's personal information without authorization.
• Using model output to train or distill a model that competes with Claude, or scraping model output in bulk.
• Attacking, scanning or load-testing CoreCode's services, or trying to obtain other users' data.
• Reverse engineering or cracking CoreCode's services, APIs or client checks, or probing our upstream accounts and configuration.
• Registering accounts in bulk, farming bonus credit or referral rewards, or topping up with a stolen payment method.
• Deliberately generating large volumes of requests that disrupt other users.

Refunds

What can be refunded

You can ask for a refund of balance you actually paid for and have not used, in full or in part. Refunds carry a 20% fee:

Refund = (amount paid − amount used − bonus credit) × 80%

Balance converts at $1 of credit = ¥1, and the amount used is what the Usage Logs show. For example, after a ¥1,000 top-up with a ¥100 bonus and ¥300 used, the refund is (1,000 − 300 − 100) × 80% = ¥480.

What is not refunded

• Credit already used. Once a request completes, its upstream cost has been incurred.
• Top-up bonuses, the new-user pack, referral rewards and credit issued as compensation.
• The balance of an account suspended or terminated for violating these terms.
• Output that falls short of expectations, refusals, or different answers to the same question. That is how models behave, not a service failure.

Before a large top-up, start with a small one to confirm the models and billing suit your needs.

Billing errors

A charged failed request, a duplicate charge or a pricing error is not a refund: once we verify it, we return the full amount to your balance with no fee. Contact us within 15 days of noticing it, with the request time and the matching Usage Logs entry.

These are billed as usual: your program resending requests or looping, a key used by someone else because it was not kept safe, and a request you disconnected from after it had already completed upstream.

How to apply

• Apply by private message to an admin, as described in Feedback and contact, with your account email, the top-up order number and the amount.
• We check your top-ups and usage, confirm the refundable amount, then issue the refund. Refunds go back to the original payment method only.
• After a refund, that amount is deducted from your balance; your account and API keys keep working.

Payment disputes

If you have a question about a charge, contact us first. If you file a chargeback with your bank or payment platform without contacting us, we suspend the account while the dispute is handled; if the dispute fails, we deduct the amount and the platform's dispute fee from your balance.

Privacy notice

What we collect

• Account information: your email, username, and the basic profile a third-party account provides when you sign in with it.
• Request records: each request's time, model, token counts, cost, duration, source IP and session identifier; the request's structure, such as its size, upload time, the number of messages, tools and images, the size of a structured-output schema and the thinking settings, without any text; and the error message the upstream returns, which can quote part of your request. These are used for billing, troubleshooting, and keeping a session on the same upstream account.
• Payment records: order number, amount and payment status. Payment is handled by the payment provider; we never see your payment account details.
• Site analytics: the website, docs and console use Google Analytics to count the pages visited, referrers, devices and approximate region, and whether a sign-up or top-up completed (with the order number and amount for a top-up), so we can see how the site is used. It recognizes returning visitors with a browser cookie and never includes your request content.

Request content

Request content is forwarded to Anthropic for processing; how Anthropic handles it is described in its privacy policy. We do not store the text of ordinary requests' prompts or the model's replies, except in the following cases (effective November 3, 2026):

• Safety checks: to prevent use that violates the acceptable use policy, such as distillation and bulk scraping of model output, pornographic content, malware and cyberattacks, jailbreaks and reverse engineering, and to protect the service and other users, we check requests and replies automatically. Requests and replies that trigger a check are kept for human review for up to 30 days. When a violation is confirmed and the account is restricted because of it, they are kept until the appeal period has ended and the case is closed.
• Error diagnosis: when the upstream rejects a request as malformed, its body is kept for 7 days, with long text shortened.
• Troubleshooting you agree to: when you contact us about a problem and agree to it, we keep the request content of the API key you name for an agreed period, usually 30 minutes, and store it for 7 days.

Only authorized operators can read this content. It is deleted automatically when its period ends, and copies in backups are kept for up to 14 more days. It is used only for the purposes above and never to train models.

Who we share with

We do not sell your data. We give third parties only the information needed to provide the service (Anthropic processing requests, payment providers handling payments, email providers sending codes and notices, Google Analytics measuring site visits), or when the law requires it.

Retention and deletion

Request records are kept for as long as billing and troubleshooting need them; request content is kept for the periods above. When you close your account we delete your account information, except records we must keep for legal or financial reasons.

Contact us

For questions about this page, or requests about refunds, your account and data, message an admin privately as described in Feedback and contact.