# Visa — API Agent Score

> Score: 60/100 (Grade: C) | Domain: visa.com | Rubric: 1.0.0 | Checked: July 24, 2026

Visa scored 60/100 (C), classified "partially-ready".

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

## Summary

- Overall: 60/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 56/100 (D)
- Developer Experience: 52/100 (D)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 87/100 (A)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="0.0.1") and header-versioning detected. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — 86% of operations have documented schemas (target 95%+). Investigated: spec 67%, sdk 0%.
- [fail] Auth declared & discoverable — No securitySchemes declared. Investigated: spec 0%, docs 0%.
- [fail] Security & governance hygiene — 4 credential-shaped strings detected in spec: bearer-jwt (×4). Investigated: spec 0%, wellknown 0%.
- [fail] Example coverage — 34% example coverage. Investigated: spec 0%, sdk 0%.

### Developer Experience

- [pass] Description completeness — 88% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 42 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/moyasar, 2652 snippets). Investigated: docs 100%, sdk 88%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.visa.com/llms.txt, https://developer.visa.com/docs/llms.txt). Investigated: docs 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 13 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 98% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 86%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Docs structured data — 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

- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 5% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Pagination documented & consistent — 1 list endpoint(s) exist but no pagination params found. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Visa's API program shows strength in agent understanding and documentation parseability, but faces critical gaps in operational reliability, runnable integration assets, and API design fundamentals — all of which directly block partners and their AI agents from building with confidence. The most urgent priorities are closing the agentUsability failures (missing idempotency, rate-limit signaling, and pagination guidance) and establishing a self-service developer portal with a clear quickstart, as these two gaps have the highest combined impact on partner activation and agent-driven integrations. Alongside these, auth declaration, example coverage, and agent-discoverable documentation must be addressed to make the program truly partner-ready at scale.