Skip to content

API subscription

01

Oro API

FREE
$8/ month

120 Oro Balance credits monthly

Connect supported provider keys and run those providers from the Oro canvas while keeping every source and decision attached.

  • Complete Oro workspace
  • Supported BYOK provider connections
  • Provider and model choice at the node
  • Provider charges remain on your account
  • No Oro Balance spent on BYOK runs
  • Included credits reset monthly · no Rollover
  • Purchase Top-up · $10 for 1,000 credits
  • Purchased credits expire after 12 months
Request API beta access

Oro Enterprise

Bring the provider relationship you already have into a canvas built for the work around it.

Join Oro today with our Starter plan.

Request Beta Access

Your API keys. Inside a better system.

Pricing / explained

The boundaries are part of the product.

01What does Oro API cost?
02How do my keys enter the workflow?
03Does Oro Balance pay for my API requests?
04Who controls provider pricing and availability?
05Does the subscription meter local work?
06How does Oro Balance work on this plan?
07Can I subscribe today?

Included / without meter

One subscription connects the canvas to the providers you choose.

01

Bring your own keys

Use supported provider accounts you already control instead of buying a second generation allowance.

02

Choose per workflow

Select the provider at the node where the generation happens. The rest of the graph remains provider independent.

03

Preserve the context

Keep prompts, references, intermediate decisions and resulting images visible in one production system.

04

Keep billing explicit

Provider charges stay on the account you connected. Oro does not silently convert BYOK work into Balance usage.

05

Keep a managed path available

Use 120 included monthly Oro Balance credits for your generations. The allowance resets each month without rollover.

Oro / Spending CheckSpending controls image coming soon

What the subscription covers

Oro organizes the run. Your provider supplies the model.

Oro API separates the subscription, managed Balance and your provider relationship. BYOK requests are priced and billed by the connected provider. Managed requests use the plan’s included Oro Balance when you choose to do so.

  1. 01

    Connect a supported provider account once, then choose that provider from compatible Oro nodes.

  2. 02

    Review the provider, model and available cost information before a paid request leaves the canvas.

  3. 03

    The provider charges your provider account directly. Oro Balance is never deducted from a BYOK run.

  4. 04

    The plan includes 120 Oro Balance credits each month. Included credits reset monthly with no rollover.

  5. 05

    Our top-up is $10 for 1,000 purchased credits. Purchased credits stay separate, survive plan changes and expire 12 months after purchase.

Two explicit paths

Two paths. Never one hidden bill.

Oro API is the ordinary plan that authorizes both execution sources. BYOK uses your provider relationship and provider currency. Generations outside personal API keys can use Oro Balance credits.

Oro API / $8 monthly

Your provider account

Subscribe to Oro API, connect a supported key and let that provider bill your account for each request.

Oro API / managed allowance

Managed generation

Choose a supported model, review the estimate and spend from the plan’s 120 monthly Oro Balance credits or from Top-up Oro Balance.

Product views / planned

The connection should remain visible.

These captures will show the exact places where a provider is connected, selected and confirmed inside Oro.

Settings capture placeholderConnect a supported provider

A focused view of provider credentials and the boundary between Oro and the connected account.

01Settings capture placeholder

Connect a supported provider

A focused view of provider credentials and the boundary between Oro and the connected account.

Workflow capture placeholderChoose the provider where the work happens

A real generation node showing provider selection, model controls and the decision before a request runs.

02Workflow capture placeholder

Choose the provider where the work happens

A real generation node showing provider selection, model controls and the decision before a request runs.