HYPERLABS website screenshot

HYPERLABS

HYPERLABS, Inc. designs and manufactures signal-integrity products for high-speed digital and datacom test in the United States. Two product classes: ultra-broadband Components (amplifiers, baluns, DC blocks, bias tees, pick-off tees, power dividers, attenuators, terminations, inverters) built for 112 and 224 Gbps PAM-4 applications, and Instruments — USB-powered and USB-controlled TDRs, Signal Path Analyzers, controlled-impedance analyzers and impulse generators with 1-20 channels and rise times as fast as 35 ps. Founded in 1992, with engineering and manufacturing in Louisville, Colorado and Beaverton, Oregon. HYPERLABS publishes two machine-readable contracts: an OpenAPI 3.0.1 definition (175 operations, served with Swagger UI) for the hyperlabs.com product-catalog and customer web backend, and an MIT-licensed proto3 gRPC service definition, radium.v1.Radium, for programmatic control and waveform streaming from the TDR11100 Time Domain Reflectometer. Instrument automation is also offered as first-party Windows DLL packages (ZTDR and XTDR) with C++ sample source and manuals.

HYPERLABS publishes 2 APIs on the APIs.io network: Web API and Radium gRPC API (TDR11100). Tagged areas include signal-integrity, Test and Measurement, Electronic Components, Instrumentation, and time-domain-reflectometry.

The HYPERLABS catalog on APIs.io includes 1 event-driven AsyncAPI specification.

HYPERLABS’s developer surface includes documentation, API reference, getting-started guide, support, changelog, authentication, code examples, and 26 more developer resources.

30.8/100 thin ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
2 APIs 1 MCP Servers
signal-integrityTest and MeasurementElectronic ComponentsInstrumentationtime-domain-reflectometryhigh-speed-digitalDatacomHardwaregRPCManufacturing

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 30.8/100 · thin
Contract Quality 13.6 / 25
Developer Ergonomics 5.6 / 20
Access Clarity 1.3 / 20
Operational Transparency 2.4 / 13
Contract Governance 2.0 / 12
Discoverability 5.9 / 10
Agent readiness — 25/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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/hyperlabs: 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.

HYPERLABS Web API

The ASP.NET Core backend that powers www.hyperlabs.com — product catalog, product classes, categories, tags and filtering, application notes, datasheets, software/DLL downloads,...

HYPERLABS Radium gRPC API (TDR11100)

Public gRPC control and acquisition interface for the HYPERLABS TDR11100 Time Domain Reflectometer. The proto3 service radium.v1.Radium exposes 22 unary RPCs covering readiness ...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Hyperlabs.Web

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

HYPERLABS Radium instrument event streams (TDR11100)

Server-streaming surface of the radium.v1.Radium gRPC service running on a HYPERLABS TDR11100 Time Domain Reflectometer. A client opens a gRPC channel to the instrument on TCP 5...

ASYNCAPI

Security Posture 2

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

Hyperlabs Authentication

apiKey · 1 scheme

SECURITY

Hyperlabs Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 4

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hyperlabs
name: HYPERLABS
description: 'HYPERLABS, Inc. designs and manufactures signal-integrity products for high-speed digital and datacom test in
  the United States. Two product classes: ultra-broadband Components (amplifiers, baluns, DC blocks, bias tees, pick-off tees,
  power dividers, attenuators, terminations, inverters) built for 112 and 224 Gbps PAM-4 applications, and Instruments — USB-powered
  and USB-controlled TDRs, Signal Path Analyzers, controlled-impedance analyzers and impulse generators with 1-20 channels
  and rise times as fast as 35 ps. Founded in 1992, with engineering and manufacturing in Louisville, Colorado and Beaverton,
  Oregon. HYPERLABS publishes two machine-readable contracts: an OpenAPI 3.0.1 definition (175 operations, served with Swagger
  UI) for the hyperlabs.com product-catalog and customer web backend, and an MIT-licensed proto3 gRPC service definition,
  radium.v1.Radium, for programmatic control and waveform streaming from the TDR11100 Time Domain Reflectometer. Instrument
  automation is also offered as first-party Windows DLL packages (ZTDR and XTDR) with C++ sample source and manuals.'
image: https://www.hyperlabs.com/assets/logoFull.svg
url: https://raw.githubusercontent.com/api-evangelist/hyperlabs/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- signal-integrity
- Test and Measurement
- Electronic Components
- Instrumentation
- time-domain-reflectometry
- high-speed-digital
- Datacom
- Hardware
- gRPC
- Manufacturing
tags_raw:
- signal-integrity
- test-and-measurement
- electronic-components
- instrumentation
- time-domain-reflectometry
- high-speed-digital
- datacom
- hardware
- grpc
- manufacturing
apis:
- name: HYPERLABS Web API
  description: The ASP.NET Core backend that powers www.hyperlabs.com — product catalog, product classes, categories, tags
    and filtering, application notes, datasheets, software/DLL downloads, website content (banner, events, FAQs, team, timeline,
    sales representatives, sales-and-warranty terms), customer accounts with Google and Microsoft sign-in, customer wishlists,
    quote requests and contact messages, plus an authenticated admin surface. The OpenAPI 3.0.1 definition and a Swagger UI
    are served publicly from the API host. It is not marketed as a developer product and carries no published terms of use
    for third-party consumption.
  humanURL: https://www.hyperlabs.com/api/swagger/index.html
  baseURL: https://www.hyperlabs.com/api
  tags:
  - Product Catalog
  - E-Commerce
  - Content
  - Account
  - Test and Measurement
  tags_raw:
  - product-catalog
  - e-commerce
  - content
  - accounts
  - test-and-measurement
  properties:
  - type: OpenAPI
    url: openapi/hyperlabs-web-openapi-original.json
  - type: APIReference
    url: https://www.hyperlabs.com/api/swagger/index.html
  - type: Authentication
    url: authentication/hyperlabs-authentication.yml
  - type: Conventions
    url: conventions/hyperlabs-conventions.yml
  - type: ErrorCatalog
    url: errors/hyperlabs-problem-types.yml
  - type: DataModel
    url: data-model/hyperlabs-data-model.yml
  - type: Overlay
    url: overlays/hyperlabs-web-overlay.yaml
