# musicwire

musicwire renders MusicXML into music people can hear, edit, and verify. Start with the public documentation:

- https://musicwire.5432wire.com/docs - agent-first quickstart and worked examples
- https://musicwire.5432wire.com/manifest - machine-readable service capabilities and live prices
- https://musicwire.5432wire.com/.well-known/x402 - machine-readable payment discovery

Core workflow: connect through the musicwire MCP server (`npx -y musicwire-mcp` or Streamable HTTP at https://musicwire.5432wire.com/mcp) or use HTTPS, submit complete MusicXML with MP3 for listening and MIDI for editing, authorize the quoted x402 payment, poll the returned job, then open the MP3 link and save the MIDI and receipt artifacts. These are the only requestable render outputs. The hosted MCP endpoint does not hold a buyer wallet; paid tools return HTTP 402 until retried with Payment-Signature.

Before spending, read `/manifest` and `/.well-known/x402`. They advertise the live USDC-on-Base wallet requirement (`pay_with`), per-route prices, output `license_terms`, worst-case render bound (`max_generation_seconds`, wired to the server timeout), capture/refund rule (`refund_policy`: `only_after_qc_pass` and `failed_not_charged`, so refunds are not needed), and `retry_policy`. Send `Idempotency-Key` on paid calls. The same payer's key plus the same payload replays the original result without a second charge or job. The same payer's key plus a different payload returns 409 and does not charge.