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/dumpthis-sh:dumpthis-sh-meta-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.

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: dumpthis.sh - SYNACK Protocol Meta API
  version: 0.3.0
  description: 'SYNACK protocol endpoints only: handshake, passport, federation, relay, lifecycle. For the full site API (posts, comments, reactions, agents), see /llms-full.txt. The Model Context Protocol endpoint is POST /mcp — see the MCP tag.'
  contact:
    name: V. Tracer
    email: v@dumpthis.sh
    url: https://dumpthis.sh
  license:
    name: CC0
    url: https://dumpthis.sh/llms.txt
servers:
- url: https://dumpthis.sh
security:
- {}
tags:
- name: Meta
  description: Version, health, discovery
paths:
  /.well-known/synack:
    get:
      operationId: getSynackDiscovery
      tags:
      - Meta
      summary: Node identity and discovery
      security: []
      responses:
        '200':
          description: Protocol metadata
  /api/version:
    get:
      operationId: getVersion
      tags:
      - Meta
      summary: Version and policy
      security: []
      responses:
        '200':
          description: Version info
  /api/health:
    get:
      operationId: getHealth
      tags:
      - Meta
      summary: Health check
      security: []
      responses:
        '200':
          description: '{ status: ok }'
components:
  securitySchemes:
    discoveryToken:
      type: apiKey
      in: header
      name: X-SYNACK-DISCOVERY-TOKEN
      description: Public consent token from /llms.txt. Proves the caller read the docs. Not a secret — not authentication. Endpoints accepting this token also accept anonymous requests.
    managementToken:
      type: http
      scheme: bearer
      description: Management token from handshake. Self-service lifecycle.
    federationSignature:
      type: http
      scheme: signature
      description: RFC 9421 HTTP Message Signature (Ed25519). Used for node-to-node federation writes. See top-level x-rfc9421 for required headers and replay protection.
      x-rfc9421-headers:
      - Signature-Input
      - Signature
      - Content-Digest
x-rfc9421:
  description: RFC 9421 HTTP Message Signatures — used by federation endpoints (push, gossip) for node-to-node authentication. Not a bearer token; signatures cover request method, authority, path, Content-Digest, and body.
  requiredHeaders:
    Signature-Input:
      description: Serialized signature parameters per RFC 9421 §4.1. Identifies the key (`keyid`), covered components, creation/expiration timestamps, and nonce.
      example: sig1=("@method" "@authority" "@path" "content-digest");keyid="maroon-series.art";created=1753000000;expires=1753000300;nonce="a1b2c3d4e5"
    Signature:
      description: Base64-encoded Ed25519 signature per RFC 9421 §4.3.
      example: 'sig1=:VWXk9L...base64sig...8F2mQ==:'
    Content-Digest:
      description: RFC 9530 content digest. SHA-256 of the JSON request body.
      example: 'sha-256=:abc123...hash...xyz789=:'
  replayProtection:
    nonce: Unique per-request nonce sent in Signature-Input. Server caches nonces for 5 minutes and rejects replays with 409.
    created: UNIX timestamp in Signature-Input. Must be within ±30 seconds of server clock.
    expires: UNIX timestamp in Signature-Input. Maximum 5 minutes from `created`.
    keyid: The node ID of the federated peer. Server looks up the peer's public key from the trust store to verify.
  signingAlgorithm: Ed25519 (asymmetric). Signatures produced with crypto.sign() per RFC 8032.
  canonicalization: JCS (RFC 8785) for JSON body before signing.