# Liquid Instruments

> Liquid Instruments builds Moku — software-defined, FPGA-reconfigurable test-and-measurement
> hardware (Moku:Go, Moku:Lab, Moku:Pro, Moku:Delta) that replaces a bench of traditional
> instruments with one device. Every Moku serves its own RESTful HTTP control API on the local
> network, wrapped by first-party Python, MATLAB and LabVIEW client libraries and the MokuCLI
> command-line utility. A hosted OpenID Connect identity service backs MokuCLI sign-in, Moku
> Cloud Compile and licensed features.

Generated by API Evangelist (https://apievangelist.com) from the public Liquid Instruments
surface on 2026-08-04. Liquid Instruments does not publish an llms.txt of its own — /llms.txt
returned HTTP 404 on apis.liquidinstruments.com, liquidinstruments.com,
knowledge.liquidinstruments.com, forum.liquidinstruments.com and compile.liquidinstruments.com.
This is an independent third-party profile, not a Liquid Instruments document.

## How the API works

- The Moku REST API is **device-local**: there is no vendor-hosted base URL. The published URL
  form is `http://<device-ip>/api/<group>/<action>`.
- **Every action is a POST** of a JSON parameter object (send `{}` when there are no parameters).
  It is action-oriented RPC over HTTP, not resource REST.
- **Authenticate by claiming ownership**: POST `{}` to `/api/moku/claim_ownership`; the response
  carries a `Moku-Client-Key` header that must be sent on every subsequent request. Release with
  `/api/moku/relinquish_ownership`.
- **Responses are always HTTP 200** with an envelope `{success, code, messages, data}`. Failure is
  signalled by `success: false` plus a `code` — not by the HTTP status. Agents must parse the body.
- The Moku is **single-owner**: one session controls a device at a time.
- MokuCLI is **required** for API connections since release 4.0.1, and is how instrument
  bitstreams are downloaded (`mokucli instrument download 4.3.0`).

## APIs

- [Moku REST API](https://apis.liquidinstruments.com/api/): device-local HTTP control API for all
  Moku instruments — oscilloscope, spectrum analyzer, waveform generator, arbitrary waveform
  generator, lock-in amplifier, PID controller, phasemeter, laser lock box, logic analyzer,
  FIR filter box, digital filter box, frequency response analyzer, datalogger, time & frequency
  analyzer, gigabit streamer, neural network and custom instruments.
- [Liquid Instruments Identity (OAuth 2.0 / OIDC)](https://auth.liquidinstruments.com/.well-known/openid-configuration):
  hosted identity for MokuCLI sign-in, Moku Cloud Compile and licensing.

## Docs

- [Moku documentation home](https://apis.liquidinstruments.com/)
- [REST API home](https://apis.liquidinstruments.com/api/)
- [API reference (all instruments)](https://apis.liquidinstruments.com/api/reference/)
- [Getting started with cURL / REST](https://apis.liquidinstruments.com/api/getting-started/starting-curl.html)
- [Getting started with Python](https://apis.liquidinstruments.com/api/getting-started/starting-python.html)
- [Getting started with MATLAB](https://apis.liquidinstruments.com/api/getting-started/starting-matlab.html)
- [MokuCLI](https://apis.liquidinstruments.com/cli/)
- [Moku Compile (FPGA in the browser)](https://apis.liquidinstruments.com/mc/)
- [Moku Neural Network](https://apis.liquidinstruments.com/mnn/)
- [API changelog](https://apis.liquidinstruments.com/api/changelog/)
- [Knowledge base](https://knowledge.liquidinstruments.com/)
- [Community forum](https://forum.liquidinstruments.com/)

## Packages

- [moku (PyPI)](https://pypi.org/project/moku/) — `pip install moku`, MIT, Python >= 3.8
- [moku-MATLAB (MATLAB File Exchange)](https://www.mathworks.com/matlabcentral/fileexchange/94160-moku-matlab)
- [LabVIEW API](https://liquidinstruments.com/products/apis/labview-api/)
- [MokuCLI](https://liquidinstruments.com/software/utilities/)
- [moku-examples (GitHub, MIT)](https://github.com/liquidinstruments/moku-examples) — Python,
  MATLAB, VHDL, and raw-REST demos in C++, C#, Java, Go, Rust, Node.js and Perl.

## API Evangelist artifacts for this provider

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/liquid-instruments/refs/heads/main/apis.yml)
- authentication/liquid-instruments-authentication.yml — the two auth surfaces
- scopes/liquid-instruments-scopes.yml — OIDC scopes read from live discovery
- conventions/liquid-instruments-conventions.yml — transport, envelope, versioning, timeouts
- errors/liquid-instruments-error-codes.yml — the error-code registry
- data-model/liquid-instruments-data-model.yml — 22 operation groups, 522 operations
- lifecycle/liquid-instruments-lifecycle.yml — versioning, deprecations, support
- changelog/liquid-instruments-changelog.yml — recent releases
- cli/liquid-instruments-cli.yml — the MokuCLI command surface
- conformance/liquid-instruments-conformance.yml — standards conformance
- well-known/liquid-instruments-well-known.yml — /.well-known probe results
- security/liquid-instruments-domain-security.yml — TLS/DNS posture

## What Liquid Instruments does NOT publish

Recorded so an agent does not go looking:

- No OpenAPI, Swagger, GraphQL SDL or AsyncAPI document (404 on every host probed).
- No MCP server and no A2A agent card (`/.well-known/agent-card.json` and
  `/.well-known/agent.json` return 404 everywhere).
- No webhooks or event callbacks of any kind.
- No `security.txt`, no vulnerability-disclosure page, no bug-bounty program, no trust centre.
- No `/.well-known/api-catalog`, no `ai-plugin.json`, no Postman collection.
- No deprecation policy, no Sunset/Deprecation headers, no SLA.
- `status.liquidinstruments.com` exists in DNS but fails the TLS handshake, so there is no
  usable status page.

## Company

- [Website](https://liquidinstruments.com/)
- [About](https://liquidinstruments.com/company/about/) — San Diego, CA; Canberra and Melbourne, Australia
- [Blog](https://liquidinstruments.com/blog/) ([RSS](https://liquidinstruments.com/feed/))
- [Store / pricing](https://store.liquidinstruments.com/)
- [Support](https://liquidinstruments.com/support/contact/)
- [Terms of use](https://liquidinstruments.com/terms-of-use/) · [Privacy](https://liquidinstruments.com/privacy)
- [GitHub](https://github.com/liquidinstruments)