Oracleoracle.com

ScoredJul 24, 2026, 09:44 AM

Oracle's API program shows solid fundamentals in API design and developer experience, but two areas risk stalling partner adoption: agent discovery and agent understanding. Partners and their AI agents cannot reliably find or parse Oracle's API documentation without machine-readable discovery artifacts and structured context files — meaning integrations start with a sales conversation instead of self-serve.

API DesignA clean, typed, well-governed API contract agents can reason about3 pass1 warn1 fail74B
SignalPointsFindingsRationale
passSchema coverage & depthvia sdk25/25package.json "types" → types/index.d.ts. Investigated: sdk 100%, spec 57%.Typed, complete request/response schemas are what make agent function-calling possible.
warnMachine-readable, versioned contractvia spec18.8/25info.version="1.0.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
passSecurity & governance hygienevia spec15/15No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
passExample coveragevia spec10/10100% example coverage across params + responses. Investigated: spec 100%, sdk 100%, docs 0%.Examples carry shape semantics schemas under-specify — for humans and agents alike.
failAuth declared & discoverablevia spec0/25No securitySchemes declared. Investigated: spec 0%, docs 0%.Agents can only authenticate when auth is declared, scoped, and discoverable.
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples3 pass1 warn1 fail75B
SignalPointsFindingsRationale
passSelf-service developer portalvia docs29/29Self-service signup at https://www.oracle.com/cloud/free/; no free tier or sandbox language detected. Investigated: docs 100%.Self-serve key/account creation is the fast first call for partners, with no sales gate.
passDescription completenessvia spec15/1587% description completeness (target 90%+). Investigated: spec 100%.Complete descriptions are the context humans and agents need to use endpoints.
passChangelog publishedvia sdk13/13Newest official SDK activity 2 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.A published changelog lets partners track changes without surprise.
warnQuickstart presentvia docs12.5/25Quickstart page reachable (1 variants scanned starting at https://docs.oracle.com/get-started/) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.A quickstart is the fastest path from landing page to first successful call.
failCode samples in docsvia docs0/18No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.Multi-language samples shorten time-to-first-call.
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass2 warn1 fail61C
SignalPointsFindingsRationale
passRegistry & SDK presencevia docs28/28Indexed on Context7 (steipete/oracle, 765 snippets). Investigated: docs 100%, sdk 67%, cli 0%, mcp 0%, wellknown 0%.Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
warnDocs reachable, not hard auth-gatedvia docs15/301 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
warnCrawlable / AEOvia wellknown6/12No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
failllms.txt present, valid & comprehensivevia docs0/30No llms.txt found at any candidate location (https://docs.oracle.com/llms.txt, https://docs.oracle.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.A valid, comprehensive llms.txt is the machine-readable entry point for agents.
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs1 pass3 warn2 fail73B
SignalPointsFindingsRationale
passMachine-readable errors (RFC 9457)via docs28/287 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
warnOperation purpose clarityvia spec23.8/2588% of operations are agent-inferable (target 90%+). Investigated: spec 95%.Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
warnAgent-navigable, token-efficient docsvia docs14.1/22No pages support .md URLs (0/1 tested). Investigated: docs 64%.Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
warnDescription consistency across surfaces0.8/7Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 4% (threshold 35% for full credit).Every surface tells the same story about what the product is.
failAgent instructions file (AGENTS.md)via wellknown0/10No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
failDocs structured datavia docs0/8Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%.Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
Agent UsabilityAgents have the context to use your APIs reliably, not just find them1 pass3 warn1 fail58D
SignalPointsFindingsRationale
passPagination documented & consistentvia spec22/22page_size pagination detected (good for agents). Investigated: spec 100%, docs 100%.Consistent, documented pagination lets agents traverse collections.
warnSandbox separationvia sdk10/20No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.An isolated environment lets agents exercise destructive operations safely.
warnRate-limit signalingvia spec7.7/22No rate-limit response headers documented. Investigated: spec 35%, docs 35%.Machine-readable rate-limit headers let agents throttle adaptively.
warnRunnable collection with test scriptsvia platform4.5/9No test scripts found in the workspace's collections. Investigated: platform 50%.A public, maintained collection with assertions is runnable truth agents validate against.
failIdempotency documentedvia spec0/270% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.Documented idempotency lets agents retry safely.
Resources Discovered

The public resources we found for Oracle — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hintsContext7 (765)
APIs analyzed10Identity and Access Management Service API, Data Science API, Media Services API, Object Storage Service API, Language API, Resource Manager API, API Gateway API, Generative AI Agents Management API, WebLogic Management Service API (pre-GA), Anomaly Detection API
Want to improve your results?