How to Get an AI API Key (Step-by-Step Guide)

By the Zylo team · Updated June 8, 2026 · 4 min read

Getting an AI API key is the first step toward integrating large language models into any application, script, or workflow. An API key is a credential that authenticates your requests to a model provider — without one, calls to endpoints like https://api.zyloai.net/v1 will be rejected. If you are new to the concept, what AI API keys are and how they work is worth reading before proceeding. The process described here takes under five minutes and requires no credit card, making it one of the lowest-friction entry points to frontier AI available today.

Create your account at the console

Navigate to the Zylo console at console.zyloai.net and sign up with either an email address or a Google account. No credit card is required at this stage. After you verify your email via the one-time code Zylo AI sends, your account is active and provisioned on the free Basic plan automatically. The Basic plan gives you approximately 200,000 tokens and 7,200 requests per day at no cost, with a rate limit of 10 requests per minute, so you can begin building and testing immediately. This is a real allowance on Basic-tier models — lightweight, capable models suitable for a wide range of tasks — not a trial that expires after a fixed number of days. Once your account exists you can explore the full model catalogue to understand which models are available under the Basic plan and which require a paid plan with credits. The whole flow is intentionally short because the goal is to get you to a working first call quickly: there is no sales step, no credit-card wall, and no waiting period for approval. Once the account exists you already have everything you need to authenticate a request, and the only decision left is which model to call. If you are evaluating several providers at once, this low-friction path also makes Zylo easy to slot into a side-by-side test, since you can have a live key in hand within a minute or two and compare real responses rather than marketing claims.

Copy your API key from the dashboard

After signing in, open the dashboard and locate the API key section. Zylo AI displays your key once in plaintext so you can copy it; subsequent visits show only a masked version for security. Copy the key to a secure location such as a password manager or an environment variable in your deployment environment before closing the tab. If you lose access to the key or suspect it has been exposed, you can rotate it at any time from the same dashboard screen — rotation invalidates the old key immediately and issues a new one. The free AI API key guide covers this rotation workflow in more detail, including what happens to in-flight requests when you rotate. Never store the key in version control or client-side browser code; treat it with the same care as a database password.

Use the key with any OpenAI-compatible client

Because Zylo AI exposes an OpenAI-compatible interface, any library or tool that already speaks the OpenAI API format will work without modification beyond two configuration values: set the base URL to https://api.zyloai.net/v1 and set the API key to the credential you copied. In Python, that means passing base_url and api_key to the openai.OpenAI client constructor. In Node.js the pattern is identical with the openai npm package. Coding assistants such as Cursor, Cline, aider, and Continue accept these two fields in their settings panels. You then select models by their bare identifier — for example claude-opus-4.8 or gemini-2.5-flash-lite — and the gateway routes the request to the correct provider automatically. The developer quickstart includes copy-paste snippets for the most common clients.

Keep your key secret and know its limits

The free Basic plan covers Basic-tier models only; premium models from Anthropic, OpenAI, and Google require a paid Go plan or higher with credits loaded. Credits are purchased separately and carry a flat 25 percent platform fee at the time of purchase — there is no per-token markup on top of the base model rate. Because the key grants access to your credit balance, leaking it is a financial risk as well as a security one. Set it as an environment variable (for example ZYLO_API_KEY) and read it at runtime; never hardcode it in source files. When your needs grow beyond the Basic plan — whether for higher daily token limits, access to models such as gpt-5.5 or claude-opus-4.8, or features like web search and code execution — upgrade from the console billing page. The key itself does not change on upgrade, so no client reconfiguration is needed.