Changelog

What shipped.

Every release that changes what you can build — in plain English, newest first. Breaking changes are always called out here and in the versioning policy.

PricingSeptember 15, 2026

Founding Members get the starter credit by status; every starter credit lasts 30 days

  • •Founding Members — a Muso account status — now receive the $25 starter credit automatically when they add a card, with no account cap and no deadline.
  • •Every $25 starter credit is good for 30 days from the day it is granted. Whatever you haven't used by then is removed; credit you purchased is untouched.
  • •Everyone else: the first-200-accounts-through-Oct-1 founding offer is unchanged.
PricingAugust 6, 2026

Plans: Build and Scale at the plan rate from call 1

  • •Two monthly plans — Build at $500/mo (25,000 calls included) and Scale at $3,000/mo (150,000 calls included) — sell the $0.020 per-call rate from your first call. Plan money counts toward usage, so you only ever pay the difference. Current grid on /pricing.
  • •Prepaid credits: load a balance and usage draws it down — your card is charged only when you load. You'll never pay more than you load.
  • •Welcome and founding credits: a $5 welcome credit when you add your card, and a founding credit that brings new accounts to $25 total for the first 200 accounts.
APIJuly 12, 2026

Publishable keys, embeddable widgets, hosted MCP

  • •Publishable keys (mpk_) — a browser-safe, read-only key type for embedding Muso data in your website. Create and manage them from the console Keys page; they can only read profile data on a dedicated embed surface and can never touch the paid catalog API.
  • •Embed surface: GET api.platform.muso.ai/embed/v1/profile/{id} (+ credits, charts, collaborators) with CORS enabled — callable directly from the browser with a publishable key.
  • •@muso-ai/embeds — drop-in Profile Card and Roster widgets: a <script> embed for any website, styled on the Muso design system. The React component ships in the same package, which is not yet on npm — use the hosted script today.
  • •Hosted MCP endpoint — mcp.muso.ai now serves the platform Data API over the Model Context Protocol (Streamable HTTP), so AI clients like Claude can use your key without running a local server.
  • •muso CLI — a public command-line client (login, profile, credits, search, usage) entered review; install channel announced when it lands.
PricingJuly 10, 2026

Pure pay-as-you-go pricing with usage tiers

  • •One metered plan: add a card, start with $5 in credits, pay per call on marginal volume bands — no base fee, no trials, no plans to pick.
  • •Usage tiers (Start / Build / Scale) govern throughput and monthly spend caps — the per-call rate is the same at every tier. Tiers grow automatically with usage history, or upgrade instantly with a monthly commitment that credits toward your usage.
  • •Per-profile chart analytics (positions, scores, popularity) are available today in the metered API. Platform Analytics ($3,000/mo minimum) — system-wide, cross-catalog analytics with Scale-tier throughput — is rolling out.
  • •The console Limits page shows your tier, rate limits, spend cap, and self-service upgrades.
PlatformJuly 9, 2026

The platform site is public

  • •platform.muso.ai marketing, pricing, and documentation are publicly reachable (the developer console still requires sign-in).
  • •api.platform.muso.ai is live — the dedicated API host documented in every quickstart.
  • •The site now runs on the Muso design system (Octave) end-to-end.
SecurityJuly 8, 2026

Legal terms, transactional email, social sign-in

  • •Terms of Service and the Data License Agreement published at /legal — including the live-use (no caching/storage) license and the enterprise storage carve-out.
  • •Verification, password-reset, and team-invitation emails are delivered (previously log-only).
  • •Sign-in with Google, Apple, and Facebook verified end-to-end on login.muso.ai.
PlatformJuly 6, 2026

Self-serve launch surface

  • •Sign up with your Muso account (login.muso.ai), add a card, and get a working API key — provisioned at the gateway with metering from the first call.
  • •Team workspaces: invite members, roles (owner/admin/member), key visibility gated by role, removal rotates the workspace key.
  • •Docs overhauled: real endpoint paths, runnable quickstart, x-api-key auth everywhere, try-it panel wired to the live API.

Current operational state lives on the status page (machine-readable at /api/status).