Liquid Instruments website screenshot

Liquid Instruments

Liquid Instruments builds Moku, a family of software-defined, FPGA-reconfigurable test-and-measurement hardware platforms (Moku:Go, Moku:Lab, Moku:Pro, Moku:Delta) that replace a bench of traditional instruments — oscilloscope, spectrum analyzer, waveform generator, lock-in amplifier, PID controller, phasemeter, laser lock box, logic analyzer, FIR/digital filter box, frequency response analyzer and more — with one reconfigurable device. Every Moku exposes a RESTful HTTP control API served by the device itself on the local network, wrapped by first-party Python, MATLAB and LabVIEW client libraries plus the MokuCLI command-line utility, and the company runs a hosted OpenID Connect identity service for Moku Cloud Compile and licensed feature access. The company was founded out of gravitational-wave detection research and is headquartered in San Diego, California with offices in Canberra and Melbourne, Australia.

Liquid Instruments publishes 2 APIs on the APIs.io network. Tagged areas include Company, Test and Measurement, Instrumentation, Hardware, and Oscilloscope.

Liquid Instruments’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 26 more developer resources.

32.7/100 thin ▬ flat Agent 14/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
2 APIs
CompanyTest and MeasurementInstrumentationHardwareOscilloscopeSpectrum AnalyzerData AcquisitionFPGAPhotonicsScientific InstrumentsElectronicsLaboratory

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 32.7/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 2.7 / 13
Governance 0.4 / 12
Discoverability 7.6 / 10
Agent readiness — 14/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/liquid-instruments: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

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,...

Liquid Instruments Identity (OAuth 2.0 / OpenID Connect)

The hosted identity service behind mokucli login, Moku Cloud Compile and licensed feature access. It publishes a full OpenID Connect discovery document at https://auth.liquidins...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Liquid Instruments Authentication

apiKey/oauth2/openIdConnect · 3 schemes

SECURITY

Liquid Instruments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Liquid Instruments Scopes

5 scopes · authorizationCode/clientCredentials/deviceCode/implicit/password

5 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 6

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: liquid-instruments
name: Liquid Instruments
description: Liquid Instruments builds Moku, a family of software-defined, FPGA-reconfigurable test-and-measurement hardware
  platforms (Moku:Go, Moku:Lab, Moku:Pro, Moku:Delta) that replace a bench of traditional instruments — oscilloscope, spectrum
  analyzer, waveform generator, lock-in amplifier, PID controller, phasemeter, laser lock box, logic analyzer, FIR/digital
  filter box, frequency response analyzer and more — with one reconfigurable device. Every Moku exposes a RESTful HTTP control
  API served by the device itself on the local network, wrapped by first-party Python, MATLAB and LabVIEW client libraries
  plus the MokuCLI command-line utility, and the company runs a hosted OpenID Connect identity service for Moku Cloud Compile
  and licensed feature access. The company was founded out of gravitational-wave detection research and is headquartered in
  San Diego, California with offices in Canberra and Melbourne, Australia.
image: https://liquidinstruments.com/wp-content/uploads/2022/01/liquid-instruments-logo.svg
url: https://raw.githubusercontent.com/api-evangelist/liquid-instruments/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.20'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Test and Measurement
- Instrumentation
- Hardware
- Oscilloscope
- Spectrum Analyzer
- Data Acquisition
- FPGA
- Photonics
- Scientific Instruments
- Electronics
- Laboratory
apis:
- 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: Code Samples
    url: https://apis.liquidinstruments.com/api/moku-examples/
- name: Liquid Instruments Identity (OAuth 2.0 / OpenID Connect)
  description: The hosted identity service behind mokucli login, Moku Cloud Compile and licensed feature access. It publishes
    a full OpenID Connect discovery document at https://auth.liquidinstruments.com/.well-known/openid-configuration, advertising
    the authorization, token, userinfo, device-authorization, logout and JWKS endpoints, the authorization_code / client_credentials
    / refresh_token / password / implicit / device_code grant types, and the openid, offline_access, email, phone and profile
    scopes. mokucli signs in with the authorization code flow plus PKCE (S256) and then mints a short-lived Security Token
    Service credential that is cached locally.
  humanURL: https://apis.liquidinstruments.com/cli/login.html
  baseURL: https://auth.liquidinstruments.com
  tags:
  - Authentication
  - OpenID Connect
  - OAuth
  properties:
  - type: OpenIDConnect
    url: https://auth.liquidinstruments.com/.well-known/openid-configuration
  - type: Documentation
    url: https://apis.liquidinstruments.com/cli/login.html
  - type: OAuthScopes
    url: scopes/liquid-instruments-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/liquid-instruments-domain-security.yml
- type: Website
  url: https://liquidinstruments.com/
- type: DeveloperPortal
  url: https://apis.liquidinstruments.com/
- type: Documentation
  url: https://apis.liquidinstruments.com/
- type: APIReference
  url: https://apis.liquidinstruments.com/api/reference/
- type: GettingStarted
  url: https://apis.liquidinstruments.com/api/getting-started/
- type: Support
  url: https://liquidinstruments.com/support/contact/
- type: HelpCenter
  url: https://knowledge.liquidinstruments.com/
- type: Community
  url: https://forum.liquidinstruments.com/
- type: Blog
  url: https://liquidinstruments.com/blog/
- type: BlogRSS
  url: https://liquidinstruments.com/feed/
- type: GitHubOrganization
  url: https://github.com/liquidinstruments
- type: SourceCode
  url: https://github.com/liquidinstruments/moku-examples
- type: Code Samples
  url: https://github.com/liquidinstruments/moku-examples
- type: Pricing
  url: https://store.liquidinstruments.com/
- type: SignUp
  url: https://liquidinstruments.com/my-account/
- type: TermsOfService
  url: https://liquidinstruments.com/terms-of-use/
- type: PrivacyPolicy
  url: https://liquidinstruments.com/privacy
- type: AcceptableUsePolicy
  url: https://liquidinstruments.com/terms/acceptable-use-policy
- type: ChangeLog
  url: https://apis.liquidinstruments.com/api/changelog/
- type: ChangeLog
  name: Moku API changelog (captured)
  url: changelog/liquid-instruments-changelog.yml
- type: Packages
  url: packages/liquid-instruments-packages.yml
- type: SDKs
  url: packages/liquid-instruments-packages.yml
- type: CLI
  url: cli/liquid-instruments-cli.yml
- type: Authentication
  url: authentication/liquid-instruments-authentication.yml
- type: OAuthScopes
  url: scopes/liquid-instruments-scopes.yml
- type: WellKnown
  url: well-known/liquid-instruments-well-known.yml
- type: Conformance
  url: conformance/liquid-instruments-conformance.yml
- type: ErrorCatalog
  url: errors/liquid-instruments-error-codes.yml
- type: Lifecycle
  url: lifecycle/liquid-instruments-lifecycle.yml
- type: Conventions
  url: conventions/liquid-instruments-conventions.yml
- type: DataModel
  url: data-model/liquid-instruments-data-model.yml
- type: LLMsTxt
  url: llms/liquid-instruments-llms.txt
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 15
  pass: local-v1