# Databricks — API Agent Score

> Score: 83/100 (Grade: A) | Domain: databricks.com | Rubric: 1.0.0 | Checked: July 24, 2026

Databricks scored 83/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/databricks)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 83/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 84/100 (A)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 68/100 (C)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 2569/2581 (100%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [warn] Security & governance hygiene — security.txt present but missing or expired Expires. Investigated: wellknown 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://www.databricks.com/get-started (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://docs.databricks.com/aws/en/getting-started with a runnable first-call sample. Investigated: docs 100%.
- [warn] Description completeness — 1296/1353 operations carry a description. Investigated: sdk 96%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — llms-full.txt reachable at https://api.databricks.com/llms-full.txt. Investigated: docs 100%, sdk 0%.
- [warn] Registry & SDK presence — 3/4 registry-metadata components present; missing: keywords. Investigated: sdk 92%, cli 50%, docs 0%.
- [warn] Crawlable / AEO — Sitemap present (5627 entries) but carries no lastmod values. Investigated: wellknown 75%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ApiRetriableError" with 584 subclasses. Investigated: sdk 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Databricks' API program excels in discovery, design, and general developer experience — partners can find and evaluate the APIs with minimal friction. The two areas that need immediate attention are agent understanding and agent usability: there is no structured guidance file for AI coding agents, no machine-readable structured data layer on docs, and no runnable collection with test scripts for agents to build confidently against. Closing these gaps will let partners' AI agents integrate correctly without guessing, and will position the program to meet the growing expectation that APIs are natively consumable by automated tooling.