Get your EvoLink API key

Free

The model access layer for AI teams shipping to production.

FreeFree tier

Inputs: text, image, video, audioOutputs: text, image, video, audio

Type

Open Source

Company

EvoLink

Visit Website GitHub (40 stars)

About Get your EvoLink API key

EvoLink is a model access layer that provides a unified API for over 170 AI models from 30+ providers, including LLMs (text), image generation, video generation, and audio models. Built for production teams, it offers drop-in compatibility with OpenAI, Anthropic, and Google SDKs – most existing code works by simply changing the base URL and API key. EvoLink features transparent pay-as-you-go pricing (1 credit ≈ $0.0147) with no hidden multipliers, real-time usage dashboards, and automatic provider failover for 99.9% uptime. It supports async operations, webhooks, retries, and per-request cost tracking. Sign up is free with no credit card required, and you only pay for what you use via credit top-ups (minimum $10). EvoLink is designed for developers shipping production apps, teams scaling AI features, and media generation workflows requiring reliable, cost-controllable API access.

Key Features

One API for 170+ models from 30+ providers (LLM, image, video, audio)

Drop-in compatibility with OpenAI, Anthropic, and Google SDK formats

Transparent pay-as-you-go pricing with per-model rates visible before use

99.9% observed uptime with automatic provider failover

Async patterns, webhooks, retries, and provider fallback for production workloads

Real-time usage dashboard with per-key analytics and itemized cost breakdown

Secure proxy with TLS 1.3, no prompt/response storage, and per-key usage tracking

Pros & Cons

Pros

Unified API eliminates the need to manage multiple provider keys and SDKs
Transparent pay-as-you-go pricing with no hidden multipliers or surprise costs
High uptime and automatic failover when upstream providers degrade
Free to start with no credit card required, only pay for actual usage
Supports production-critical features like async operations, webhooks, and retries
Real-time dashboard provides per-request cost visibility and itemized records

Cons

Dependency on a third-party API layer may introduce additional latency and reliance on EvoLink's infrastructure
Limited to models that EvoLink supports; some cutting-edge or niche models may not be available immediately
Credit-based billing requires monitoring and top-ups (minimum $10) to avoid service interruptions
May be more expensive than direct provider pricing for very high-volume usage, though savings are shown for many models

Best For

Shipping production AI applications with predictable behavior and clear costsScaling AI features across teams with model comparison and routing by quality or costMedia generation workflows requiring reliable async APIs for video, image, and audio modelsReplacing multiple provider API keys with a single, unified API keyBuilding cost-controllable AI systems with real-time usage monitoring

FAQ

What models are supported by EvoLink?

EvoLink supports over 170 models from more than 30 providers, spanning LLMs (text), image generation, video generation, and audio models. The catalog includes models from OpenAI, Anthropic, Google, Kling, BytePlus, Alibaba, MiniMax, and others. Prices are listed per model before you call.

How does pricing work?

EvoLink uses a pay-as-you-go credit system. One credit is approximately $0.0147. You top up your balance via card, Alipay/WeChat Pay, or bank transfer (minimum top-up $10). Usage is metered per call (per token, per second, per image), and the unit price is visible on each model page. There are no hidden multipliers, and you can view real-time usage and costs in the dashboard.

Is there a free tier?

Yes, you can get started with EvoLink in minutes with no credit card required. There is no upfront cost; you only pay for the API calls you make after topping up your credits.

Is my data stored or used by EvoLink?

EvoLink acts as a secure proxy. Your prompts and responses are not stored. All traffic is encrypted in transit with TLS 1.3. Audit logs cover compliance metadata, not request content. API keys are per-key and can be rotated, and usage is tracked per key without accessing the content.