Pay how you want.
Build without limits.

No. Aperture maintains its own upstream relationships with each provider. You use one Aperture key (sg-...) and we route to whichever model your code requests.

Pro subscription is best when you ship something that calls models every day. Credits suit weekend projects, prototyping, or unpredictable spikes. You can run both at once: Pro covers your daily 10K, credits soak up the overflow.

No. Once you top up, credits stay in your account until you burn them down. No 6-month or 12-month clocks.

Visa, Mastercard, and Amex via Stripe. Most cards issued in Asia work. Local payment rails (e-wallets) are not currently supported — Stripe card is the only payment path.

Requests pass through our low-latency edge (DigitalOcean SGP1) on the way to the upstream provider. We do not log prompt or response bodies — only metadata (model, token count, status, latency) for billing and analytics. Cache entries are keyed on input hash and live in Redis with the TTL of your plan.

Each plan ships with a generous daily request quota that resets at midnight UTC. Over-quota requests return HTTP 429 daily_quota_exceeded with the exact reset time. Upstream provider rate limits also apply (you'll see those as the original provider 429s, pass-through).

Subscriptions cancel anytime via Stripe portal — your plan stays active through the end of the billing month, no charge after. Credits are non-refundable once spent, but unused credits refund on request within 14 days of purchase.

Aperture exposes a single /api/v1 endpoint. Switch models by changing the model name in your request — no path changes, no new keys.

Singapore peers excellently with Indonesia, Vietnam, the Philippines, Malaysia, Thailand — and still keeps sub-100ms hops to Tokyo, Sydney, and the US west coast. For an SEA-first audience it gives the best blended latency without splitting infrastructure across regions.