# Isbank — API Agent Score

> Score: 56/100 (Grade: D) | Domain: isbank.com.tr | Rubric: 1.0.0 | Checked: November 10, 2026

Isbank scored 56/100 (D), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/isbank)
[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: 79/100 (B)
- Developer Experience: 43/100 (F)
- Agent Discovery: 54/100 (D)
- Agent Understanding: 62/100 (C)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.
- [warn] Machine-readable, versioned contract — The API sets a version ("4.1.3") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 75%, docs 50%.
- [warn] Schema coverage & depth — Only 86% of the 77 operations document both request and response schemas (target 95%+), so an agent can't reliably call the rest. Investigated: spec 67%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [fail] Example coverage — Only 0% of parameters and responses (0 of 1179) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 0%, docs 0%.

### Developer Experience

- [warn] Quickstart present — Quickstart page is reachable at https://developer.sandbox.isbank.com.tr/tr/all-apis/quickstart (24 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [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] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Description completeness — Only 45% of operations and parameters have descriptions (0 of 77 ops, 385 of 431 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### Agent Discovery

- [warn] Docs reachable, not hard auth-gated — 50 of 50 sampled pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.sandbox.isbank.com.tr/tr/all-apis/llms.txt, https://developer.sandbox.isbank.com.tr/llms.txt, https://developer.sandbox.isbank.com.tr/docs/llms.txt). Investigated: docs 33%.
- [fail] Registry & SDK presence — Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 8 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.
- [warn] Agent-navigable, token-efficient docs — No sampled pages support .md URLs (0/50 tested). Investigated: docs 71%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 3 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [fail] Operation purpose clarity — Only 0% of operations (0 of 77) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 0%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [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 is documented on the docs site at https://developer.sandbox.isbank.com.tr/tr/all-apis/sandbox, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 45) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Isbank's API program has a solid machine-readable contract as its foundation, but two critical gaps are blocking partner and agent adoption at scale. The developer experience is severely undermined by missing descriptions, no changelog, and no self-service onboarding path — partners cannot evaluate or integrate without direct engagement. At the same time, agents cannot ground themselves in real payload shapes (zero examples across 1,179 parameters and responses), cannot discover the API autonomously, and cannot safely retry mutations without idempotency or rate-limit guidance. Prioritizing example coverage and documentation quality will unlock both human and AI-driven integration paths, while adding a discoverable front door and runnable collections will compress time to a partner's first successful call.