13 AI-powered endpoints for dental diagnostics — cephalometric landmarks, clinical findings, segmentation analysis, image classification, and treatment length estimation.
Integrate AI-powered diagnostics directly into your practice management software to transform patient outcomes.
Integrate any endpoint within minutes using standard REST calls. Works with any platform and any programming language.
Deep learning models trained on thousands of clinical cases deliver precise landmark detection, classification, and segmentation results.
Enable clinicians to create data-driven treatment plans — assess difficulty levels, estimate treatment duration, and document conditions automatically.
Outsource complex AI algorithm development to our proven API. No need to build and train computer vision models from scratch.
Sync bidirectionally with health record systems. Structured JSON responses integrate seamlessly with digital charting and dental recordkeeping.
Built on peer-reviewed research in quantitative deep learning and dento-craniofacial cognitive diagnosis — a proven methodology for automated clinical assessment.
Unified API gateway — every endpoint follows the same pattern under a single domain.
Authentication Required — All API endpoints require a valid API Key. Include it in the x-api-key header with every request. To obtain your API Key, please contact our team.
Sandbox API Key — Try our API immediately with the sandbox key below. This key is rate-limited to 10 requests/minute and 2,000 requests/month for evaluation purposes.
sandbox-8da678009a7382d71c62f5eaaee567b1
Rate limit headers (X-RateLimit-Remaining-Month) are included in every response so you can track your usage.
All image-processing APIs follow the same request pattern. The TLE endpoint uses GET with query parameters.
Use the sandbox key above to start testing immediately, or contact our team for a production API key.
Select the API matching your imaging modality — lateral ceph, panoramic, clinical photos, etc.
Include your key in the x-api-key header. POST a JSON body with PatientID, TimeStamp, and ImageName (URL to the image).
Get structured JSON with detected landmarks, findings, classifications, or segmentation data — plus an OutputImageUrl to download the annotated image. See Output Images for details.
curl -X POST \
https://api.annie-insights.com/api/annie-clinical-images-v2 \
-H "Content-Type: application/json" \
-H "x-api-key: YOUR_API_KEY" \
-d '{
"PatientID": "P-001",
"TimeStamp": "2026-05-24",
"ImageName": "https://example.com/clinical.jpg"
}'curl -H "x-api-key: YOUR_API_KEY" \
"https://api.annie-insights.com/api/annie-tle-v2?\
p01=1&p02=1&p03=2&p04=2&p05=2&p06=16.3&p07=1&p08=1&p09=0&p10=0&p11=1"Base URL: https://api.annie-insights.com/api/
All image-processing endpoints accept the same base JSON body via POST.
| Parameter | Type | Required | Description |
|---|---|---|---|
| PatientID | string | Required | Unique patient identifier |
| TimeStamp | string | Required | Timestamp for the analysis session |
| ImageName | string | Required | Full URL to the image (e.g. https://...) |
Some endpoints accept additional parameters such as PlotLabels or StandardName. See individual endpoint documentation below for details.
All image-producing endpoints return an OutputImageUrl — a secure, temporary link to the processed image stored in Azure Blob Storage.
How OutputImageUrl Works — When an endpoint processes an image, the annotated output (with landmarks, bounding boxes, or segmentation masks) is uploaded to Azure Blob Storage. The response includes a OutputImageUrl field containing a pre-signed SAS URL for secure, read-only access.
| Property | Detail |
|---|---|
| URL Format | Azure Blob Storage SAS URL with embedded authentication token |
| Access Type | Read-only (sp=r) — no authentication header required to download |
| SAS URL Validity | 72 hours from generation time |
| Image Retention | 3 days — images are automatically deleted by lifecycle policy |
| JSON-only Endpoints | Classifier, TMJ, and TLE do not return OutputImageUrl |
Important: Output images are ephemeral. Download or cache the image within 72 hours of receiving the response. After 3 days, the image is permanently deleted from storage. Do not store the SAS URL as a permanent reference.
Download the output image from OutputImageUrl as soon as you receive the API response and store it in your own system.
If the SAS URL has expired, simply re-submit the same request to the API. A fresh output and new URL will be generated.
Click any endpoint to view request parameters, example payloads, and sample response.
Watch how our AI processes dental images in real time — from identification to analysis.
Watch how the AI automatically identifies and categorizes dental structures from clinical images.
See our deep learning models analyze dental radiographs and photographs for automated diagnostics.
All endpoints return structured error responses with consistent formatting.
{
"message": "No API key found in request"
}Include a valid x-api-key header in your request.
{
"message": "API rate limit exceeded"
}You have exceeded your plan's request limit. Check X-RateLimit-Remaining-Month response headers to monitor usage. Contact our team to upgrade your plan.
{
"detail": {
"PatientID": "P-001",
"TimeStamp": "2026-05-24",
"ImageName": "missing.jpg",
"Error": "The specified image is not available"
}
}Returned when required fields are missing from the request body.
Returned on unexpected model or processing failures. Contact support if this persists.