← Voltar aos guias

Your First Claude API Call with 59API in 5 Minutes

Why use a relay for your first Claude request?

Claude is easy to call once authentication, billing, and the endpoint are configured, but a direct Anthropic setup is not always the most convenient or affordable starting point. You may need an eligible payment method, regional access, and separate accounts for different model providers. A relay such as 59API gives you one pay-as-you-go account for Claude and GPT models, using the compatible base URL https://api.59api.com.

The important distinction is model quality. 59API provides native, official-quality models rather than a cheaper model that has been silently downgraded. Depending on what is currently available in your account, you can choose Claude Opus, Sonnet, Haiku, or Fable for different combinations of reasoning ability, speed, and cost.

Five-minute setup

1. Create an account and add credit. Sign up for 59API, generate an API key, and add a small balance. Pay-as-you-go access lets you test a real workflow without committing to a large subscription. Keep the key in an environment variable rather than placing it directly in source code.

2. Choose a model ID. Open your 59API model list and copy the exact Claude model identifier shown there. Model names and versions can change, so copying the current ID is more reliable than guessing one from an old tutorial.

3. Send a standard Messages request. The following request uses the familiar Anthropic API format. Replace the model value with the ID from your dashboard:

Terminal command: curl https://api.59api.com/v1/messages -H "x-api-key: $CLAUDE_API_KEY" -H "anthropic-version: 2023-06-01" -H "content-type: application/json" -d '{"model":"YOUR_MODEL_ID","max_tokens":200,"messages":[{"role":"user","content":"Explain API relays in one sentence."}]}'

A successful response should contain the generated text, usage information, and the selected model. Start with a low max_tokens value while testing so an accidental loop or oversized prompt does not consume more credit than expected.

4. Move the call into your application. The Anthropic SDK can generally be configured with a custom base URL, while the OpenAI SDK works by setting its base_url to https://api.59api.com/v1 and supplying your 59API key. This makes 59API useful if your project already supports Claude Code, Codex, or OpenAI-compatible clients. Check the SDK's current configuration names before deployment, because they differ slightly between languages and versions.

59API versus calling Anthropic directly

• 59API pros: one low-cost, pay-as-you-go balance; access to Claude and GPT models through one relay; compatibility with Claude Code, Codex, Anthropic-style requests, and OpenAI SDKs; and a referral rebate that can reduce future costs. It is a practical choice for prototypes, scripts, and developers comparing providers.
• 59API cons: billing and account support pass through a third party; the exact model catalogue and identifiers are controlled by the relay; and you should review current retention, privacy, rate-limit, and uptime policies before sending sensitive production data.
• Direct Anthropic pros: a first-party account, direct vendor support, and the most straightforward relationship for teams that need enterprise contracts or tightly controlled compliance terms.
• Direct Anthropic cons: you manage Anthropic billing and access separately, and costs or availability may be less convenient for casual experimentation or multi-provider applications.

Practical checks before production

Protect the API key with server-side environment variables, set request timeouts, log request IDs and token usage without logging private prompts, and add retry handling for temporary rate-limit or server errors. Compare Haiku for fast classification, Sonnet for general application work, and Opus for demanding reasoning; use a cheaper model when the task does not justify a larger one.

For a first request, 59API is attractive because changing the endpoint and key is usually enough to test Claude without rebuilding your application. Sign up when you are ready to try the request, start with a small balance, and verify both the response and usage record before expanding the integration.

Preços · Docs