POST
/
alpha
/
consensus
curl -X POST "https://api.sully.ai/alpha/consensus" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "What are the differential diagnoses for a 45-year-old patient presenting with chest pain, shortness of breath, and elevated troponin levels?"
  }'

{
  "data": {
    "id": "consensus_abc123def456",
    "status": "pending",
    "created_at": "2024-01-15T10:30:00Z",
    "updated_at": "2024-01-15T10:30:00Z",
    "metadata": {}
  }
}

​
Overview

The medical consensus endpoint allows you to submit queries to get expert medical opinions and consensus from multiple sources. This is useful for getting second opinions, validating diagnoses, or exploring treatment options.

​
Rate Limiting

This endpoint is rate limited to prevent abuse:
  • Limit: Configurable requests per day (based on your plan)
  • Window: 24 hours
  • Behavior: Requests exceeding the limit will be blocked

​
Request Body

​
query
string
required
The medical query or question you want to get consensus on. This should be a clear, specific medical question or scenario.

​
Response

​
data
object
The created consensus request object
curl -X POST "https://api.sully.ai/alpha/consensus" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "What are the differential diagnoses for a 45-year-old patient presenting with chest pain, shortness of breath, and elevated troponin levels?"
  }'

{
  "data": {
    "id": "consensus_abc123def456",
    "status": "pending",
    "created_at": "2024-01-15T10:30:00Z",
    "updated_at": "2024-01-15T10:30:00Z",
    "metadata": {}
  }
}

​
Status Codes

​
202
Accepted
Consensus request created successfully and is being processed
​
400
Bad Request
Invalid request body or missing required parameters
​
401
Unauthorized
Invalid or missing API key
​
429
Too Many Requests
Rate limit exceeded - wait before making another request
​
500
Internal Server Error
Server error occurred while processing the request

​
Next Steps

After creating a consensus request:
  1. Poll for results: Use the Get Consensus endpoint with the returned ID to check the status and retrieve results
  2. Clean up: Use the Delete Consensus endpoint to remove requests you no longer need