Limrun
Limrun (Limrun, Inc.) is a Y Combinator-backed cloud infrastructure company for mobile development, built so cloud coding agents and Linux CI runners can build, run, and test iOS and Android apps without a Mac. Limrun exposes three composable cloud services behind one REST control plane at api.limrun.com: iOS simulators running on real Macs (streamable in a browser and drivable programmatically through taps, screenshots, accessibility element trees, video recording, and app lifecycle), remote Xcode and Bazel build sandboxes that accept synced sources and run xcodebuild or remote build execution, and accelerated Android emulators reachable over an ADB tunnel by Android Studio, Appium, or scrcpy. Gradle build sandboxes and a managed Asset Storage service for .apk and .app build artifacts round out the platform. Every instance is created through the control plane with an org API key and returns its own per-instance token, data-plane URLs, a signed browser stream URL, and its own Model Context Protocol server, which makes Limrun one of the few providers shipping a per-instance MCP endpoint alongside first-party Agent Skills for coding agents.
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 Limrun the way a machine reads it — 13 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 — Limrun scores 45.9/100 (developing), with a separate agent-readiness read of 78/100 (agent native). 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 Limrun
Each block below is one kind of artifact we hold for Limrun. 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.
Limrun Analytics API
The Analytics API from Limrun — 3 operation(s) for analytics.
Limrun Android Instances API
The Android Instances API from Limrun — 2 operation(s) for android instances.
Limrun Assets API
The Assets API from Limrun — 2 operation(s) for assets.
Limrun Downloads API
The Downloads API from Limrun — 1 operation(s) for downloads.
Limrun Gradle Instances API
The Gradle Instances API from Limrun — 2 operation(s) for gradle instances.
Limrun Ios Instances API
The Ios Instances API from Limrun — 2 operation(s) for ios instances.
Limrun Xcode Instances API
The Xcode Instances API from Limrun — 4 operation(s) for xcode instances.
Scroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
limrun-mcp.yml
MCP SERVERSecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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 Limrun — 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 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/limrun · machine-readable index on apis.io