Shani Einav

Overview Reindeer document workflows are designed for real operational documents, not only clean digital PDFs. Reindeer can read business documents, parse them into structured information, classify...

Overview Some workflows receive multiple documents, emails, or updates that refer to the same real-world business item. In those workflows, the goal is not always "one input equals one case." The g...

Overview An agent case schema defines the business fields Reindeer tracks for each case in a workflow. It is the shared contract between the agent, the case page, reviewers, reporting, and any conn...

Overview Reindeer case pages can be configured to match the way each workflow is reviewed. This means different agents can show different fields, actions, layouts, statuses, and review controls dep...

Overview Use the external case PATCH endpoint to update case state after a review, correction, or operator action. The endpoint uses optimistic locking so concurrent edits do not silently overwrite...

Overview The case state schema defines the expected structure of the JSON state returned for each case by the external API. It helps API clients, case views, and derived keywords agree on where imp...

Overview Display settings control how an agent's case data appears in Reindeer case views. They are configured on the agent through the external API and are separate from the case state itself. Use...

Overview Reindeer agents store working data for each case in a JSON object called case state. The external API lets teams read and update that state, define the expected schema, and configure which...

What a Context Is and Why It Matters A context is one artifact file that gives an agent business knowledge or instructions for a specific workflow. Think of it as a document you would give a new te...

The Cases Aggregation API returns case counts for an agent, either as a single total or grouped by case keywords. Use it to track case volume and monitor the distribution of keyword values (for exa...