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/aztecprotocol-status-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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Aztecprotocol Status API
  version: '2026-09-27'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-09-27: 4 operation(s) read from 8 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Aztecprotocol has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 3
    documentation: 1
    pages-with-code: 7
    pages-read: 8
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-09-27'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://docs.aztec.network/developers/docs/resources/migration_notes
  - https://docs.aztec.network/developers/docs/tutorials/contract_tutorials/token_contract
  - https://docs.aztec.network/developers/docs/tutorials/contract_tutorials/counter_contract
  - https://docs.aztec.network/developers/getting_started_on_testnet
  - https://docs.aztec.network/developers/getting_started_on_local_network
  - https://docs.aztec.network/developers/docs/tutorials/testing_governance_rollup_upgrade
  - https://docs.aztec.network/developers/docs/tutorials/contract_tutorials/recursive_verification
  - https://docs.aztec.network/developers/docs/tutorials/js_tutorials/webapp/the-contract
servers:
- url: https://install.aztec.network
tags:
- name: Status
paths:
  /status:
    get:
      operationId: get_status
      tags:
      - Status
      summary: GET /status now returns a JSON body with per-component health
      x-source: https://docs.aztec.network/developers/docs/resources/migration_notes
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetStatusResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    GetStatusResponse:
      type: object
      properties:
        ok:
          type: boolean
          description: overall health flag
        components:
          type: object
          description: map of component names to their health status
        components.p2p.healthy:
          type: boolean
          description: whether the p2p component is healthy
        components.p2p.enabled:
          type: boolean
          description: whether the p2p component is enabled
        components.p2p.connectedPeers:
          type: integer
          description: number of connected peers