OpenAI
Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology
Scorecard detail
OpenAI is the canonical API-first AI vendor. The Python and Node SDKs are auto-generated from a public OpenAPI spec at github.com/openai/openai-openapi, and the chat completions, embeddings, assistants, batch, files, fine-tuning, and Realtime endpoints form one of the densest single API surfaces in production. Bearer-token auth, structured outputs with JSON schema, and tool-calling are first-class primitives. The dashboard exists for billing and key management, not as the contract.
signals (6)
- +AI review appliedReviewer: Editorial review on 2026-05-20
- +OpenAPI specPublished, 0 operations
- ·GraphQL endpointDiscovered at https://openai.com/graphql, introspection disabled or scoped
- +SDKs maintained3 (javascript, ruby, typescript); top by stars: openai/openai-realtime-api-beta (1014 stars)
- +SDK recency1 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
- −npm weekly downloadsNo published npm package detected for the JS/TS SDKs
cite (1)
- github.sdks@2026-05-19
Practically every workflow OpenAI exposes is reachable from code. Fine-tuning jobs, file uploads, batch runs, assistants, threads, vector stores, response streaming, evals, and project-level usage are all API-controllable. Account-level billing and team membership still require the dashboard, but the agent-relevant surface is comprehensive. The Realtime and Responses APIs extend the headless story into streaming and tool-orchestrated workflows that older completion APIs could not express.
signals (9)
- +AI review appliedReviewer: Editorial review on 2026-05-20
- −API operations exposedOpenAPI present but operations could not be counted
- ·Docs pages crawled0 pages (crawler: none)
- ·Auth schemes documentedAuth documentation page not reached by crawler
- ·Setup / quickstart docsNot reached by crawler
- ·Billing docsNot reached by crawler
- ·Teams / org docsNot reached by crawler
- ·CLI docsNot reached by crawler
- ·Schema / data model docsNot reached by crawler
cite (1)
- github.sdks@2026-05-19
OpenAI does not publish an official MCP server, but the Responses API, function calling, and structured outputs are the targets MCP clients connect to most often. Tool-use is a first-class primitive in the API itself rather than a layered protocol, so the practical agent integration story is excellent even without OpenAI authoring an MCP server. Editorial note: this is the unusual case where absence of MCP is not a gap.
signals (4)
- +AI review appliedReviewer: Editorial review on 2026-05-20
- −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
- −Community MCP serversNone found
- +Agent-friendly SDKs2 TS/JS SDKs available; top: openai/dallify-discord-bot
cite (1)
- github.sdks@2026-05-19
The OpenAPI specification at github.com/openai/openai-openapi is the source of truth for every official SDK and is regenerated on each API change. Any agent with internet access can fetch the schema and build a client cold. JAIRF historically scored OpenAI at Level 3 (AI-Ready) on this artifact; the scoring engine was unavailable in the current build environment, but the artifact itself remains the category benchmark for schema discoverability.
signals (3)
- +AI review appliedReviewer: Editorial review on 2026-05-20
- +OpenAPIPublished at https://raw.githubusercontent.com/openai/openai-openapi/master/openapi.yaml (OpenAPI undefined, 0 operations)
- ·GraphQL introspectionGraphQL endpoint at https://openai.com/graphql but introspection is disabled, scoped, or behind authentication
cite (1)
- github.sdks@2026-05-19
OpenAI added webhook support for batch completions in 2025, joining the Realtime API server-sent events and the fine-tuning job status callbacks. HMAC signing is documented, payload structure mirrors the API object model, and replay through the events API is straightforward. The catalog is narrower than payments or commerce platforms because LLM workloads are mostly synchronous, but for the async surfaces that do exist the implementation is operationally sound.
signals (2)
- +AI review appliedReviewer: Editorial review on 2026-05-20
- ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
- github.sdks@2026-05-19
FCFoundational Compliance70/100
Structural validity, standards conformance, and parsability of the OpenAPI specification.
DXJDeveloper Experience & Tooling Compatibility61.8/100
Documentation clarity, example coverage, response completeness, and ingestion health.
ARAXAI-Readiness & Agent Experience43.8/100
Semantic clarity, intent expression, datatype specificity, and error standardization.
AUAgent Usability100/100
Operational composability, complexity comfort, navigation affordances, and safety patterns.
SECSecurity80/100
Authentication strength, transport security, secret hygiene, and OWASP risk posture.
AIDAI Discoverability97.8/100
Descriptive richness, intent phrasing, workflow context, and registry signals.
Band rationale:B band: JAIRF=73.8 HeadlessIndex=86
Show OpenAI's score on your site.
Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.
How THI compares to external scorers
| Source | Score | Measures | Last checked |
|---|---|---|---|
| Fern Agent Score | not found | Documentation completeness and SDK shape (~22 checks) | — |
| CLIRank Agent Friendliness | 94 · Excellent | CLI readiness, docs quality, and overall agent affordances | — |
| Cloudflare Is It Agent Ready? | blocked | Cloudflare's manual agent-readiness heuristic per vendor URL | — |
| Jentic Scorecard | n a | JAIRF-based scorecard requiring a public OpenAPI specification | — |
THI display 86 vs external median 94 (delta -8). Within calibration band.