Oracle Adds Meta’s AI Tools to Marketplace With Per-Token Billing

Oracle customers can now get Meta’s models and coding agent through an existing purchasing route. Meta Model API and Muse Code are available on Oracle Marketplace, with usage billed per token against an Oracle subscription. The September 24 announcement gives buyers another way to procure the tools, while leaving developers a choice between building with the models and using a ready-made agent.

The tools came before the Oracle listing

Meta released Muse Spark 1.3 on September 2 and made it available through Muse Code and Meta Model API. That was a model release. This announcement adds an Oracle buying route for tools that were already available through Meta.

Meta Model API gives developers access to Meta’s proprietary models for apps or agents they build themselves. Oracle says the API works with the OpenAI and Anthropic software development kits and agent command-line tools. Teams using a compatible client can change its base URL and set a key rather than replace the rest of their code.

Muse Code takes on a different job. It is a coding agent for a terminal or software pipeline, powered by Muse Spark. Oracle says developers can give it a broader objective, such as planning changes across a large code repository, debugging and checking the result. For complex projects, Oracle says it can split work among agents running in parallel.

What comes with the API

The API also serves Muse Image for image generation and editing, and Muse Voice Transcribe for speech-to-text. Oracle says the transcription service supports speaker attribution and custom vocabulary. These are capabilities available through the new Marketplace route, not separate launches announced with the listing.

Teams can use the Model API dashboard to create keys, test prompts before writing code and invite users to a managed account. It also tracks token usage, giving buyers a place to monitor spending as developers make requests.

The purchasing decision

Oracle presents the Marketplace listing as a way to buy both tools without setting up a separate procurement process for each technology. Usage goes against an Oracle subscription and appears in the dashboard. That puts purchasing and usage tracking into an existing Oracle workflow rather than requiring a team to manage a separate buying process for each tool.

A team considering the listing still needs to check the terms of the offering it intends to buy. Oracle describes per-token billing but gives no per-token rate in the announcement. The new purchasing route may simplify procurement; the announcement alone does not settle what a particular workload will cost.