DOCSPontx Hub
Public docsv1
On this pageTypeScript SDKs

SDK / TypeScript + Node.js

Consistent SDK naming, types, and calls.

Each API uses an @pontx/<api-slug> package, generated types, and a dedicated CLI so discovery, verification, and production integration stay aligned.

01Discoverpontx-hub search
02Inspectpontx-hub show
03Previewpontx-hub preview
04Integratepontx-hub sdk
01

The shared package contract

Package names are predictable, types come from the approved OAS, and Hub verifies the exact published release.

Package@pontx/<api-slug>
RuntimeNode.js ≥ 18
ModulesESM + CommonJS
TypesTypeScript declarations
Install
pnpm add @pontx/frankfurter
02

Client shapes follow authentication

Every SDK shares the naming and typing contract; exports accurately reflect each API's auth and call model.

Default client
import currencyExchangeClient from "@pontx/frankfurter";

const result = await currencyExchangeClient.exchangeRates.getLatestRates({
  base: "USD",
  symbols: "JPY,CNY"
});

Endpoint methods are generated from OAS controller/tag and operationId. Follow each API's SDK page instead of assuming every provider has the same auth constructor.

03

Dedicated API CLIs

A published SDK may also expose pontx-<api-slug>, backed by the same generated contract.

Frankfurter dedicated CLI
pnpm add --global @pontx/frankfurter

pontx-frankfurter call exchangeRates.getLatestRates   --base USD   --symbols JPY,CNY   --dry-run
pontx-hubCatalog-wide

Search, resource inspection, Hub preview, and controlled proxy calls.

pontx-<api>One API

Ships with the SDK for local development, CI, and API-specific scripts.

04

Versions and release boundaries

Visitors install published releases. Hub verifies them but never publishes npm packages on a visitor's behalf.

major

Breaking OAS or generated API changes

minor

Backward-compatible Endpoints or fields

patch

Documentation or generator fixes

Browse published SDKs