Estimated reading time: 5 minutes · Last updated:
Oracle announced on September 24, 2026, as first reported by Oracle Blogs, that Meta Model API and Muse Code are available through Oracle Marketplace, enabling Oracle customers to procure Meta’s models and an agentic coding tool via Oracle billing and Universal Credits. Meta Model API offers an OpenAI-compatible endpoint to Meta’s Muse Spark family and serves Muse Image and Muse Voice Transcribe, while Muse Code is a terminal coding agent powered by Muse Spark that can plan, implement and validate changes across large repositories. The post was presented on Oracle’s site as a 4 minute read.
Key takeaways
- Availability: Oracle made Meta Model API and Muse Code available through Oracle Marketplace on September 24, 2026.
- Core technology: Both offerings use Muse Spark, Meta’s reasoning model family, and include Muse Image and Muse Voice Transcribe for multimodal work.
- Billing: Oracle says usage is billed per token against customers’ Oracle subscriptions and tracked in the Model API dashboard.
- Procurement: Eligible Marketplace purchases can use Oracle Universal Credits and receive consolidated billing from Oracle.
Table of contents
How availability on Oracle Marketplace changes enterprise procurement
Oracle positioned the listing as a way for customers to bring Meta’s models and agentic tooling into existing procurement and cloud-investment workflows. By listing Meta Model API and Muse Code in Oracle Marketplace, Oracle says customers can use Oracle Universal Credits where eligible and receive consolidated billing instead of running a separate procurement route for each provider.
That billing link matters operationally: Oracle explicitly states usage is billed per token and tracked in a Model API dashboard where teams manage API keys, invite users and monitor token consumption. For enterprises this means cost visibility is centralised in Oracle’s subscription model rather than split across vendor invoices.
The Marketplace route does not change the technical interfaces. Oracle says the Meta Model API can serve as a direct replacement for OpenAI and Anthropic SDKs and the related agent command-line tools, so migration frequently comes down to swapping the base URL and credentials rather than rewriting SDKs.
What Muse Code and Muse Spark offer developers for complex projects
Muse Code is presented as a terminal coding agent powered by Muse Spark that handles planning, editing, debugging and result validation across large codebases. Oracle frames the workflow as agent-led: a developer supplies an objective and Muse Code outlines steps, performs edits and verifies the outcomes.
For long-horizon and large-repository tasks, Muse Code can spawn teams of agents to parallelise work and manage multiple concurrent tasks. Oracle frames that agent orchestration as a way to accelerate project progress while keeping developers in control of outcomes and validation steps.
Muse Spark is the reasoning model family behind Muse Code and is also the backbone of Meta Model API; Oracle points to Muse Image for image generation and Muse Voice Transcribe for speech-to-text as other model capabilities available through the same API surface. The implication is teams can combine coding, multimodal understanding and complex reasoning from one provider endpoint.
Compatibility, management and the Model API dashboard
Meta Model API is presented as a simple, scalable endpoint that is OpenAI-compatible, meaning teams can point existing OpenAI or Anthropic clients at a new base URL and set a key to begin testing. Oracle points to a Model API dashboard where teams can test prompts in a playground before writing production code and monitor token usage against their Oracle subscription.
The dashboard is the control plane Oracle highlights: developers can create API keys, add teammates to a centrally managed account, and monitor token consumption that is billed through Oracle. Oracle also notes the Model API delivers Muse Image and Muse Voice Transcribe alongside Muse Spark, allowing multimodal development without separate vendor integrations.
For teams that prefer packaged tooling rather than direct model calls, Oracle positions Muse Code as the ready-made CLI agent or pipeline alternative. The marketplace listing therefore supports two adoption paths: direct API integration for apps and SDKs, and an agent-first route via the Muse Code terminal experience.
| Offering | Best for | Access method | Billing |
|---|---|---|---|
| Meta Model API | Direct model access for apps and SDKs | OpenAI/Anthropic-compatible API endpoint; Model API dashboard | Billed per token; Oracle Universal Credits eligible |
| Muse Code | Terminal coding agent for multi-step engineering tasks | CLI agent powered by Muse Spark; available via Marketplace | Billed per token via Oracle subscription |
Two-sided case for adoption
The case for
- Streamlined procurement: Marketplace and Oracle Universal Credits can reduce procurement friction and consolidate billing for customers that already use Oracle Cloud.
- Easier migration: OpenAI-compatible endpoints lower integration effort for teams that already use OpenAI or Anthropic SDKs and agent CLIs.
The case against
- Per-token billing introduces variable costs that customers must model in their Oracle subscription to avoid unexpected spend.
- Some teams will prefer direct model control and custom governance rather than agentic workflows, so Muse Code may fit some engineering teams better than others.
What to be careful about
- Per-token billing can create unanticipated operating costs if usage patterns are not profiled against Oracle subscription terms.
- Relying on an agentic tool for broad engineering tasks requires explicit validation steps; Oracle emphasises keeping developers in control but operational practice must enforce those checks.
- Consolidated billing via Oracle Universal Credits still requires mapping marketplace usage to existing cloud commitments and cost centres.
The bottom line
Listing Meta Model API and Muse Code on Oracle Marketplace ties Meta’s Muse Spark models and an agentic CLI into Oracle’s procurement and billing flows. For teams already invested in Oracle Cloud, the Marketplace path promises consolidated billing and easier procurement via Oracle Universal Credits, while OpenAI-compatible endpoints reduce integration work. Operationally, organisations should model per-token costs, clarify data residency and SLA terms, and define validation gates for any agent-driven workflows before rolling Muse Code into production.
What to watch
- Check the Oracle Marketplace listing for Meta Model API and Muse Code for updated pricing and Universal Credits eligibility; no date has been set.
- Watch for documentation updates to Muse Code and Muse Spark in the Oracle listing to clarify enterprise deployment and governance options; no date has been set.
Frequently asked questions
What is Muse Code and what can it do for my team?
Muse Code is Meta’s terminal coding agent powered by Muse Spark; Oracle describes it as a tool that can plan work, make code changes, debug and validate results across large repositories and long-running workflows.
How is usage billed when I buy through Oracle Marketplace?
Oracle says usage is billed per token against the customer’s Oracle subscription and tracked in the Model API dashboard; eligible purchases can use Oracle Universal Credits for consolidated billing.
Does Meta Model API require changing my SDKs?
Oracle says the Meta Model API is compatible with OpenAI and Anthropic SDKs and agent command-line tooling; in many cases teams only need to reconfigure their existing client to use a new endpoint and API key instead of overhauling SDK code.
Related reading
This article is information, not financial advice. Anyone acting on it should do their own checks.
