Skip to main content
Each cookbook builds one complete workflow, from the first API call to results stored in your own system.

Recipes

Split, then extract

Find each section of a long report, then fill a small schema for each.

Highlight sources

Draw the exact words behind an extracted value on its page.

RAG ingestion

Index a document’s chunks with metadata that cites their pages.

Cloud intake

Parse a whole bucket as one batch and write each result back to it.

Before you start

The recipes are in Python; the TypeScript SDK has the same calls, with camelCase names. Each recipe starts from this client (SDKs covers setup):

From test to production

Most integrations take this path: Save the settings that work as a saved config, and send its config_id with each pipeline or batch. Then store each result in your own system: a result can expire, and some organizations delete a result the first time it’s read.

Sample documents

Each name opens a hosted test document in the dashboard. To use one in an API call, send https://platform.runpulse.com/api/examples/<id>/pdf as the file_url.