# Fiserv — API Agent Score

> Score: 75/100 (Grade: B) | Domain: fiserv.com | Rubric: 1.0.0 | Checked: July 24, 2026

Fiserv scored 75/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 55/100 (D)
- Agent Discovery: 79/100 (B)
- Agent Understanding: 76/100 (B)
- Agent Usability: 71/100 (B)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — Versioning declared (info.version="26.2.5") and url-versioning detected. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Only 60% of operations have documented schemas. Investigated: spec 61%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [pass] Example coverage — 6% example coverage. Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Description completeness — 85% description completeness (target 90%+). Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 111 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [warn] Quickstart present — Quickstart page reachable (10 variants scanned starting at https://developer.fiserv.com/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [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] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Discovered SDKs in 3 distinct languages. Investigated: sdk 100%, docs 0%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 39 pages. Investigated: docs 67%.
- [warn] Docs reachable, not hard auth-gated — 39 of 39 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 9 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% 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/39 tested). Investigated: docs 75%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 5% (threshold 35% for full credit).
- [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 1 assessed pages (1 JS-rendered). Investigated: docs 0%.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://developer.fiserv.com/limits. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — Pagination params detected on 1 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Sandbox server declared but no distinguishable test credentials in scheme descriptions. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Fiserv's API Design is a clear strength — the contract itself is well-structured and machine-readable. However, two areas are holding back partner outcomes: Agent Understanding (docs lack the machine-readable signals and structured context that AI agents need to parse and act on your APIs without guessing) and Developer Experience (no self-service portal or inline code samples means partners spend weeks getting to their first working integration instead of minutes). Prioritizing a self-service documentation portal with agent-ready signals, followed by runnable collections and idempotency guidance, will unlock faster partner onboarding and reliable agent-driven workflows.