Lewati ke konten

Produk··2 menit baca

BYOK or BYOA? Bringing the AI Access You Already Pay For

Bring a static API key, or connect a subscription account with OAuth. How each one works in Pecutin, and how its usage stays apart from your billed cost.

Tim Pecutin

Read in English

Many teams do not start from zero. They already pay for an API key at one provider, or for a subscription seat that includes model access. Rebuilding that access from scratch just to put a gateway in front of it would waste money.

Two ways to bring what you have

BYOK (bring your own key) is for static API keys. You paste a key from a provider you already pay, and requests sent through Pecutin with your sk-pc-… key can use it.

BYOA (bring your own account) is for subscription accounts that sign in with OAuth instead of handing out a static key. Supported accounts include Claude, Codex, Gemini, Grok, and Antigravity. You authorize once in the console, and the account becomes an upstream you can route to.

What stays the same

The point of both is that nothing downstream has to change. A BYOK or BYOA upstream is turned into a provider entry like any other, so a request takes the same path: your key is checked, routing picks an upstream, the response comes back, and the request is recorded.

That means the controls you already set keep working:

  • Routing rules can send some tasks to your own upstream and others to a paid provider.
  • Quotas and rate limits per key still apply.
  • Every request still appears in your logs.

What is different: who pays

When a request runs on your own key or subscription, the provider bills you there, not Pecutin. So that usage is shown separately from the cost deducted from your rupiah balance. You can see how much ran on your own upstream without it being mixed into billed spend.

When to use which

Use BYOK when your provider gives you a normal API key and you want to keep using a contract or credit you already have. Use BYOA when the access you pay for is a subscription seat rather than a key. Many teams use both: a subscription for coding agents, and pay-per-request for production traffic.

Pertanyaan yang sering diajukan

Do I still need a balance if everything runs on my own key?

Requests on your own upstream are billed by that provider. A balance is only deducted for requests that run on paid upstreams through Pecutin.

Can I mix my own upstream with paid providers?

Yes. Routing rules decide per request, so you can prefer your own upstream and fall back to a paid provider, or the other way around.

Berhenti mengurus akun satu per satu. Mulai dari satu kunci.