Formant
Formant is a San Francisco–based robotics and physical-operations cloud platform that lets companies operate fleets of robots and advanced connected devices. The Formant software platform implements workflows for remote monitoring, intervention requests, data management, teleoperation, tech-support investigations, and business analysis, and exposes an extensible cloud infrastructure that can be built upon to create custom robot management experiences. The product surface spans an on-robot Formant Agent (ingesting telemetry from ROS / ROS2 / non-ROS sources via configurable adapters), a REST Admin API at `api.formant.io/v1/admin`, a Python package (`pip install formant`) that bundles both a Cloud SDK (query and ingest data programmatically) and an Agent SDK (post telemetry, handle commands, drive teleoperation from robot-side Python), a Data SDK for JavaScript/TypeScript that powers custom views, modules, and embedded experiences, the `fctl` command-line tool for SSH / SCP / port-forwarding over Formant's peer-to-peer connection, and Formant Metaphysics — an AI-powered incident-management layer that automates alarm triage, predictive maintenance, and SOP-driven investigations across SCADA, Snowflake, Slack, and Teams. The API is organized around devices, fleets, streams, views, commands, events, annotations, intervention requests, files, key-value storage, roles, users, schedules, analytics, and presence/online monitoring. Formant's GitHub organization (FormantIO) publishes the ROS / ROS2 adapter, a Boston Dynamics Spot adapter, an ONVIF camera adapter, a P2P adapter, Cradlepoint adapter, the Toolkit meta-repo for building on Formant APIs, the 3D viewer module, custom module boilerplate, Data SDK examples for Node.js and React Native, a Homebrew tap for `fctl`, and a public JSON-schema repo for module configuration.
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 Formant the way a machine reads it — 92 machine-readable artifacts across 7 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 — Formant scores 53.0/100 (developing), with a separate agent-readiness read of 41/100 (agent aware). 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 Formant
Each block below is one kind of artifact we hold for Formant. 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 7
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.
Formant Admin API
Formant's primary REST API, served from `https://api.formant.io/v1/admin`. Covers devices, fleets, streams, views, teleop views, commands and command templates, schedules, event...
Formant Agent SDK
Python client embedded in the `formant` PyPI package (`pip install formant`, `from formant.sdk.agent.v1 import Client`). Runs on-robot alongside the Formant agent and exposes ty...
Formant Cloud SDK
Python client embedded in the `formant` PyPI package (`from formant.sdk.cloud.v1 import Client`). Wraps the Admin API for programmatic query and ingest of datapoints against you...
Formant Data SDK (JavaScript / TypeScript)
Browser- and Node-side JavaScript / TypeScript SDK for building custom modules, custom views, and embedded experiences against Formant's real-time and historical data planes. Po...
Formant Authentication API
The Authentication API from Formant — 1 operation(s) for authentication.
Formant Commands API
The Commands API from Formant — 2 operation(s) for commands.
Formant Data Access API
The Data Access API from Formant — 1 operation(s) for data access.
Scroll within the panel for all 7 ·
Features 38
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 38 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Formant Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Formant API Rules
SPECTRALFormant API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Formant Command Structure
JSON STRUCTUREFormant Stream Current Value Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Formant Login Example
EXAMPLEFormant Send Command Example
EXAMPLESecurity Posture 2
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.
Integrations 23
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Scroll within the panel for all 23 ·
Solutions 10
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Scroll within the panel for all 10 ·
Resources
Every other property we hold for Formant — 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 5
Portal, sign-up, and the first successful call
Documentation 24
Reference material describing how the API behaves
Scroll within the panel for all 24 ·
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 32
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 32 ·
Access & Security 2
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/formant · machine-readable index on apis.io