Per Vices

Per Vices Corporation is a Toronto-based company that designs and manufactures high-performance software defined radio (SDR) platforms, where signal tuning is handled in hardware while the remaining radio functionality runs in software so a single application-agnostic platform can serve many markets. Its product line includes Cyan (up to 16 independent radio chains, near-DC to 18 GHz), Crimson TNG (4 Rx / 4 Tx, near-DC to 6 GHz), Chestnut (near-DC to 9 GHz on an Intel Stratix 10 FPGA), and Calamine (receive-only, near-DC to 40 GHz). Per Vices ships open-source host software and firmware built on the UHD (USRP Hardware Driver) framework rather than a public web API; developers program the radios through the UHD C++ driver, GNU Radio integration, and example applications published on its GitHub org, with full integration support provided directly to customers. Control of the radio is device-local rather than internet-facing: an on-device web UI and socket.io channel on the SDR management port, plus the UHD state tree read and written with the uhd_manual_get / uhd_manual_set utilities. Unusually for its market, Per Vices publishes list prices for every platform configuration on a public pricing page. It publishes no public REST/OpenAPI web API surface, no MCP server and no A2A agent card; every /.well-known/ path returned 404 on both hosts on 2026-08-14.

Per Vices is profiled on the APIs.io network. Tagged areas include Company, Software Defined Radio, SDR, Radio Frequency, and Wireless.

Per Vices’ developer surface includes engineering blog, support, documentation, getting-started guide, pricing, changelog, CLI, and 13 more developer resources.

24.9/100 emerging ▲ 16.0 Agent 3/100 human only Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
0 APIs
CompanySoftware Defined RadioSDRRadio FrequencyWirelessHardwareFPGATelecommunicationsEmbedded Systems

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 24.9/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 6.6 / 17
Commercial Clarity 8.9 / 17
Operational Transparency 2.3 / 11
Governance 0.0 / 10
Discoverability 4.9 / 9
Regulatory Posture 2.1 / 15
Agent readiness — 3/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 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
Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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/per-vices: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Per Vices Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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

Per Vices Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 5

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 3

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

Source (apis.yml)

apis.yml Raw ↑
aid: per-vices
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/per-vices.png
name: Per Vices
description: 'Per Vices Corporation is a Toronto-based company that designs and manufactures high-performance software defined
  radio (SDR) platforms, where signal tuning is handled in hardware while the remaining radio functionality runs in software
  so a single application-agnostic platform can serve many markets. Its product line includes Cyan (up to 16 independent radio
  chains, near-DC to 18 GHz), Crimson TNG (4 Rx / 4 Tx, near-DC to 6 GHz), Chestnut (near-DC to 9 GHz on an Intel Stratix
  10 FPGA), and Calamine (receive-only, near-DC to 40 GHz). Per Vices ships open-source host software and firmware built on
  the UHD (USRP Hardware Driver) framework rather than a public web API; developers program the radios through the UHD C++
  driver, GNU Radio integration, and example applications published on its GitHub org, with full integration support provided
  directly to customers. Control of the radio is device-local rather than internet-facing: an on-device web UI and socket.io
  channel on the SDR management port, plus the UHD state tree read and written with the uhd_manual_get / uhd_manual_set utilities.
  Unusually for its market, Per Vices publishes list prices for every platform configuration on a public pricing page. It
  publishes no public REST/OpenAPI web API surface, no MCP server and no A2A agent card; every /.well-known/ path returned
  404 on both hosts on 2026-08-14.'
url: https://raw.githubusercontent.com/api-evangelist/per-vices/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- a16z
- y-combinator
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-08-14'
tags:
- Company
- Software Defined Radio
- SDR
- Radio Frequency
- Wireless
- Hardware
- FPGA
- Telecommunications
- Embedded Systems
apis: []
common:
- type: DomainSecurity
  url: security/per-vices-domain-security.yml
- type: Packages
  url: packages/per-vices-packages.yml
  name: Per Vices Developer Packages
- type: SDKs
  url: packages/per-vices-packages.yml
  name: Per Vices UHD / GNU Radio Developer Libraries
- type: LLMsTxt
  url: llms/per-vices-llms.txt
  name: Per Vices llms.txt
- type: Website
  url: https://www.pervices.com
  name: Per Vices Website
- type: Blog
  url: https://www.pervices.com/blog
  name: Per Vices Blog
- type: Support
  url: https://support.pervices.com
  name: Per Vices Support Portal
- type: GitHubOrganization
  url: https://github.com/pervices
  name: Per Vices on GitHub
- type: SourceCode
  url: https://github.com/pervices/examples
  name: Per Vices Example Programs and Applications
- type: Documentation
  url: https://support.pervices.com/
  name: Per Vices Support and Documentation Site
- type: GettingStarted
  url: https://support.pervices.com/how-to/pvht-1-physicalsetup/
  name: 'PVHT-1: How to Physically Set Up a Per Vices SDR'
- type: BlogRSS
  url: https://www.pervices.com/feed/
  name: Per Vices Blog RSS Feed
- type: Pricing
  url: https://www.pervices.com/pricing/
  name: Per Vices Pricing
- type: TermsOfService
  url: https://www.pervices.com/terms-conditions/
  name: Per Vices Terms and Conditions
- type: Plans
  url: plans/per-vices-plans-pricing.yml
  name: Per Vices Published Hardware Pricing
- type: RateLimits
  url: rate-limits/per-vices-rate-limits.yml
  name: Per Vices Rate Limits (none published)
- type: ChangeLog
  url: changelog/per-vices-changelog.yml
  name: Per Vices Firmware and Host Driver Releases
- type: CLI
  url: cli/per-vices-cli.yml
  name: Per Vices UHD Command-Line Utilities
- type: Conventions
  url: conventions/per-vices-conventions.yml
  name: Per Vices Device Control Interface Conventions
- type: Lifecycle
  url: lifecycle/per-vices-lifecycle.yml
  name: Per Vices Release and Support Lifecycle
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 7
  pass: local-v1
x-coverage:
  state: none
  reason: not-a-software-company
  detail: Per Vices manufactures software defined radio hardware — the product is a radio, and its control plane is device-local
    (an on-device web UI and socket.io channel on the SDR management port, default 192.168.10.2, plus the UHD state tree),
    so there is no internet-facing API to publish; every /.well-known/, /openapi.json, /swagger.json and /llms.txt path returned
    a genuine 404 on both www.pervices.com and support.pervices.com.
  evidence:
  - url: https://www.pervices.com/openapi.json
    status: 404
  - url: https://www.pervices.com/.well-known/agent-card.json
    status: 404
  - url: https://support.pervices.com/openapi.json
    status: 404
  - url: https://support.pervices.com/how-to/pvht-15-get-set-paths-uhd/
    status: 200
  checked: '2026-08-14'