Skip to main content

Why Build Your Research Assistant with Bigdata.com?

Bigdata.com is designed specifically for business and finance professionals, delivering real-time, AI-driven insights with precision and speed. Unmatched Data Access — Instantly analyze vast, high-quality datasets.
Finance & Business Expertise — Designed for professionals, not generic use.
Seamless Integration — Easily power your chatbot with cutting-edge AI.
In just 5 minutes, you’ll learn how to: ✅ Create your API Key
✅ Craft a research prompt
✅ Chat with Bigdata.com Research Agent
✅ Advance filters: temporal, entity, sources
Ready to get started? Let’s dive in!
Choose research_effort equal to lite for a quick response, equivalent to the former Chat Service experience.

Create your API Key

Please click here to create your API Key: Developer Platform > API Keys

Craft a research prompt

The Research Agent accepts complex prompts, you can specify the role to the LLM, describe the research steps that you want to follow, and the output format you want. Example:

Chat with Bigdata.com Research Agent

The following script sends a single request to the Research Agent API using the Deep Research mode and starts printing the response as it comes. You can control the research effort with the parameter research_effort. It supports two values:
  • lite: Quick response, equivalent to the former Chat Service experience.
  • standard: The Research Agent will perform multiple steps until it has enough data to respond. It conducts Deep Research, and we recommend it for complex prompts.
Output:

Next steps

The example above only handles ANSWER, GROUNDING, and COMPLETE events. A production integration should also handle planning, tool calls, retries, and errors. The Concepts guides cover everything the stream can emit and how to respond to each.

Streaming responses

The 11 message types, their fields, and a complete dispatching handler.

Grounding and citations

Render the references you just collected as inline Markdown citations.

Error handling

HTTP-level errors, in-stream ERROR vs TOOL_ERROR vs LLM_RETRY, and retry strategy.

Conversation continuity

Continue Research Agent chats with chat_id and checkpoint_id.

Non-streaming print

Buffer the stream and print the complete answer in one go.

Monitor usage

See a breakdown of your organization’s usage per service.