> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundpiece.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with AI

> Give your coding assistant what it needs to write a correct Soundpiece integration

AI coding assistants write better integrations when they can read these docs instead of guessing. There are four ways to give them access, from most to least capable. Whichever you use, start your assistant off with the [starter prompt](#starter-prompt) below.

## Install the Soundpiece skill

A skill is a set of instructions an agent loads when a task needs it. The Soundpiece skill tells it how the API works, which endpoint does what and what it costs, how to use the [reference client](/client), and what the [production checklist](/best-practices) asks for. Install it with:

```bash theme={null}
npx skills add https://docs.soundpiece.co
```

You can also read it directly at [docs.soundpiece.co/skill.md](https://docs.soundpiece.co/skill.md).

## Connect the docs MCP server

These docs run an [MCP](https://modelcontextprotocol.io) server, so an assistant can search them and read any page while it works. Its URL is:

```text theme={null}
https://docs.soundpiece.co/mcp
```

* **Claude:** in **Settings → Connectors**, choose **Add custom connector** and paste the URL.
* **Claude Code:** run `claude mcp add --transport http soundpiece-docs https://docs.soundpiece.co/mcp`.
* **Cursor** and **VS Code:** use **Connect to Cursor** or **Connect to VS Code** in the menu at the top of any page.
* **Anything else:** add the URL as a remote (HTTP) MCP server in its settings.

Agents connected this way can also find the Soundpiece skill through the server.

## Point it at llms.txt

Two plain-text files describe the whole site for language models:

* [`llms.txt`](https://docs.soundpiece.co/llms.txt) lists every page, with a one-line summary and a link to it.
* [`llms-full.txt`](https://docs.soundpiece.co/llms-full.txt) is the full text of every page in one file, to paste in or attach.

Every page is also available as Markdown: add `.md` to its URL, for example [docs.soundpiece.co/client.md](https://docs.soundpiece.co/client.md).

## Use the page menu

The menu at the top of every page can:

* **Copy page** as Markdown, to paste into a chat;
* **View as Markdown**;
* **Open in ChatGPT**, **Open in Claude** or **Open in Perplexity**, with the page already in the conversation;
* **Copy MCP server URL**, or **Connect to Cursor** and **Connect to VS Code**.

## Starter prompt

Paste this at the start of a session, then describe what you want to build.

```text theme={null}
I'm integrating the Soundpiece audio API. Before writing any code:

1. Read the Soundpiece docs: use the Soundpiece skill or docs MCP server if you have
   them, otherwise fetch https://docs.soundpiece.co/llms.txt and the pages it links to.
2. Use the reference client from https://docs.soundpiece.co/client.md. Copy the file
   for my language (soundpiece.py or soundpiece.mjs) into the project unchanged, and
   call run() and download() rather than writing your own HTTP calls.
3. Follow the production checklist at https://docs.soundpiece.co/best-practices.md.
   In particular: read the API key from the SOUNDPIECE_API_KEY environment variable;
   create one idempotency key per job, store it before the first request, and pass it
   to run() on every attempt; branch on error.code, never error.message; download
   results promptly instead of storing their URLs.
4. Take request fields, limits and credit costs from the API Reference, not from memory.

What I want to build:
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.