Delldell.com
Dell's API program shows strength in discovery and crawlability, where partners and agents can already find the front door. The most urgent gaps are in agent understanding and usability: there are no machine-readable instructions or structured data for AI agents to parse, no runnable collections with test scripts for agents to build against, and no worked examples in the API contract or docs to accelerate partner onboarding.
API DesignA clean, typed, well-governed API contract agents can reason about0 pass1 warn1 fail50D
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| warn | Security & governance hygienevia wellknown | 7.5/15 | security.txt present but missing or expired Expires. Investigated: wellknown 50%. | No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel. |
| fail | Example coveragevia docs | 0/10 | No detectable code samples across 1 sampled docs pages. Investigated: docs 0%. | Examples carry shape semantics schemas under-specify — for humans and agents alike. |
| na | Machine-readable, versioned contract | —/25 | No surface produced evidence for this capability in this run. | A current OpenAPI version with a declared versioning scheme lets agents reason about the contract. |
| na | Schema coverage & depth | —/25 | No surface produced evidence for this capability in this run. | Typed, complete request/response schemas are what make agent function-calling possible. |
| na | Auth declared & discoverable | —/25 | No surface produced evidence for this capability in this run. | 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 examples2 pass1 warn1 fail71B
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Self-service developer portalvia docs | 29/29 | Signup page at https://www.dell.com/en-us; no free-tier language detected in docs/pricing. Investigated: docs 100%. | Self-serve key/account creation is the fast first call for partners, with no sales gate. |
| pass | Changelog publishedvia sdk | 13/13 | Newest official SDK activity 2 day(s) ago. Investigated: sdk 100%. | A published changelog lets partners track changes without surprise. |
| warn | Quickstart presentvia docs | 12.5/25 | Quickstart page reachable (10 variants scanned starting at https://www.dell.com/di/idp/dwa/authorize?response_type=id_token&client_id=657d850a-459b-4b56-ab6d-361e7181b981&redirect_uri=https%3a%2f%2fwww.dell.com%2fdci%2ffp%2fdi%2fv3%2ffp%2foidc%2fauthorize%3fresponse_type%3dcode%26client_id%3dc168319c-62a3-4131-95ec-6b80cfe82578%26scope%3dopenid%2bprofile%2bdellprofile%2baddress%26state%3dyjKg6eGaJEHwKbjU2FiwktSiQM8gQo92P6hN8xPG_w8%253d%26redirect_uri%3dhttps%253a%252f%252fdeveloper.dell.com%252flogin%252foauth2%252fcode%252fdias-creds%26nonce%3dtZ_gBAB-z_u2sWjHb1GhNjFTo_JM9uhDEEx7tp1scEU%26code_challenge%3d7onfHF4pQjEv820gSkTTYEarOhrQ500kgHK-rC7Ebb8%26code_challenge_method%3dS256%26ContextId%3dd3c139970c074a0aba20bb3c50e77fc2&tag=cid=c168319c-62a3-4131-95ec-6b80cfe82578&state=fp&scope=openid&nonce=d3c13997-0c07-4a0a-ba20-bb3c50e77fc2&contextid=d3c13997-0c07-4a0a-ba20-bb3c50e77fc2) 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. |
| fail | Code samples in docsvia docs | 0/18 | No detectable code samples across 1 sampled docs pages. Investigated: docs 0%. | Multi-language samples shorten time-to-first-call. |
| na | Description completeness | —/15 | No surface produced evidence for this capability in this run. | Complete descriptions are the context humans and agents need to use endpoints. |
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass2 warn0 fail80A
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | llms.txt present, valid & comprehensivevia docs | 30/30 | llms-full.txt reachable at https://developer.dell.com/llms-full.txt. Investigated: docs 100%. | A valid, comprehensive llms.txt is the machine-readable entry point for agents. |
| warn | Registry & SDK presencevia sdk | 14/28 | Discovered SDKs in only 2 language(s); target ≥3. Investigated: sdk 50%, docs 0%, cli 0%, mcp 0%, wellknown 0%. | Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look. |
| warn | Crawlable / AEOvia wellknown | 9/12 | Sitemap present (0 entries) but carries no lastmod values. Investigated: wellknown 75%. | Bots allowed plus a fresh sitemap make docs findable by agent crawlers. |
| na | Docs reachable, not hard auth-gated | —/30 | No surface produced evidence for this capability in this run. | Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics. |
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs0 pass0 warn2 fail40F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| fail | Agent instructions file (AGENTS.md)via wellknown | 0/10 | No 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. |
| fail | Docs structured datavia docs | 0/8 | Neither JSON-LD nor OpenGraph/meta tags detected across 1 sampled pages — likely a CSR-only docs site. 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. |
| na | Machine-readable errors (RFC 9457) | —/28 | No surface produced evidence for this capability in this run. | RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens. |
| na | Operation purpose clarity | —/25 | No surface produced evidence for this capability in this run. | Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice. |
| na | Agent-navigable, token-efficient docs | —/22 | No surface produced evidence for this capability in this run. | Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly. |
| na | Description consistency across surfaces | —/7 | Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare. | Every surface tells the same story about what the product is. |
Agent UsabilityAgents have the context to use your APIs reliably, not just find them0 pass0 warn1 fail40F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| fail | Runnable collection with test scriptsvia platform | 0/9 | No public Postman workspace discovered for the org. Investigated: platform 0%. | A public, maintained collection with assertions is runnable truth agents validate against. |
| na | Idempotency documented | —/27 | No surface produced evidence for this capability in this run. | Documented idempotency lets agents retry safely. |
| na | Rate-limit signaling | —/22 | No surface produced evidence for this capability in this run. | Machine-readable rate-limit headers let agents throttle adaptively. |
| na | Pagination documented & consistent | —/22 | No surface produced evidence for this capability in this run. | Consistent, documented pagination lets agents traverse collections. |
| na | Sandbox separation | —/20 | No surface produced evidence for this capability in this run. | An isolated environment lets agents exercise destructive operations safely. |