I check my balance before opening Claude Code

A small balance check comes before the first prompt

Claude Code lets you work with an AI coding assistant from a terminal, the text-based application where you type instructions to your computer. It can help explain unfamiliar code, investigate errors, and make changes to a project. You do not need a powerful laptop to run the AI model locally, because the model runs on remote servers. You do need an internet connection and a supported operating system.

For a student, the first useful habit is checking the budget before starting. API access is metered: sending a request and receiving an answer uses tokens, which are pieces of text. A personal API key identifies the account paying for that usage. It is a credential, not a free-access pass.

Keep the coding tool separate from the account paying for it

Claude Code is the tool on your laptop. Your API provider supplies access to the model and records the bill. Installing the tool does not automatically connect those two parts, and a chat subscription should not be assumed to cover API usage.

MyRelay offers a personal, pay-as-you-go relay with one key and one budget across supported models. It works with Claude Code and shows the tokens and cost for every request. If that arrangement suits your needs, create a MyRelay account and check the current pricing before adding funds. Start with an amount you would be comfortable spending on a short learning session, rather than funding a whole semester immediately.

Install Claude Code using instructions for your laptop

Use the official Claude Code installation instructions for your operating system. Installation methods and system requirements can change, so avoid copying an old tutorial without checking it. On a school-managed laptop, first confirm that you are allowed to install developer tools and connect them to an external AI service.

After installation, open a fresh terminal and check that Claude Code starts. If it does not, resolve the installation problem before entering payment credentials. Keeping installation and authentication separate makes troubleshooting less confusing: you can tell whether the laptop cannot find the tool or the tool cannot reach your provider.

Connect your personal key without exposing it

In your MyRelay account, find the API key and the current Claude Code setup instructions. The connection needs both a credential and the correct service address. MyRelay lists its API base as https://api.myapirelay.com, but follow its Claude Code instructions for the exact endpoint and authentication settings rather than borrowing settings from another coding tool.

Those instructions may ask you to set environment variables. These are named settings that an application reads when it starts. Enter the values using the recommended method for your operating system, then reopen the terminal if instructed. Check that Claude Code is using the intended provider and billing route before doing real work.

Treat the key like a password. Do not paste it into a prompt, commit it with coursework, or include it in screenshots. If it leaks, revoke or replace it through your provider before continuing.

Make the first task deliberately small

Open a small practice project containing no private information. Ask Claude Code to explain one short function without changing anything. Choose a supported model whose current price fits your budget; Claude Haiku 4.5 is one option to check on MyRelay's menu. Use the provider's documented model identifier rather than guessing from its display name.

After the answer, check MyRelay's request record for tokens and cost. This confirms that usage is reaching the account you intended. An authentication or model error is a reason to check the setup, not repeatedly retry with different secrets.

Review the cost before making the task bigger

Long conversations, large files, and repeated attempts can increase usage. Keep requests narrow, avoid sharing unnecessary project content, and review proposed edits before accepting them. Use version control or keep a backup so you can undo changes.

Check any available spending controls, but distinguish a warning from a hard limit. Finish your first session by reviewing the total cost. A small, understood bill is a better starting point than an ambitious task whose price you only discover afterward.