Create a Research Object via x402
Start a new research job using x402 payment. This endpoint mints a temporary API key that is returned in the response and is billed via the x402 settlement flow instead of your Caesar API credits.
Headers
X-PAYMENT
Base64-encoded x402 payment payload.
Request
This endpoint expects an object.
query
Primary research question or instruction.
reasoning_loops
Maximum number of iterative reasoning cycles the research process can perform.
source_timeout
Maximum time in seconds to wait when fetching content from each source URL.
reasoning_mode
When enabled, uses an advanced reasoning model for deeper analysis.
allow_early_exit
When enabled, the research process may complete before exhausting all reasoning loops.
excluded_domains
List of domains to exclude from search results (e.g., “example.com”). Subdomains are also excluded.
auto
When enabled, activates auto mode which analyzes the query to determine optimal configuration.
system_prompt
Custom system prompt to guide the research synthesis.
model
Preferred AI model to use for research synthesis. Valid values are “gpt-5.2”, “gemini-3-pro”, “gemini-3.1-pro”, “gemini-3-flash”, or “claude-opus-4.5”. When not specified, the system automatically selects an appropriate model.
Response
Research job accepted and x402 payment settled.
id
Research job identifier.
status
Current status of the research job:
queued: Job accepted, waiting to startsearching: Gathering sources from the webresearching: Processing and analyzing sourcesanalyzing: Deep analysis of gathered informationsummarizing: Generating final synthesiscompleted: Research finished successfullyfailed: Research encountered an error
api_key_secret
Temporary API key secret created for this x402 request.
Errors
400
Bad Request Error
402
Payment Required Error
500
Internal Server Error