Casperlabs API
Casperlabs API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-07); not the provider's own document.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/casperlabs:casperlabs-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.1.0
info:
title: Casperlabs API
version: '2026-10-07'
description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-07: 3 operation(s) read from 2 public documentation page(s) (each operation
names its page in x-source). This is not the provider''s published contract; Casperlabs has published no machine-readable contract that the
pipeline could find. Engine: local.'
x-evidence-tiers:
code-example: 1
documentation: 2
pages-with-code: 2
pages-read: 2
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-07'
x-generator: generate-contract-from-docs.py
x-engine: local
x-sources:
- http://docs.casper.network/next/operators/setup/node-endpoints
- http://docs.casper.network/1.5.X/operators/setup/node-endpoints
servers:
- url: http://<node_address>:8888
paths:
/:
get:
operationId: get
tags:
- Api
summary: GET /
x-source: http://docs.casper.network/next/operators/setup/node-endpoints
responses:
'200':
description: Success (shape read from the example response on the page)
content:
application/json:
schema:
$ref: '#/components/schemas/GetResponse'
x-evidence:
kind: code-example
language: curl
snippet: "curl -s http://<node_address>:8888/metrics \n You can check the node's status using this command: "
/metrics:
get:
operationId: get_metrics
tags:
- Metrics
summary: Node Endpoints
description: 'Retrieves general health metrics of the node. Example usage: `curl -s http://<node_address>:8888/metrics`.'
x-source: http://docs.casper.network/next/operators/setup/node-endpoints
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: documentation
/status:
get:
operationId: get_status
tags:
- Status
summary: Node Endpoints
description: 'Provides a JSON response with node status information. Example usage: `curl -s http://<node_address>:8888/status | jq`.'
x-source: http://docs.casper.network/next/operators/setup/node-endpoints
responses:
'200':
description: Success (status as documented)
content:
application/json:
schema:
$ref: '#/components/schemas/GetStatusResponse'
x-evidence:
kind: documentation
components:
schemas:
GetResponse:
type: object
properties:
api_version:
type: string
chainspec_name:
type: string
starting_state_root_hash:
type: string
peers:
type: array
items:
type: object
properties:
node_id:
type: string
address:
type: string
last_added_block_info:
type: object
properties:
hash:
type: string
timestamp:
type: string
format: date-time
era_id:
type: integer
height:
type: integer
state_root_hash:
type: string
creator:
type: string
our_public_signing_key:
type: string
round_length:
type: string
next_upgrade:
type:
- string
- 'null'
build_version:
type: string
uptime:
type: string
GetStatusResponse:
type: object
properties:
api_version:
type: string
description: The RPC API version
chainspec_name:
type: string
description: The chainspec name, used to identify the currently connected network
starting_state_root_hash:
type: string
description: The state root hash used at the start of the current session
peers:
type: array
description: The node ID and network address of each connected peer
last_added_block_info:
type: object
description: The minimal info of the last Block from the linear chain
our_public_signing_key:
type: string
description: Our public signing key
round_length:
type: string
description: The next round length if this node is a validator
next_upgrade:
type: string
description: Information about the next scheduled upgrade
build_version:
type: string
description: The compiled node version
uptime:
type: string
description: Time that has passed since the node has started
tags:
- name: Api
- name: Metrics
- name: Status