Standard Bots website screenshot

Standard Bots

Standard Bots designs and builds AI-native industrial robotic arms — the RO1 family (Spark, Core/RO1, Thor, and the Bolt beta) — designed and assembled in the USA for machine tending, welding, palletizing, pick & place, and inspection. The robots ship with a developer platform, "StandardOS", that exposes a Bearer-token REST API served on the robot control box (/api/v1) for controlling arm motion, the gripper/end-effector, cameras, routines, teleoperation, recording, I/O and fault recovery. Alongside the REST API, Standard Bots publishes an official Python SDK (PyPI: standardbots), a realtime protobuf external-control streaming channel, and a ROS2 bridge (Cyclone DDS) with MoveIt and Modbus tooling — making the RO1 programmable both for high-level orchestration and low-latency realtime control.

Standard Bots publishes 1 API on the APIs.io network. Tagged areas include Company, Robotics, Industrial Automation, Robotic Arm, and Manufacturing.

Standard Bots’ developer surface includes documentation, API reference, support, engineering blog, authentication, sandbox, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub
29.6/100 thin ▬ flat Agent 19/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyRoboticsIndustrial AutomationRobotic ArmManufacturingArtificial IntelligenceMachine TendingDeveloper APIROS 2Physical AI

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 29.6/100 · thin
Contract Quality 6.7 / 25
Developer Ergonomics 8.9 / 20
Access Clarity 5.5 / 20
Operational Transparency 0.3 / 13
Contract Governance 0.5 / 12
Discoverability 7.6 / 10
Agent readiness — 19/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 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 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 Well-Known Document 0 / 5
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/standard-bots: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

RO1 Robotics REST API

On-robot REST API (served by the RO1 control box on /api/v1, Bearer-token auth) for controlling arm position and motion, the gripper/end-effector, cameras, routines, teleoperati...

Security Posture 2

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

Standard Bots Authentication

http · 1 scheme

SECURITY

Standard Bots Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Login
Login
 Sandbox
Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate
X-MCPServerCandidate
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Lifecycle
Lifecycle
 Conformance
Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication

Operate 1

Status, limits, changes, and where to get help

Support
Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

Protobuf
Protobuf

Source (apis.yml)

apis.yml Raw ↑ 
aid: standard-bots
name: Standard Bots
description: 'Standard Bots designs and builds AI-native industrial robotic arms — the RO1 family (Spark, Core/RO1, Thor,
  and the Bolt beta) — designed and assembled in the USA for machine tending, welding, palletizing, pick & place, and inspection.
  The robots ship with a developer platform, "StandardOS", that exposes a Bearer-token REST API served on the robot control
  box (/api/v1) for controlling arm motion, the gripper/end-effector, cameras, routines, teleoperation, recording, I/O and
  fault recovery. Alongside the REST API, Standard Bots publishes an official Python SDK (PyPI: standardbots), a realtime
  protobuf external-control streaming channel, and a ROS2 bridge (Cyclone DDS) with MoveIt and Modbus tooling — making the
  RO1 programmable both for high-level orchestration and low-latency realtime control.'
url: https://raw.githubusercontent.com/api-evangelist/standard-bots/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://assets-global.website-files.com/63d925b46a84dec214bc0bbd/6408ee2c083a0474a480124a_OG%20Image-Home.jpg
x-type: company
x-source: vc-portfolio
x-backed-by:
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Robotics
- Industrial Automation
- Robotic Arm
- Manufacturing
- Artificial Intelligence
- Machine Tending
- Developer API
- ROS 2
- Physical AI
tags_raw:
- Company
- Robotics
- Industrial Automation
- Robotic Arm
- Manufacturing
- Artificial Intelligence
- Machine Tending
- Developer API
- ROS2
- Physical AI
apis:
- name: RO1 Robotics REST API
  description: On-robot REST API (served by the RO1 control box on /api/v1, Bearer-token auth) for controlling arm position
    and motion, the gripper/end-effector, cameras, routines, teleoperation, the recorder, I/O, calibration and fault recovery.
    A companion realtime protobuf stream and ROS2 bridge cover low-latency control.
  humanURL: https://docs.standardbots.com/docs/rest-api/
  baseURL: http://robot-control-box.local:3000
  x-base-url-note: The RO1 REST API is served on the robot control box on the local network (default port 3000), not a public
    internet host; the base URL is device-local and per-robot. Enable it in the Standard Bots app under Settings -> Configure
    Developer API.
  properties:
  - type: APIReference
    url: https://docs.standardbots.com/docs/rest-api/
  - type: Authentication
    url: authentication/standard-bots-authentication.yml
  - type: Protobuf
    url: grpc/standard-bots-external-control.proto
common:
- type: DomainSecurity
  url: security/standard-bots-domain-security.yml
- type: Website
  url: https://standardbots.com
- type: DeveloperPortal
  url: https://standardbots.com/developers
- type: Documentation
  url: https://docs.standardbots.com/
- type: APIReference
  url: https://docs.standardbots.com/docs/rest-api/
- type: Support
  url: https://standardbots.com/support
- type: Blog
  url: https://standardbots.com/blog
- type: GitHubOrganization
  url: https://github.com/standardbots
- type: Login
  url: https://admin.standardbots.com
- type: TermsOfService
  url: https://standardbots.com/terms-of-service
- type: PrivacyPolicy
  url: https://standardbots.com/privacy-policy
- type: Packages
  url: packages/standard-bots-packages.yml
- type: SDKs
  url: packages/standard-bots-packages.yml
- type: Authentication
  url: authentication/standard-bots-authentication.yml
- type: Conventions
  url: conventions/standard-bots-conventions.yml
- type: ErrorCatalog
  url: errors/standard-bots-error-codes.yml
- type: X-MCPServerCandidate
  url: mcp/standard-bots-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DataModel
  url: data-model/standard-bots-data-model.yml
- type: Lifecycle
  url: lifecycle/standard-bots-lifecycle.yml
- type: Conformance
  url: conformance/standard-bots-conformance.yml
- type: Sandbox
  url: sandbox/standard-bots-sandbox.yml
- type: Protobuf
  url: grpc/standard-bots-external-control.proto
- type: LLMsTxt
  url: llms/standard-bots-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-07-21'
  status: enriched
  artifacts_added: 15
  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/standard-bots"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/standard-bots/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/standard-bots/evidence"

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

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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