SDKs - Outcrawl

Outcrawl provides two official SDKs. There is no third, everything either one does not cover is reachable the same way: plain HTTP.

TypeScript SDK

npm install @outcrawl/sdk, zero runtime dependencies, the only client with live browser control.

Python SDK

pip install outcrawl, pure Python, one wheel for every OS, async and context managed.

Which one should I use?

	TypeScript	Python
Package	`@outcrawl/sdk`	`outcrawl`
Install	`npm install @outcrawl/sdk`	`pip install outcrawl`
Registry	npm	PyPI
Requirement	Node.js, zero runtime deps	Python 3.10+, one dependency (`httpx`)
Async model	Promises	`async`/`await`, context managed
Scrape, crawl, search	Yes	Yes
Agents (submit, watch, cancel, hand off to a person)	Yes	Yes
Live browser control (`oc.browser()`)	Yes	No, TypeScript SDK only
Monitors, profiles, secrets, rules, integrations	Yes	Yes
Usage and credits	Yes	Yes

The one real asymmetry: live browser control needs a CDP connection held open in the caller’s own process, so it exists only in TypeScript. Python reaches the same underlying page work through agent and scrape, which run the loop on the platform’s own side rather than the caller’s, a difference in kind rather than a missing feature.

Authentication

Both SDKs read the same credential the same way: an API key, ock_<keyId>.<secret>, from the OUTCRAWL_API_KEY environment variable, or passed directly at construction. Generate one from the console at https://outcrawl.ai/console/keys.

ock_YOUR_KEY_ID.YOUR_SECRET