Server-Side SDK

The server-side SDK. Install it with pip install pulp-sdk, then reach the three engines as first-class namespaces on one client. Under the hood every call hits the HTTP API at https://api.pulp.dev/v1 over HTTPS with JSON bodies and a bearer key in the Authorization header. pk_test_ keys are sandboxed and free; pk_live_ keys meter against your plan.

Three engines, one question each. Radiance, Windfall, and Groundwater depend on nothing and compose freely. Building for the browser? Reach for loosethreads UI, the React SDK that turns these engines into living conversations.

Packages

Conventions

• Versioning. Date-pinned per key (for example 2026-07-01). We will never move your integration under you; you upgrade when you choose.
• Idempotency. Send an Idempotency-Key header on any write and retries become safe. Simulations are expensive thoughts; you should never pay for the same one twice because a router blinked.
• Errors. Machine-readable, human-decent. A JSON body with type, code, message, and a doc link.
• Webhooks. Subscribe to simulation.completed, batch.finished, score.threshold_crossed, and friends. Payloads are signed; verification is one SDK call.
• Rate limits. Radiance calls are cheap and limited high. Windfall simulations are metered by persona-message pairs. ServerCore batch is queued, not limited. Headers tell you where you stand on every response.
• Install. pip install pulp-sdk, then from pulp import Pulp. The client reads PULP_API_KEY from the environment, so the key never lands in code. Every call on these pages is Python.
• Brand casing. The web SDK is always written loosethreads, all-lowercase. Its component names stay PascalCase (WarpDisplays, WeftConversations, DyeMedia, BightInteractions) because JSX requires capitalized component identifiers.

Start with Radiance, the reason to be here.