What authentication does the Moode Audio API use?

None. The specification declares no authentication scheme and no security requirement on any of its 16 operations, and Moode's own documented curl example passes no credentials. You have no key to obtain and no account to create, because Moode is software running on your own device: access is governed by who can reach the player on your network. Keep the Pi on a trusted network, or put a reverse proxy in front of it if you need authentication.

Can I read the currently playing song with the Moode API?

Yes. Call GET /command/?cmd=get_currentsong to receive the current song's title, artist, album, track number and bitrate. The same response carries a state field, so one call also tells you whether the player is playing, paused or stopped. Moode requires the Metadata file option to be enabled in Audio Config for this command to return data.

What are the rate limits for the Moode Audio API?

Moode publishes none. It is software you run on your own Raspberry Pi, so requests never cross a vendor gateway and no quota is applied to them, and the project's documentation defines no limit. Throughput is bounded by your own hardware and network, so poll at a rate your device is comfortable with.

How do I change the volume through Jentic?

Search Jentic for 'set the Moode volume', load the schema for GET /command/?cmd=set_volume, and execute it with the level argument and your player's local base URL. Jentic returns the volume and mute state Moode reports back.

Does the Moode API work over the internet?

By default no. The player answers on your own network at its local hostname (moode.local) or its IP address, and Moode operates no hosted endpoint you could call from outside. To control Moode remotely, put the Pi behind a reverse proxy that adds TLS and authentication, or use a VPN back to the home network.

Can I limit what my agent is allowed to do with the Moode Audio API?

Yes. Because you run Jentic One yourself, your own rules decide which of Moode's command operations the agent may call. Moode carries the command name in a cmd query parameter rather than in the URL path, so rules bound the agent by operation: you can give it get_currentsong and withhold the commands that change the player. Transport, volume and queue commands are reachable only if you add them to the agent's allowed set.

Is there a Moode Audio MCP server?

You don't need an MCP server to give your agent Moode Audio API. Jentic connects it directly from the API Directory: import Moode Audio API, point it at your player's local base URL, and your agent can read what is playing and control playback, without loading another server's tool definitions into its context. Moode is unauthenticated on your own network, so you have no credential to configure either.