Liquid Instruments

Moku REST API

The Moku Scripting API is a RESTful HTTP interface served by the Moku device itself. A client first POSTs an empty JSON object to moku/claim_ownership to mint a Moku-Client-Key, then POSTs JSON parameter objects to /api// for every subsequent operation. Responses are a uniform envelope of success, code, messages and data. Because the API server runs on the customer's own hardware, there is no vendor-hosted base URL — the base URL is the device's IP address on the local network (IPv4, or a bracketed IPv6 link-local address over USB).

Documentation GitHub

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/moku-rest-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

name: Moku REST API
description: The Moku Scripting API is a RESTful HTTP interface served by the Moku device itself. A client
  first POSTs an empty JSON object to moku/claim_ownership to mint a Moku-Client-Key, then POSTs JSON
  parameter objects to /api/<instrument-or-group>/<action> for every subsequent operation. Responses are
  a uniform envelope of success, code, messages and data. Because the API server runs on the customer's
  own hardware, there is no vendor-hosted base URL — the base URL is the device's IP address on the local
  network (IPv4, or a bracketed IPv6 link-local address over USB).
humanURL: https://apis.liquidinstruments.com/api/
baseURL: http://{device_ip}/api
x-base-url-note: 'Device-local API. The published URL form is http://<ip>/api/<instrument>/<action> (source:
  https://apis.liquidinstruments.com/api/getting-started/starting-curl.html). There is no vendor-hosted
  production host for this API; each Moku serves its own.'
tags:
- Test and Measurement
- Instrumentation
- Device Control
properties:
- type: Documentation
  url: https://apis.liquidinstruments.com/api/
- type: APIReference
  url: https://apis.liquidinstruments.com/api/reference/
- type: GettingStarted
  url: https://apis.liquidinstruments.com/api/getting-started/starting-curl.html
- type: Authentication
  url: authentication/liquid-instruments-authentication.yml
- type: ErrorCatalog
  url: errors/liquid-instruments-error-codes.yml
- type: Conventions
  url: conventions/liquid-instruments-conventions.yml
- type: DataModel
  url: data-model/liquid-instruments-data-model.yml
- type: CodeExamples
  url: https://apis.liquidinstruments.com/api/moku-examples/