Moode Audio API

Name: Moode Audio API
Brand: Moode Audio API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaAudio Processingnone16 EndpointsREST

For Agents

Control playback, inspect the music library, and read system status of a local Moode Audio Raspberry Pi player through simple HTTP commands.

Install Jentic One Beta

Connect the Moode Audio API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moode Audio API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Moode Audio API.

Read the currently playing song, playback status, and elapsed position from the Pi over HTTP

List and load music library entries via the get_library command

Inspect and modify the current playlist or queue with playback commands

GET STARTED

Start building with Moode Audio API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Moode Audio API, keeping it validated and agent-ready. Moode is an audiophile-quality music player for Raspberry Pi that exposes a simple HTTP command interface for control and inspection. The 16 endpoints are command-style GETs that read the current song, playback status, library, playlist, radio stations, audio output and system information from a local Moode device. The base URL is the device's local hostname (http://moode.local), so the API is intended for use on the same network as the Pi.

Use Cases

Patterns agents use Moode Audio API for, with concrete tasks.

★ Voice or Chat Control of a Local Hi-Fi

An owner adds voice or chat control to their Moode-based hi-fi by exposing the local Moode endpoints behind a simple agent. The agent can read the current song, pause, skip, queue up a playlist, or switch to a radio station, all through plain GET commands against http://moode.local. No cloud account is required because Moode runs entirely on the Pi.

Read the currently playing song from Moode and return artist, album, and elapsed time.

Home Dashboard Now-Playing Card

Home dashboards (Home Assistant, custom panels) poll Moode for now-playing and playback status to show a media card next to other smart-home tiles. Because the Moode endpoints are deterministic GETs with no auth, integration is just an HTTP fetch on a schedule.

Poll Moode every 10 seconds and update a now-playing card with the current song, status, and elapsed time.

Local Library and Radio Browsing

An interactive remote app lists the music library and the configured internet radio stations from Moode, letting the user pick a track or station from a richer UI than Moode's web interface. The library and radio commands return the data the remote app needs without re-implementing Moode's storage layer.

List all radio stations configured on Moode and return their names and stream URLs.

AI Agent Audiophile Assistant

An on-device AI agent uses Jentic to discover Moode's command endpoints, runs them against the local Pi, and answers natural-language questions like 'what's playing' or 'switch to BBC Radio 4' without exposing a cloud service. Because Moode does not publish a public OpenAPI spec, Jentic's spec is the only structured way to drive the device through agent tooling.

Search Jentic for 'control my Moode player', load the schema for the playback-status command, and execute it against http://moode.local.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for moode audio api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/command/?cmd=get_currentsong

Get the currently playing song

GET

/command/?cmd=get_playback_status

Get playback status

GET

/command/?cmd=get_library

Browse the music library

GET

/command/?cmd=get_playlist

Get the current playlist or queue

GET

/command/?cmd=get_radio_stations

List configured radio stations

GET

/command/?cmd=get_audio_info

Get audio output information

GET

/command/?cmd=get_system_info

Get Moode and Pi system information

GET

/command/?cmd=get_currentsong

Get the currently playing song

GET

/command/?cmd=get_playback_status

Get playback status

GET

/command/?cmd=get_library

Browse the music library

GET

/command/?cmd=get_playlist

Get the current playlist or queue

GET

/command/?cmd=get_radio_stations

List configured radio stations

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Moode API does not require credentials, but Jentic still applies environment policy — agents can only call the configured local base URL, preventing accidental calls to look-alike public hosts.

Intent-based discovery

Agents search Jentic by intent (e.g. 'control my Moode player') and receive the matching command endpoint and parameter schema, removing the need to memorise Moode's cmd= query strings.

Time to first call

Direct Moode integration: an hour to read the cmd reference and wire requests. Through Jentic: minutes to search, load, and execute the first command against the local Pi.

FAQs

Specific to using Moode Audio API through Jentic.

Why is there no official OpenAPI spec for Moode Audio API?

Moode Audio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Moode Audio API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Moode Audio API use?

The local Moode HTTP interface does not require authentication; access control is by network reachability since the base URL is http://moode.local on the LAN. Restrict access by keeping the Pi on a trusted network or behind a reverse proxy that adds auth.

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, and elapsed time. Pair it with /command/?cmd=get_playback_status to know whether playback is running, paused, or stopped.

What are the rate limits for the Moode Audio API?

The Pi is the only enforcement point and has no documented rate limit; in practice a Pi 4 handles a few requests per second comfortably. Avoid polling more than once per second to keep CPU usage low on lower-end Pi models.

How do I list radio stations through Jentic?

Search Jentic for 'list Moode radio stations', load the schema for GET /command/?cmd=get_radio_stations, and execute it with the local base URL. Jentic will return the configured stations from the Pi.

Does the Moode API work over the internet?

By default no — the API is reachable at http://moode.local on the local network. To control Moode remotely, expose the Pi behind a reverse proxy that adds TLS and authentication, or use a VPN back to the home network.