OPENSDK — DOCS IN. SDK OUT.  •  NO HAND-WRITTEN CLIENTS  •  NO REVERSE ENGINEERING  •  TYPE-SAFE TYPESCRIPT  •  OPENAPI NATIVE  •  SPEC-FIRST  •  14 FEATURE MODULES  •  AUTH • RETRIES • PAGINATION • STREAMING • INTERCEPTORS  •  FREE TO START  •   OPENSDK — DOCS IN. SDK OUT.  •  NO HAND-WRITTEN CLIENTS  •  NO REVERSE ENGINEERING  •  TYPE-SAFE TYPESCRIPT  •  OPENAPI NATIVE  •  SPEC-FIRST  •  14 FEATURE MODULES  •  AUTH • RETRIES • PAGINATION • STREAMING • INTERCEPTORS  •  FREE TO START  • 
The fastest way to turn docs into SDKs

Every doc.
Every endpoint.
One SDK.

Turn API documentation into production-ready SDKs. OpenSDK examines your docs, builds the spec, and generates typed client code. No manual work. No maintenance.

Documentation
Live Demo
$curl -X POST https://opensdk.ca/api/dispatch \
-H "X-API-Key: sk_..." \
-d '{"url": "https://docs.acme.com/api"}'
+ Analyzed documentation (42 pages)
+ Extracted 24 endpoints, 18 schemas
+ Detected Bearer auth, cursor pagination, retries
+ Built API spec (OpenAPI 3.1)
+ Generated TypeScript SDK with 14 feature modules
+ Package ready @acme/sdk
import { AcmeClient } from "@acme/sdk"
const users = await client.users.list({ limit: 10 })
Zero runtime dependencies

Extract endpoints, build OpenAPI specs, generate type-safe SDKs

Capabilities

Read and Build.

Extract endpoints, schemas, and auth from real API docs. Review the spec, then generate production-ready SDKs.

DOCScrawl /reference
Examine documentation
Crawl reference docs, guides, examples, and changelogs. Every page becomes structured input.
Any size
SPECbuild /spec
Build API spec
Turn unstructured docs into a structured OpenAPI-style spec. Endpoints, schemas, auth — all extracted.
Auto-extracted
SDKgenerate /sdk
Generate TypeScript SDK
Typed client with auth, retries, pagination, streaming, interceptors, typed errors, multipart, idempotency, and environment config. 14 feature modules.
AST-generated
REVISErevise /task
Revise your SDK
Describe changes in plain text and OpenSDK re-analyzes and regenerates. Adjust endpoints, schemas, and behavior without starting over.
Text-based
EXPORTexport /sdk
Export package
Download the generated SDK as source files or a tarball, or export the inferred OpenAPI spec as JSON.
SDK · OpenAPI · TGZ
IMPORTimport /spec
Import OpenAPI spec
Skip the analysis step entirely. Feed an existing OpenAPI 3.1 spec directly into the pipeline for deterministic, zero-AI SDK generation.
OpenAPI 3.1
Process

Docs in. SDK out.

From raw documentation to a production-ready SDK in minutes.

01
Point at your docs
curl -X POST https://opensdk.ca/api/dispatch \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://docs.stripe.com/api", "task": "charges, customers, and refunds"}'
02
OpenSDK builds your spec
+ Analyzed docs.stripe.com/api (48 pages)
+ Extracted 24 endpoints, 18 schemas, 3 environments
+ Detected OAuth2 auth, cursor pagination, retries
+ Detected idempotency, streaming, multipart uploads
+ Detected typed errors, per-endpoint timeouts
+ Built spec → OpenAPI 3.1
03
Get your SDK
curl https://opensdk.ca/api/dispatch/tasks/abc-123/export/sdk \
  -H "X-API-Key: YOUR_API_KEY"

+ Generated client: StripeClient
+ Generated 47 typed methods, 86 models
+ Included: auth, retries, pagination, streaming, interceptors
+ Included: typed errors, idempotency, multipart, environments
+ Ready → download .zip
Spec-First

One spec.
Every integration.

Connect your docs once. OpenSDK builds a reusable API spec and generates SDKs your team can ship immediately. Works with any REST API documentation.

No hand-written clients. No reverse-engineering from scattered docs. One source of truth for every integration.

Docs Source
curl -X POST https://opensdk.ca/api/dispatch \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://docs.acme.com/api"}'

Works with any REST API docs. OpenAPI, Swagger, or unstructured reference pages.

Credits

Pricing.

Start free with 100 credits. Buy more when you need them. No subscriptions, no surprises.

Starter
Free
100 credits
  • +100 credits on signup
  • +~4 SDK generations
  • +Full TypeScript output
  • +API key access
100 Pack
$9
100 credits
  • +100 API credits
  • +Dispatch, revise, export
  • +No expiration
  • +Instant top-up
500 Pack
$39
500 credits
  • +500 API credits
  • +Best value for teams
  • +No expiration
  • +Instant top-up
2,000 Pack
$149
2,000 credits
  • +2,000 API credits
  • +Best for high volume
  • +No expiration
  • +Instant top-up
Enterprise
Custom
Volume pricing
  • +Custom credit volumes
  • +Dedicated support and SLA
  • +Private deployments
  • +Team workflows
FAQ

Common questions.

Getting started, pricing, and how it all works.

01How do I get started?
Sign up at opensdk.ca and create an API key from the dashboard. Every new account gets 100 free starter credits. Then use the REST API to submit a docs URL or OpenAPI spec and generate your SDK.
02How does pricing work?
OpenSDK uses a one-time credit system — no subscriptions. Every new account gets 100 free starter credits. Dispatching a task costs 25 credits, revising costs 10, and exporting costs 5. Buy more credits anytime from the billing dashboard. Credits never expire.
03Can I change the SDK after it's generated?
Yes. After OpenSDK generates your SDK, you can revise it with plain-text instructions — describe what to change (e.g. 'add retry logic', 'rename the users endpoint') and OpenSDK re-analyzes and regenerates. No starting over.
04What languages are supported?
TypeScript is the fully supported target language. The architecture supports adding more languages through the generator plugin system — each new language is a separate template module.
All credit usage is tracked in real time on your billing dashboard

Documentation
becomes developer tools.

You already have the docs. OpenSDK turns them into structured specs and production-ready SDKs. Free to start. No credit card.

Start Building →