Binarly
Binarly is a firmware and software supply-chain security company whose Binarly Transparency Platform performs binary-native analysis of compiled software, firmware, and container images without requiring source code. It detects known and unknown vulnerabilities, hardcoded secrets, cryptographic materials, malicious code, and missing hardening mitigations across UEFI, bootloaders, Linux packages, and application binaries, then generates SBOM, VEX, CBOM, and PQC-compliance artifacts for supply-chain assurance. The platform exposes a REST API (v4, Keycloak/OIDC-authenticated) so producers can automate firmware scanning inside CI/CD pipelines and enterprise buyers can programmatically assess vendor software. Binarly also maintains open firmware-research tooling such as the FwHunt rule format and fwhunt-scan. The company was surfaced as a portfolio company of Canaan Partners.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Binarly the way a machine reads it — 27 machine-readable artifacts across 20 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Binarly scores 50.0/100 (developing), with a separate agent-readiness read of 46/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Binarly
Each block below is one kind of artifact we hold for Binarly. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 20
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Binarly Assistant API
The Assistant API from Binarly — 5 operation(s) for assistant.
Binarly Chart API
The Chart API from Binarly — 7 operation(s) for chart.
Binarly CustomRules API
The CustomRules API from Binarly — 4 operation(s) for customrules.
Binarly Escalation API
The Escalation API from Binarly — 1 operation(s) for escalation.
Binarly File API
The File API from Binarly — 4 operation(s) for file.
Binarly Finding API
The Finding API from Binarly — 4 operation(s) for finding.
Binarly Grid API
The Grid API from Binarly — 12 operation(s) for grid.
Binarly Group API
The Group API from Binarly — 5 operation(s) for group.
Binarly Image API
The Image API from Binarly — 15 operation(s) for image.
Binarly Integration API
The Integration API from Binarly — 10 operation(s) for integration.
Binarly Notification API
The Notification API from Binarly — 1 operation(s) for notification.
Binarly Product API
The Product API from Binarly — 4 operation(s) for product.
Binarly RoleBinding API
The RoleBinding API from Binarly — 3 operation(s) for rolebinding.
Binarly Scan API
The Scan API from Binarly — 5 operation(s) for scan.
Binarly Search API
The Search API from Binarly — 2 operation(s) for search.
Binarly Subscription API
The Subscription API from Binarly — 2 operation(s) for subscription.
Binarly TempFile API
The TempFile API from Binarly — 1 operation(s) for tempfile.
Binarly User API
The User API from Binarly — 3 operation(s) for user.
Binarly UserStorage API
The UserStorage API from Binarly — 2 operation(s) for userstorage.
Binarly Vulnerability API
The Vulnerability API from Binarly — 2 operation(s) for vulnerability.
Scroll within the panel for all 20 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOGenerate supply-chain compliance artifacts with Binarly
For a scanned image, export the full set of supply-chain assurance artifacts — CycloneDX and SPDX SBOMs, an OpenVEX VEX, a CBOM, and a findings report — for procurement and regu...
ARAZZOScan firmware in CI/CD with Binarly
Create (or reuse) a product, upload a firmware/binary image, run a scan, poll until it completes, then list the findings and pull a PDF report — the core CI/CD gate flow for the...
ARAZZOSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Binarly — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/binarly · machine-readable index on apis.io