Latchkey Jobs API Jobs API

Create, submit, observe and cancel runner jobs.

Business capability
Continuous Integration Management BC-4210.10

Operations 7

POST /jobs Create a job #
GET /jobs List recent jobs #
GET /jobs/{id} Get job status #
POST /jobs/{id}/submit Submit a job for execution #
PUT /jobs/batches/{batch}/budget Set or lower a batch's budget #
GET /jobs/{id}/logs Read job logs #
POST /jobs/{id}/cancel Cancel a job #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/latchkey:latchkey-jobs-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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

OpenAPI Specification

latchkey-jobs-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Latchkey Jobs API
  version: 1.0.0
  summary: Run a single command on a fresh Latchkey runner, with no GitHub in the path.
  description: 'The Jobs API gives a coding agent or CI system direct access to an ephemeral Latchkey runner. A job runs ONE command on a fresh Ubuntu 24.04 x86_64 machine that is destroyed afterwards. Nothing registers with GitHub, so jobs keep running when GitHub Actions is unavailable.


    Typical lifecycle: create a job, optionally upload a context archive to the returned presigned URL, submit it, then poll status and stream logs until a terminal state.


    The Model Context Protocol server is documented separately at https://latchkey.dev/.well-known/mcp/manifest.json.


    Authentication is a Latchkey API key sent as a bearer token. Keys are created in the Latchkey dashboard and carry scopes: `jobs:read` for status, logs and listing; `jobs:run` for create, submit and cancel.'
  contact:
    name: Latchkey Support
    url: https://latchkey.dev/support
    email: support@latchkey.dev
  license:
    name: Proprietary
    url: https://latchkey.dev/terms
servers:
- url: https://api.latchkey.dev
  description: Production
security:
- latchkeyApiKey: []
tags:


# --- truncated at 32 KB (32 KB total) ---
# Full source: https://artifacts.apis.io/latchkey/openapi/latchkey-jobs-api-openapi.yml