# NetApp — API Agent Score

> Score: 70/100 (Grade: B) | Domain: netapp.com | Rubric: 1.0.0 | Checked: November 3, 2026

NetApp scored 70/100 (B), classified "partially-ready".

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

## Summary

- Overall: 70/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 100/100 (A+)
- Developer Experience: 46/100 (F)
- Agent Discovery: 63/100 (C)
- Agent Understanding: 60/100 (C)
- Agent Usability: 85/100 (A)

## Check Results

### API Design

- [pass] Schema coverage & depth — 337/337 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [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

- [warn] Description completeness — 203/204 operations carry a description. Investigated: sdk 100%.
- [fail] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Quickstart present — No quickstart or getting-started page found at the conventional docs paths, so new developers and agents have no obvious first step. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (netapp/harvest, 5496 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 2144 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms-full.txt was found at any candidate origin, so agents can't grab your full docs in one fetch. Investigated: docs 0%, sdk 0%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (camelCase). Investigated: sdk 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — 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%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, 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

NetApp's API program shows strength in safe integration practices, but two areas are holding back partner adoption: developer onboarding is effectively blocked — there is no self-service signup path and no quickstart to guide partners to a first successful call — and the program is largely invisible to AI agents, with no machine-readable discovery artifacts or structured error contracts for agents to act on. Prioritize unblocking self-service onboarding and agent discoverability first, as these gaps prevent partners and their agents from ever reaching your API surface.