beats-btw

endpoint

https://beats.bitwrap.io/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is beats-btw live?

Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.

Is beats-btw free to use?

Not measured yet.

What tools does beats-btw have?

4 tools: get_render_status, get_song, list_genres, generate_share.

Is beats-btw safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_render_status reads unknown never probed

  Report bake state for a CID on the publish host: "ready" (the .webm is served), "queued" (in the render-farm queue), "missing" (envelope not yet mirrored), or "unmarked" (envelope present but never queued, or render farm cleared it without uploading). Pure function of the CID + publish host state — no rendering side effects. Useful for polling after generate_share(render=true) without wait=true, or for verifying earlier work.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "cid"
    ],
    "properties": {
      "cid": {
        "type": "string",
        "description": "Content-address from a beats share URL."
      }
    }
  }

  arguments 12 lines copy
• get_song reads unknown never probed

  Fetch the sealed share-v1 envelope for a CID (the deterministic recipe behind a ?cid= link).

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "cid"
    ],
    "properties": {
      "cid": {
        "type": "string",
        "description": "Content-address from a beats share URL (the z… string after ?cid=)."
      }
    }
  }

  arguments 12 lines copy
• list_genres reads unknown never probed

  List available genre presets for generation

  mcp-tool

  12345

  {
    "type": "object",
    "required": [],
    "properties": {}
  }

  arguments 5 lines copy
• generate_share changes data unknown never probed

  Create a shareable, deterministic beat from a genre + seed and return a playable URL. Builds a share-v1 envelope, computes its content-address (CID), and seals it to the store. Opening the URL regenerates byte-identical playback in the browser — no server, no AI at play time.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344

  {
    "type": "object",
    "required": [
      "genre"
    ],
    "properties": {
      "seed": {
        "type": "number",
        "description": "Integer seed for reproducible generation (default 0). Same genre+seed always yields the same track."
      },
      "wait": {
        "type": "boolean",
        "description": "With render=true, block up to ~50s waiting for the farm to publish the .webm. Capped well under typical MCP client timeouts so the call resolves cleanly: if the render finishes in time you get the audio URL inline, otherwise you get the CID + a polling hint and the render keeps going (poll get_render_status). Ignored when render=false or when the sync render+mirror path is in use. Default false."
      },
      "genre": {
        "type": "string",
        "description": "Genre preset, e.g. techno, house, ambient, dnb, dubstep, edm, synthwave, trance, trap, lofi. Use list_genres for the full set."
      },
      "swing": {
        "type": "number",
        "description": "Swing percentage 0-100 (default: genre-specific)."
      },
      "tempo": {
        "type": "number",
        "description": "Override tempo in BPM (default: genre-specific)."
      },
      "render": {
        "type": "boolean",
        "description": "Produce the downloadable .webm. With BEATS_REBUILD_SECRET set (authoring backend): mirrors the envelope to the publish host, synchronously renders on the local authoring server, then PUTs the .webm to the publish host with X-Rebuild-Secret. Without the secret (public MCP, anonymous user): queues the CID on the publish host's render farm via POST /api/rebuild-mark — the worker bakes it asynchronously. Either way the link plays in-browser via Tone.js regeneration without the .webm. Default false (envelope-only, no farm load)."
      },
      "humanize": {
        "type": "number",
        "description": "Humanize amount 0-100 (default: genre-specific)."
      },
      "structure": {
        "type": "string",
        "description": "Arrangement: loop, ab, drop, build, jam, minimal, standard, extended. Omit for infinite loop."
      },
      "arrangeSeed": {
        "type": "number",
        "description": "Seed for the arrangement (blueprint pick, humanization). Only meaningful with a non-loop structure."
      }
    }
  }

  arguments 44 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.