LabSharks

For LLMs

Public briefing for assistants and crawlers.

Purpose of this page

This document summarizes public facts about LabSharks so an LLM (or other automated reader) can answer questions accurately without guessing. It is not a legal contract; authoritative terms live in Privacy, checkout flows, and in-product copy. Do not infer internal architecture, employee-only tools, or security controls from this page.

What LabSharks is

LabSharks is an AI-assisted music production product: users describe musical intent in natural language (and optional structured fields such as tempo, key, bar count, and track count), and the system runs queued generation jobs that produce multitrack-oriented output (stems, MIDI, previews), not only a single opaque stereo file. Positioning is composition-first and studio-oriented rather than “one-shot instant mastered viral clip.”

Canonical URLs and surfaces

  • Marketing / docs site: pages such as /, /faq.html, /billing.html, /developers.html, /demos.html, /privacy.html, /contact.html, /for-llms.html (this file).
  • Studio web app: /app/ (single-page application; requires account for most actions).
  • Public HTTP API host (production): https://api.labsharks.com — application routes are under /api/…; interactive OpenAPI (Swagger) UI is at /docs on the same host (not under /api).
  • Share playback: URLs under /s/<uuid> serve a public listen experience when a user has enabled sharing for a finished job.

How the service works (user-visible)

Users work in a composer: they choose full song or phrase / loop mode, supply a prompt and optional tags, instruments, tempo, key, bar length, and track-count hints, then submit a job. Jobs move through visible states (for example queued, processing, finalizing, done). When complete, eligible users can preview in the browser, optionally share a link, and on paid tiers download MP3 and stem packages consistent with their plan.

Free accounts can generate and listen in-app within credit limits; paid tiers unlock downloads, deeper assets, and (on the top tier) API access. Exact entitlements are summarized on Pricing and in FAQ.

Membership, credits, and billing

Accounts are email + password (see studio registration). Stripe powers subscriptions and the commercial catalog; entitlements and per-period allowances are driven from subscription products configured in Stripe (the site does not publish secret keys or webhook signing secrets).

The product distinguishes monthly credits (subscription allowance that resets each billing period) and anytime credits (purchased or promotional balance that does not expire at renewal). New active members on the free tier typically receive a one-time grant of starter anytime credits (commonly marketed as 20 credits); waitlisted signups may differ—see FAQ.

Paid tiers are branded Basic, Pro, and Premium with increasing download and API capabilities. Do not quote prices from this briefing; read live pricing.

Technology and AI

LabSharks is not framed as “one text box → one end-to-end neural audio file.” Typical consumer gen-AI music often optimizes for a single polished stereo bounce from a largely monolithic model stack. Here the aim is closer to composing and producing a real track the way a session does: structure, parts, MIDI, software instruments, multitrack work, mix decisions, then stems and project-friendly material—so you can keep editing in a DAW, not only save one mystery MP3.

The generation stack is proprietary and described by the company as patent-pending. A public-facing label for the orchestration philosophy is broadcast–match–execute–aggregate: many small, purpose-built stages coordinate instead of one model owning the entire song end-to-end. We intentionally do not publish the full technical blueprint on this marketing page.

Large language models appear where interpretation or musical judgment helps, alongside traditional audio and composition tooling—they assist the pipeline; they do not replace a studio-style build-out of the piece.

Studio and API jobs run that in-house pipeline for full songs and phrase loops, then deliver previews, downloads, and assets according to plan and entitlements.

HTTP API

A versioned REST API under /api/v1/ lets eligible accounts create and poll generations, retrieve metadata, and download assets when the server exposes URLs. Clients authenticate with Authorization: Bearer <api_key>. API keys are created and revoked from the signed-in studio: Account → Developer API (browser session).

Authoritative request and response shapes live in the OpenAPI document served as interactive Swagger UI at {API_ORIGIN}/docs (for example https://api.labsharks.com/docs in production). Human-oriented entry: Developers.

Samples and demos

  • Showcase page: /demos.html — curated examples and embedded media where configured.
  • Try the product: /app/ with a free account and starter credits (subject to beta limits).
  • API experiments: use Swagger from /docs on the API host against a key from the studio (Premium tier where required).

Contact

A Contact page exists for future use; it is not active yet. Until it is turned on, use published channels linked from Privacy and FAQ where applicable.

Privacy practices and user rights are described in Privacy. Generated works, licensing, and sharing behavior are summarized in FAQ and checkout-related disclosures where applicable.

Beta status

LabSharks is in public beta: limits, features, and API shapes may change. Integrators should re-check OpenAPI and this page periodically rather than caching assumptions indefinitely.