# MTB — API Agent Score

> Score: 60/100 (Grade: C) | Domain: mtb.com | Rubric: 1.0.0 | Checked: October 29, 2026

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

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

## Summary

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

## Category Scores

- API Design: 63/100 (C)
- Developer Experience: 48/100 (F)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 58/100 (D)
- Agent Usability: 57/100 (D)

## Check Results

### API Design

- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [warn] Schema coverage & depth — 0/8 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 25%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, docs 0%.
- [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

- [warn] Quickstart present — Quickstart page is reachable at https://developer.mtb.com/quickstart (12 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%.
- [warn] Description completeness — 3/10 operations lack a description. Investigated: sdk 70%.
- [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 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [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 (infineon/mtb-xmclib-cat3, 8052 snippets). Investigated: docs 100%, sdk 25%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Crawlable / AEO — Sitemap has 0 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developer.mtb.com/llms.txt, https://developer.mtb.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Operation purpose clarity — Read/write classification is mostly ambiguous: only 2/10 operations classified. Investigated: sdk 60%.
- [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%.
- [fail] Machine-readable errors (RFC 9457) — No single common SDK base error class was found; errors do not share one root. Investigated: sdk 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [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

Mtb's API program shows reasonable discoverability fundamentals but has critical gaps in two areas that directly block partner and agent adoption: developer onboarding and agent-readiness of documentation. Partners currently cannot self-serve — there is no signup path, no in-docs code samples, and no machine-readable signals for AI agents to find or act on the APIs. Prioritizing a self-service portal with embedded code examples, structured discovery artifacts, and standardized error handling will unlock the partner-program growth that the current experience is preventing.