How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

StakPak Runners (V2) API

The Runners (V2) API from StakPak — 6 operation(s) for runners (v2).

StakPak Runners (V2) API is one of 20 APIs that StakPak publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Runners (V2). The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 9 operations across 6 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://apiv2.stakpak.dev, http://localhost:4000.

9 operations 6 paths 17 schemas 4 GET1 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://apiv2.stakpak.dev
Authentication
HTTP Bearer, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

StakPak Runners (V2) API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Api_Key). It accepts HTTP bearer tokens (JWT) (Token). An API key is passed in the cookie as .idToken (cookie).

Paths & Operations 9

Across 6 paths, the API surfaces 9 operations — 4 GET, 1 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Runners (V2) 9
GET
/v2/{account}/runners
List Runners
list_runners_handler → 200400
POST
/v2/{account}/runners
Create Runner
create_runner_handler body → 200400
GET
/v2/{account}/runners/{machine_name}
Get Runner
get_runner_handler 1 param → 200400
PATCH
/v2/{account}/runners/{machine_name}
Update Runner
update_runner_handler 1 param body → 200400
GET
/v2/{account}/runners/{machine_name}/check-upgrade
Check Runner Upgrade
check_runner_upgrade_handler 1 param → 200400
GET
/v2/{account}/runners/{machine_name}/secrets
Get Runner Secrets
get_runner_secrets_handler 1 param → 200400
POST
/v2/{account}/runners/{machine_name}/secrets
Create Runner Secret
create_runner_secret_handler 1 param body → 200400
POST
/v2/{account}/runners/{machine_name}/trigger
Trigger Runner
trigger_runner_handler 1 param body → 200400
POST
/v2/{account}/runners/{machine_name}/upgrade
Upgrade Runner Version
upgrade_runner_handler 1 param → 200400

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are GithubActionsRunner (9 properties), Runner (7 properties), CreateRunnerPayload (7 properties), CheckRunnerUpgradeResponse (3 properties). Each schema is shown below with its type and property counts.

UpdateRunnerPayload
object
1 property
TriggerRunnerPayload
object
1 property 1 required
GithubActionsRunner
object
9 properties 7 required
RunnerSecret
object
3 properties 3 required
ErrorBody
object
2 properties 2 required
GithubIntegration
object
2 properties 2 required
CreateRunnerSecretPayload
object
2 properties 2 required
CloudConfiguration
GithubActionsConfig
object
1 property
RunnerProvider
GetRunnerSecretsResponse
object
1 property 1 required
GithubActionsRunnerStatus
string
CreateRunnerPayload
object
7 properties 5 required
Runner
object
7 properties 5 required
ListRunnersResponse
object
1 property 1 required
CheckRunnerUpgradeResponse
object
3 properties 3 required
ErrorResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stakpak-runners-v2-api-openapi.yml Raw ↑

Other APIs StakPak publishes across the network.

StakPak Account API
StakPak Account (V2) API
StakPak Agents API
StakPak Agents (V2) API
StakPak Billing (V2) API
StakPak Chat API
StakPak Commands API
StakPak Knowledge API
StakPak Knowledge Registry API
StakPak MCP API
StakPak Memory API
StakPak Memory (V2) API
Where this information came from

This is an independent, third-party profile of StakPak Runners (V2) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.