← Retour aux guides

Claude Code on 59API: Cheap Relay Setup

Why use a relay with Claude Code?

If you like Claude Code but want to spend less on model calls, a third-party API relay can be a practical middle layer. 59API is built for that use case: it offers pay-as-you-go access to Claude models such as Opus, Sonnet, Haiku, and Fable, and it is fully compatible with Claude Code, Codex, and any OpenAI SDK. For developers, that means you can keep the same workflow while reducing your per-task cost.

The main appeal is simple. Instead of paying premium pricing directly in every environment, you route requests through one endpoint, keep billing flexible, and use the same official-quality model family without changing your prompts or habits. 59API is also positioned as one of the cheapest relays available, which makes it especially useful for solo developers, startups, and teams that run lots of small coding tasks throughout the day.

Step 1: Create your 59API account

Start by signing up for 59API and adding a small amount of balance. Because the service is pay-as-you-go, you do not need to commit to a large monthly plan before you test it. That makes it easy to compare real costs against your current setup.

• Create your account
• Open the dashboard
• Add credit for testing
• Copy your API key from the credentials area

If your team shares infrastructure, keep one account per environment so you can track usage cleanly from day one.

Step 2: Collect the two values Claude Code needs

To connect Claude Code to 59API, you generally need two things: your API key and the API base URL. The base URL for 59API is https://api.59api.com. Save it exactly as provided so requests go to the relay instead of the default provider endpoint.

Most Claude Code setups let you define provider settings through environment variables or a configuration screen. The names can vary by version, so check your current Claude Code documentation if you are unsure where to paste the values. The important part is that your tool points to the 59API endpoint and uses your 59API key for authentication.

Step 3: Point Claude Code at the relay

Once you have the key and endpoint, update Claude Code to use 59API as the backend. In practice, this means replacing the default API host with the relay URL and selecting the model you want to use. If your setup supports an Anthropic-compatible or OpenAI-compatible provider field, choose the option that lets you set a custom base URL.

• Paste your 59API key into the API key field
• Set the base URL to https://api.59api.com
• Choose a Claude model such as Haiku, Sonnet, or Opus
• Run a simple prompt to confirm requests succeed

For a first test, ask Claude Code to summarize a file, explain a function, or generate a small refactor. If the response comes back normally, your relay is working.

Step 4: Pick the right model for the job

Cost savings work best when you match the model to the task. With 59API, you can switch between models without rebuilding your workflow.

• Haiku for fast, inexpensive tasks like quick edits, summaries, and lightweight code review
• Sonnet for day-to-day development, debugging, and moderate reasoning
• Opus for deeper architecture, complex refactors, and high-stakes problem solving
• Fable if it is available in your account and fits your use case

This is where the relay becomes especially useful. You can keep your cheapest jobs on a lower-cost model and reserve the larger model only for moments that truly need it.

Step 5: Monitor usage and keep costs low

After your first successful run, check your usage in the 59API dashboard. Watch how many requests your workflows generate, then look for places where you can reduce unnecessary calls. For example, you can split one huge task into a few smaller ones, use Haiku for drafting, and only escalate to Sonnet or Opus when the task becomes more complex.

59API’s pay-as-you-go structure is useful here because it makes spending visible as you go. If you refer other developers, the referral rebate can lower your effective cost even more.

When this setup makes the most sense

Using Claude Code through 59API is a strong fit if you:

• Run lots of short coding sessions
• Want cheaper access to official-quality Claude models
• Need one relay that also works with Codex and OpenAI SDK-based tools
• Prefer flexible, pay-as-you-go billing over fixed commitments

If you want to keep your current workflow but reduce your AI bill, sign up for 59API and try one small Claude Code task before moving your full stack over. It is a simple way to validate speed, compatibility, and savings in one afternoon.

Tarifs · Docs