The Reasoning API returns precise, structured AI signals rather than long-form conversational answers, so it's well suited to populating fields and scoring models. It runs on named reasoning agents that Databook configures for you, and it supports a deep reasoning mode for questions that need more analytical depth.
Use the Reasoning API when you need a structured signal to feed into another system, for example a CRM field or a scoring model. If you need a conversational answer for a person to read, use the Chat API instead.
What it can do
Return structured output: responses come back as JSON, so they can be mapped directly into fields, scores, or downstream systems
Run on demand or in bulk: a single call can return a signal for one account, for example an account point of view surfaced inside your CRM, or runs can be scoped for bulk use across many accounts, for example territory scoring
Apply deep reasoning: a deep reasoning mode is available for questions that need more analytical depth than a standard lookup
Draw on the same engine as DatabookAI: answers use the same premium data sources and underlying reasoning as the rest of Databook
How it works
Authenticate to obtain an access token.
Call the reasoning endpoint, naming the reasoning agent you want to run and passing any parameters it needs.
Databook executes that agent and returns a structured response.
Example use cases
CRM fields: populate an account point of view field in Salesforce with a structured, up-to-date signal
Scoring models: feed territory scoring or account prioritization models with structured Databook signals
Structured enrichment: add precise, machine-readable signals anywhere your systems need more than free text
Getting access
Reasoning API access requires an entitlement and credentials issued by Databook. The reasoning agents you want to run also need to be configured by Databook first, so scoping runs through your account team. For bulk use cases like territory scoring, your account team will help scope and configure the run. Full request and response detail is in the API documentation portal.