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/cadencetranslate-com:cadencetranslate-com-public-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: Cadence Translate Public API
  description: API for translating text using the Cadence Translate service.
  version: 1.0.0
tags:
- name: Public
paths:
  /health:
    get:
      tags:
      - Public
      summary: Health
      description: Health check endpoint.
      operationId: health_health_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Response_NoneType_'
  /.well-known/jwks.json:
    get:
      tags:
      - Public
      summary: Jwks
      description: 'JWKS document (RFC 7517) for verifying RS256-signed access tokens.


        No auth, public by design (NP-1131) - matches the OIDC/RFC-8414

        well-known discovery convention, so it returns the bare JWKS shape

        rather than the ``Response[...]`` envelope other endpoints use.'
      operationId: jwks__well_known_jwks_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Jwks  Well Known Jwks Json Get
  /.well-known/editor-jwks.json:
    get:
      tags:
      - Public
      summary: Editor Jwks
      description: 'JWKS document (RFC 7517) for verifying ES256-signed Mega Editor V2

        editor tokens (NP-1276). Separate from ``jwks()`` above: a distinct

        keyset, algorithm and audience from NP''s own RS256 session tokens.


        No auth, public by design, same rationale as ``jwks()``.


        404s where no editor keys are configured, rather than letting

        ``build_editor_jwks()`` raise on an empty PEM. Keyed on the keys

        themselves, deliberately not on ``MEGA_EDITOR_V2_ROLLOUT_ENABLED``: an

        environment that has already run the pilot keeps serving this document

        after the rollout flag is switched off, so tokens held by tasks still in

        flight keep verifying.'
      operationId: editor_jwks__well_known_editor_jwks_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Editor Jwks  Well Known Editor Jwks Json Get
components:
  schemas:
    Response_NoneType_:
      properties:
        message:
          type: string
          title: Message
          default: Operation successful
        success:
          type: boolean
          title: Success
          default: true
        data:
          type: 'null'
          title: Data
        errors:
          anyOf:
          - additionalProperties:
              type: string
            type: object
          - type: 'null'
          title: Errors
      type: object
      title: Response[NoneType]