Drag Bot
drag&bot is a web-based industrial robotics software platform for the intuitive setup, programming, and operation of industrial robots without prior robotics or coding skills. Founded in Stuttgart in 2016 and acquired by KEBA in 2021, it lets production workers assemble robot programs by dragging and dropping reusable Function Blocks. The platform is built on ROS (Robot Operating System), making it vendor-neutral across robot brands such as KUKA, ABB, Universal Robots, FANUC, Denso, Kinova, and Aubo, as well as a wide range of grippers and peripheral tools. Developers extend the platform with Python/JSON Function Blocks and ROS-based Components (hardware drivers), and integrate with factory equipment over Modbus TCP/IP and MQTT. drag&bot has been integrated into KEBA's Kemro X automation platform. Its programmatic surface is exposed as ROS services, topics, and messages rather than a public REST/HTTP API.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Drag Bot the way a machine reads it — 1 machine-readable artifact, 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 — Drag Bot scores 13.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Drag Bot
Each block below is one kind of artifact we hold for Drag Bot. 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.
Security Posture 1
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.
Resources
Every other property we hold for Drag Bot — 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 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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/drag-bot · machine-readable index on apis.io