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.
Kin Score
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Per Vices Rate Limits
RATE LIMITSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
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