Where to Get Help After Your First Failed API Call

Introduction

Your first failed API call can be frustrating, but it's a common part of integrating with any new service. This guide walks you through the support channels and self-serve resources available for a no-KYC aggregated LLM API, and explains what information to gather before seeking help.

Self-Serve Resources

Before reaching out for support, check these resources—they often contain the answer you need.

• Documentation: The official docs usually cover authentication, request formats, error codes, and rate limits. Start here for quick answers.
• API Reference: Detailed endpoint descriptions, parameters, and example requests/responses can help you spot mistakes in your code.
• FAQ / Troubleshooting Page: Many common issues (e.g., invalid API key, insufficient balance, model unavailability) are addressed here.
• Status Page: Check if there's a known outage or degradation affecting the service.
• Community Forum or Discord: Other users may have encountered and solved similar problems. Search before posting.

Support Channels

If self-serve doesn't resolve your issue, use these channels:

• Email Support: Typically the primary channel for account-specific or billing issues. Include detailed information (see below).
• Discord / Community Chat: Good for quick questions and real-time help from community members or staff.
• GitHub Issues: If the API has an open-source component or public issue tracker, report bugs there.
• Social Media: Some services respond to direct messages on platforms like Twitter, but avoid sharing sensitive information publicly.

What Information to Gather

When asking for help, provide as much relevant detail as possible to speed up resolution. Include:

• Your API Key (but never share it publicly): Support may ask for a portion or a hash to identify your account. Never post your full key in public channels.
• The Exact Request: Include the endpoint, HTTP method, headers (redact sensitive values), and body you sent.
• The Full Error Response: Copy the entire error message, including status code and any error codes or messages.
• Timestamp: When the error occurred (with timezone).
• Model Name: Which model you were calling.
• Steps to Reproduce: If possible, describe the sequence that led to the error.
• What You've Tried: Mention any troubleshooting steps you've already taken.

Common Causes of Failed API Calls

Understanding typical failure reasons can help you self-diagnose:

• Authentication Errors: Invalid or expired API key, or missing Authorization header.
• Insufficient Balance: Your account may need a top-up. With this service, you top up using USDC on Base—no KYC required.
• Invalid Request Format: Malformed JSON, missing required parameters, or incorrect content type.
• Model Unavailable: The requested model may be temporarily down or deprecated.
• Rate Limiting: You may have exceeded your plan's rate limits. Check the docs for details.
• Network Issues: Connectivity problems between your server and the API endpoint.

How Billing and Credits Work

If your error relates to billing or credits, here's a quick recap:

• You pay the official model price multiplied by 1.3.
• Key contributors are credited the official price multiplied by 1.1 (or 1.2 for premium models) in USDC.
• Top-ups are made with USDC on Base, no KYC.

If you suspect a billing discrepancy, gather your transaction history and contact support.

Best Practices for Getting Help

• Be concise but complete: Provide all necessary details without overwhelming.
• Stay polite: Support staff are there to help; courteous requests get better responses.
• Use the right channel: Use email for account-specific issues, community chat for general questions.
• Search first: Your question may already be answered.
• Follow up: If you don't hear back, a gentle reminder is okay.

Conclusion

A failed API call is usually easy to fix once you know where to look. Start with self-serve resources, gather the right information, and use the appropriate support channel. With a bit of patience, you'll be back to building in no time.