# Palo Alto Networks — API Agent Score

> Score: 56/100 (Grade: D) | Domain: paloaltonetworks.com | Rubric: 1.0.0 | Checked: July 24, 2026

Palo Alto Networks scored 56/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 56/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 55/100 (D)
- Developer Experience: 76/100 (B)
- Agent Discovery: 75/100 (B)
- Agent Understanding: 56/100 (D)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples present on 5/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Schema coverage & depth — 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 — Self-service signup at https://www.paloaltonetworks.com/get-started; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples present on 5/20 pages across 1 language(s); broader multi-language coverage missing. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/paloaltonetworks, 12 snippets). Investigated: docs 100%, sdk 100%, cli 100%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://pan.dev/llms.txt, https://pan.dev/docs/llms.txt). Investigated: docs 33%.
- [warn] Crawlable / AEO — Sitemap present (11708 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 75%.
- [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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Paloaltonetworks demonstrates solid API discovery foundations, but the partner program faces two critical gaps that will slow or block real integrations: AI agents and coding assistants cannot reliably understand or act on the API surface due to missing structured context and machine-readable instructions, and partners lack a verified, runnable baseline to build against safely. Closing the agent-readiness and runnable-truth gaps should be the immediate priority, followed by tightening security hygiene in the contract itself and removing friction from the first-call experience.