@varve/agency-sdks

Introduction

Open-source TypeScript SDKs for official statistics, built for validated and reproducible data access.

Varve agency SDKs are open-source TypeScript clients for official statistical APIs.

They exist because public data APIs are often authoritative but difficult to use safely. Response shapes drift from documentation, identifiers are provider-specific, pagination rules differ, and error payloads are rarely consistent. These packages wrap those APIs in small, typed clients that validate every response before your application treats it as usable data.

The broader Varve thesis is simple: official numbers should be cited, reproducible, and refused when they cannot be proven. These SDKs are the provider-level access layer behind that idea.

What you get

  • Typed clients for official statistical providers
  • Runtime validation with Zod for every parsed response
  • Isomorphic fetch support for Node.js 18+, browsers, Workers, and edge runtimes
  • Provider-specific retries for transient agency failures and rate limits
  • Exported schemas and types for downstream validation pipelines
  • Documented quirks where live API behavior differs from provider docs

Packages

How the docs are organized

Start with Getting Started if you want to install a package and make a first request.

Use Choosing a Provider when you know the data problem but not the package.

Read the Core Concepts pages when you want to understand validation, retries, runtime behavior, and graph metadata across packages.

Provider sections contain the practical reference: data model, common workflows, configuration, errors, official references, and deeper guides where a package needs them.

Trust boundary

The SDKs verify the shape and transport behavior of official API responses. They do not decide whether a particular indicator, geography, seasonal adjustment, frequency, or transformation is analytically correct for your use case.

In other words: they make official data access more reproducible and easier to trust, while keeping provider ambiguity visible.

On this page