For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DocumentationAPI ReferenceChangelog
DocumentationAPI ReferenceChangelog
  • Get Started
    • Introduction
    • Authentication
    • Rate Limits
    • Pricing
  • Integration
    • MCP Server
    • SDKs
    • OpenAI Compatibility
    • MCP Docs Server
    • llms.txt
    • x402
  • Guides
    • Research Parameters
    • Research Chat
    • Brainstorming
    • Model Selection
    • Prompt Guidance
    • Versioning
  • Reference
    • Errors
    • Pagination
On this page
  • Writing effective queries
  • Be specific about your domain
  • More examples of explicit queries
  • Output transformation with system_prompt
  • How it works
  • Request example
  • Response structure
  • Common transformation patterns
  • Key principles
  • Tips for optimal results
Guides

Prompts

Built with

Caesar is a horizontal general solution for research that works across domains without requiring specialized prompt engineering. While Caesar doesn’t need complex prompting strategies, being explicit in your queries will yield better, more targeted results.

Writing effective queries

Caesar performs best when queries are clear and unambiguous. While the system is designed to understand context, explicit queries reduce ambiguity and improve result quality.

Be specific about your domain

When your query involves terms that could have multiple interpretations, provide context to guide the research.

What are the top tokens in the virtuals agent ecosystem?

The first query clarifies you’re asking about tokens within the “virtuals agent ecosystem,” avoiding ambiguity around what “virtuals” means.

More examples of explicit queries

Financial research

Instead of: “Apple performance”

Use: “Apple Inc. (AAPL) stock performance in Q3 2024 compared to tech sector peers”

Technology analysis

Instead of: “React vs Vue”

Use: “Comparison of React and Vue.js frameworks for enterprise web applications in 2024”

Market research

Instead of: “EV market”

Use: “Electric vehicle market penetration rates in European countries 2023-2024”

Cryptocurrency

Instead of: “Best L2s”

Use: “Top Ethereum Layer 2 scaling solutions by TVL and transaction throughput”

Output transformation with system_prompt

The POST /research endpoint accepts an optional system_prompt parameter that allows you to transform the final output format.

The system_prompt only affects the output format, not the research logic. Caesar performs the same comprehensive research regardless of the promptit only changes how the results are presented.

How it works

When you provide a system_prompt:

  1. Caesar performs the research using your query
  2. The research results are stored in the content field
  3. The system prompt is applied to transform the content
  4. The transformed result appears in transformed_content

Request example

POST
/research
1curl -X POST https://api.caesar.xyz/research \
2 -H "Authorization: Bearer <token>" \
3 -H "Content-Type: application/json" \
4 -d '{
5 "query": "What are the latest advancements in renewable energy technologies?"
6}'
Try it
1{
2 "query": "Latest developments in quantum computing for drug discovery",
3 "system_prompt": "Format the response as a bullet-point executive summary with key findings and implications"
4}

Response structure

When using system_prompt, the response includes both original and transformed content:

1{
2 "id": "abc123...",
3 "status": "completed",
4 "query": "Latest developments in quantum computing for drug discovery",
5 "content": "Full research content with detailed analysis...",
6 "transformed_content": "" Key Finding 1: IBM's quantum advantage in molecular simulation...\n" Key Finding 2: ...",
7 "results": [...]
8}

Common transformation patterns

Executive summary
Structured analysis
Technical brief
Investment perspective
1{
2 "system_prompt": "Provide a 3-paragraph executive summary highlighting key insights, implications, and recommendations"
3}

Key principles

No prompt engineering required

Caesar understands context and intent without complex prompts. Focus on being clear rather than clever.

Clarity beats complexity

Simple, explicit queries outperform elaborate prompt chains. State exactly what you need.

Domain agnostic

Caesar works across all domainsfinance, technology, science, cryptowithout specialized prompts.

Transform, don't guide

System prompts transform output presentation, not research quality or scope.

Tips for optimal results

  1. Include relevant context: Mention time periods, geographic regions, or specific sectors when relevant
  2. Use industry-standard terminology: Caesar understands domain-specific terms and acronyms
  3. Specify comparison criteria: When comparing options, state what metrics or factors matter
  4. Set clear boundaries: If you want specific scope (e.g., “only peer-reviewed sources”), state it explicitly

Remember: Caesar performs comprehensive research regardless of how you phrase your query. Being explicit simply ensures the research focuses on exactly what you need.