Compare approaches

One gateway, or one integration per provider?

You can always integrate each model provider directly. This page lays out, dimension by dimension, what Artany API takes off your plate when you route the same models through one contract instead.

Dimension	With Artany API	Direct integrations
Integration surface	One REST contract for the whole catalog — parse the job object once.	One SDK / API shape per provider, each with its own auth and response format.
Adding a new model	Change the model id string; request and response shape stay identical.	New integration work per provider: credentials, request mapping, result parsing.
Billing	One Credit balance, fixed catalog prices, one ledger across all models.	Separate accounts, currencies, invoices, and rate cards per provider.
Failure handling	Hold-and-refund built in: failed jobs refund automatically, idempotency keys prevent double charges.	Retry, reconciliation, and refund logic implemented by you, per provider.
Result delivery	Outputs mirrored to our CDN with stable URLs.	Provider-hosted URLs with varying expiry and availability policies.
Team management	Shared team wallets, roles, invites, and per-workspace keys in one console.	Per-provider seat and key management, if offered at all.

Direct integration remains the right call when you need a provider-exclusive feature the public contract doesn't expose — this comparison describes our own platform only and makes no claims about specific third-party services.

The same models, one contract

Every family below is available today behind the same request and response shape — switching between them is a one-line change.

Try it against your current setup

Run the same prompt through the playground on any model page, or point your coding agent at /llms.txt and let it wire up the integration.

Browse models Read the docs

One gateway, or one integration per provider?

The same models, one contract

GPT Image

Kling

Nano Banana

Seedance

Seedream

Veo

Z Image

Try it against your current setup