Explore the directory
↑ ↓ to navigate · Enter to openEsc to close
Skip to article
Introduction

Introduction

Better integrations start with better choices. Find the right SDK, understand its tradeoffs, and build a boundary your application can live with.

Quickstart
On this page

What is SDK SDK?

SDK SDK is an independent, curated discovery hub for software development kits. We bring useful libraries, official documentation, and practical integration lessons into one place so you can spend less time comparing tabs and more time building.

Find your starting point

Make your first API callA real Resend integration, from install to response.Choose with confidenceA short evaluation framework for your next dependency.Explore SDKsBrowse the directory by the job you need to do.Build a reliable boundaryDeclare capabilities before adding abstractions.

A small integration loop

  1. Start with a job. Describe the outcome: send a receipt, retrieve a page, or save an order. List the constraints that would rule a provider out.
  2. Read the primary docs. Check the supported runtime, authentication, response model, and limits for the exact operation you need.
  3. Try the native client. Make one successful call before deciding what your own integration boundary should expose.
  4. Test the failure path. Add deterministic fixtures, a deadline, and a clear policy for retries and sensitive data.

Principles worth keeping

PrincipleIn practice
Explicit capabilitiesA provider supports a specific operation, with specific semantics. Make that visible.
Deterministic mocksTest fixtures control IDs, time, errors, and ordering. A mock never quietly calls a live provider.
Honest data typesA search snippet is not a retrieved page. A retrieved page is not a generated answer.
Bounded recoveryA retry spends time and money. A fallback can send data to another company.
Native escape hatchesKeep access to useful provider-specific features instead of reducing every SDK to the same surface.

Using these docs

Official provider examples are identified and linked to their sources. Examples labeled app-owned are illustrative TypeScript patterns you can adapt; they are not exported by SDK SDK or guaranteed to match a provider's API. Always check the installed version's documentation before shipping.

Start small. A direct call to the official SDK is often enough. Add your own abstraction when it makes a real requirement—such as testing, provider selection, or observability—easier to express.

SDK SDK is an independent discovery hub. Provider examples link to official documentation. App-owned examples are illustrative patterns you can adapt.