- name: HYPERLABS Radium gRPC API (TDR11100)
  description: Public gRPC control and acquisition interface for the HYPERLABS TDR11100 Time Domain Reflectometer. The proto3
    service radium.v1.Radium exposes 22 unary RPCs covering readiness and board state, reset, LED control, board temperature,
    TDR enable/preset configuration, acquisition-filter configuration, license management, and T0 / calibration-region offsets,
    plus 3 server-streaming RPCs that emit an open-ended stream of state events, LED state and waveform sample packets. The
    service listens on TCP port 50052 on the instrument itself over an insecure (plaintext, unauthenticated) channel, so the
    contract is device-local rather than internet-facing. HYPERLABS publishes the .proto, the generated Python bindings and
    a worked Python capture example under an MIT license on its GitHub organization.
  humanURL: https://github.com/HYPERLABS/TDR11100
  x-transport: grpc
  x-endpoint: '{instrument-ip}:50052'
  x-note: No public baseURL — the Radium service runs on the customer's own TDR11100 hardware and is reached at the instrument's
    IP address on TCP 50052. Recorded honestly rather than substituted with a placeholder host.
  tags:
  - gRPC
  - Instrumentation
  - time-domain-reflectometry
  - Streaming
  - Test and Measurement
  tags_raw:
  - grpc
  - instrumentation
  - time-domain-reflectometry
  - streaming
  - test-and-measurement
  properties:
  - type: Protobuf
    url: grpc/hyperlabs-radium.proto
  - type: SourceCode
    url: https://github.com/HYPERLABS/TDR11100
  - type: AsyncAPI
    url: asyncapi/hyperlabs-radium-asyncapi.yml
  - type: Examples
    url: https://github.com/HYPERLABS/TDR11100/raw/main/gRPC_Sample_Script.zip
common:
- type: MCPServer
  url: mcp/hyperlabs-mcp.yml
- type: IssueTracker
  url: https://github.com/HYPERLABS/TDR11100/issues
- type: License
  name: MIT
  url: https://github.com/HYPERLABS/TDR11100/blob/main/LICENSE
- type: DomainSecurity
  url: security/hyperlabs-domain-security.yml
- type: Website
  url: https://www.hyperlabs.com/
- type: Documentation
  url: https://www.hyperlabs.com/support/
- type: APIReference
  url: https://www.hyperlabs.com/api/swagger/index.html
- type: GettingStarted
  url: https://www.hyperlabs.com/applications/
- type: About
  url: https://www.hyperlabs.com/about-us/
- type: Support
  url: https://www.hyperlabs.com/support/
- type: HelpCenter
  url: https://www.hyperlabs.com/support/faq/
- type: GitHubOrganization
  url: https://github.com/HYPERLABS
- type: Login
  url: https://www.hyperlabs.com/login
- type: TermsOfService
  url: https://www.hyperlabs.com/support/sales-and-warranty-terms/
- type: PrivacyPolicy
  url: https://www.hyperlabs.com/support/privacy-policy/
- type: Contact
  url: https://www.hyperlabs.com/contact/
- type: Deprecation
  url: https://www.hyperlabs.com/support/discontinued-products/
- type: SDKs
  url: packages/hyperlabs-packages.yml
- type: Packages
  url: packages/hyperlabs-packages.yml
- type: ChangeLog
  url: changelog/hyperlabs-changelog.yml
- type: Lifecycle
  url: lifecycle/hyperlabs-lifecycle.yml
- type: Conformance
  url: conformance/hyperlabs-conformance.yml
- type: Conventions
  url: conventions/hyperlabs-conventions.yml
- type: Authentication
  url: authentication/hyperlabs-authentication.yml
- type: ErrorCatalog
  url: errors/hyperlabs-problem-types.yml
- type: DataModel
  url: data-model/hyperlabs-data-model.yml
- type: Protobuf
  url: grpc/hyperlabs-radium.proto
- type: OpenAPI
  url: openapi/hyperlabs-web-openapi-original.json
- type: Overlay
  url: overlays/hyperlabs-web-overlay.yaml
- type: AsyncAPI
  url: asyncapi/hyperlabs-radium-asyncapi.yml
- type: Examples
  url: https://github.com/HYPERLABS/TDR11100/raw/main/gRPC_Sample_Script.zip
- type: LLMsTxt
  url: llms/hyperlabs-llms.txt
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/hyperlabs"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hyperlabs/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hyperlabs/evidence"

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

Get an API key

Free tier, no email required.

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