# JPMorgan Chase — API Agent Score

> Score: 66/100 (Grade: C) | Domain: jpmorganchase.com | Rubric: 1.0.0 | Checked: October 28, 2026

JPMorgan Chase scored 66/100 (C), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 87/100 (A)
- Developer Experience: 40/100 (F)
- Agent Discovery: 81/100 (A)
- Agent Understanding: 87/100 (A)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → ./dist/index.d.ts. Investigated: sdk 100%.
- [warn] Security & governance hygiene — Moderate footprint: 14 direct dependencies. Heavy frameworks: lodash-es. Investigated: sdk 83%, wellknown 0%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.
- [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

- [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] Description completeness — 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] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (jpmorganchase/fusion, 296 snippets). Investigated: docs 100%, sdk 25%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 0/1 sitemap doc pages (0%); 1 missing — Missing: https://developer.payments.jpmorgan.com/docs/home. Investigated: docs 35%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap has 739 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 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%.
- [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] 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

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 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

JPMorganChase's API program demonstrates strong fundamentals in API design, agent understanding, and discoverability — partners and agents can find and parse the surface reliably. However, two critical gaps are blocking partner program growth: there is no self-service onboarding path, meaning prospective partners hit a wall before writing a single line of code, and there is no idempotency or retry guidance, leaving partners exposed to reliability failures in production financial workflows. Closing these two gaps should be the immediate priority to convert API interest into active, confident integrations.