Bnybny.com
BNY's API program demonstrates a strong API design foundation with a machine-readable contract already in place, but two critical gaps are limiting partner and agent adoption. Agent discovery is essentially absent — partners and their AI agents cannot find, index, or act on BNY's APIs without a sales conversation.
API DesignA clean, typed, well-governed API contract agents can reason about3 pass1 warn1 fail86A
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Schema coverage & depthvia spec | 25/25 | 100% of operations have documented request and response schemas. Investigated: spec 100%. | Typed, complete request/response schemas are what make agent function-calling possible. |
| pass | Auth declared & discoverablevia spec | 25/25 | Authentication required (global or on every operation). Investigated: spec 100%, docs 100%. | Agents can only authenticate when auth is declared, scoped, and discoverable. |
| warn | Machine-readable, versioned contractvia spec | 18.8/25 | info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%. | A current OpenAPI version with a declared versioning scheme lets agents reason about the contract. |
| pass | Security & governance hygienevia spec | 15/15 | No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%. | No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel. |
| fail | Example coveragevia spec | 0/10 | 0% example coverage. Investigated: spec 0%, docs 0%. | Examples carry shape semantics schemas under-specify — for humans and agents alike. |
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples2 pass1 warn2 fail55D
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Description completenessvia spec | 15/15 | 100% of operations + parameters have substantive descriptions. Investigated: spec 100%. | Complete descriptions are the context humans and agents need to use endpoints. |
| pass | Changelog publishedvia spec | 13/13 | changelog documented in the docs site at https://nexen.bny.com/login/forms/login.fcc?SMQUERYDATA=-SM-kOfTfk1BQG9elua6JHr72eCpncbcEnBOhkiTxDZTfIXREUGWtYJ5GfweDZUxkanC1%2fUBKN6VlACI2Iw3Q1BYJjOCpoaLShja0UEqQcmtWYERwj8EohnXm59GUGOWxYIhLcyV3eqQG9YrCFxdWU1EkLUQ178NUbDRQpKE1XOK5xALpcHmb1ktkmXonFf2C%2b%2fstt7%2bIBBcpKnAG5rzlPuDTM9ZWlQZBMgB0c5x%2bhQMZc2YLiJhRiLM%2bjEY%2b77CLC1GQpUM7g0pvcsnG6h34VAclJyjmcoMwyH%2fps7%2fDO4GKSa66NYW2ZSAfvng6cI2KcZ0DBLfnWvhEDkkNzVKzbZXTx%2b2YbGfTfcAr5%2fT193hDNZGuuoAzknAh4MyrsaTeUPTuapLdYw4wPm9agKJelh6B1rQOTbf4WpkGFRH696OiAMc6fYcYXRFp%2fuUediqE%2fs7. Investigated: spec 100%, docs 100%. | A published changelog lets partners track changes without surprise. |
| warn | Quickstart presentvia docs | 12.5/25 | Quickstart page reachable (23 variants scanned starting at https://developer.bny.com/app/open/home/quickstart) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%. | A quickstart is the fastest path from landing page to first successful call. |
| fail | Self-service developer portalvia docs | 0/29 | No self-service signup detected: no signup link found 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. Investigated: docs 0%. | Self-serve key/account creation is the fast first call for partners, with no sales gate. |
| fail | Code samples in docsvia docs | 0/18 | No detectable code samples across 1 sampled docs pages. Investigated: docs 0%. | Multi-language samples shorten time-to-first-call. |
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs0 pass2 warn2 fail46F
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| warn | Docs reachable, not hard auth-gatedvia docs | 15/30 | 1 of 1 pages return 200 for non-existent URLs (soft 404). Investigated: docs 50%. | Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics. |
| warn | Crawlable / AEOvia wellknown | 6/12 | No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%. | Bots allowed plus a fresh sitemap make docs findable by agent crawlers. |
| fail | llms.txt present, valid & comprehensivevia docs | 0/30 | No llms.txt found at any candidate location (https://developer.bny.com/app/open/home/llms.txt, https://developer.bny.com/llms.txt, https://developer.bny.com/docs/llms.txt); candidates redirected cross-host to https://nexen.bny.com (agents can't follow cross-host redirects). Investigated: docs 0%. | A valid, comprehensive llms.txt is the machine-readable entry point for agents. |
| fail | Registry & SDK presencevia docs | 0/28 | Not indexed on Context7 — agents can't pull this API's docs on demand via Context7. Investigated: docs 0%, sdk 0%, cli 0%. | Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look. |
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs2 pass1 warn2 fail78B
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Machine-readable errors (RFC 9457)via spec | 28/28 | Only 2 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: spec 100%, docs 100%. | RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens. |
| pass | Operation purpose clarityvia spec | 25/25 | 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%. | Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice. |
| warn | Agent-navigable, token-efficient docsvia docs | 15.7/22 | No pages support .md URLs (0/1 tested). Investigated: docs 71%. | Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly. |
| fail | Agent instructions file (AGENTS.md)via wellknown | 0/10 | No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%. | An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index. |
| fail | Docs structured datavia docs | 0/8 | Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). Investigated: docs 0%. | Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed. |
| na | Description consistency across surfaces | —/7 | Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare. | Every surface tells the same story about what the product is. |
Agent UsabilityAgents have the context to use your APIs reliably, not just find them1 pass0 warn1 fail76B
| Signal | Points | Findings | Rationale | |
|---|---|---|---|---|
| pass | Rate-limit signalingvia spec | 22/22 | rate-limit behavior documented in the docs site at https://nexen.bny.com/login/forms/login.fcc?SMQUERYDATA=-SM-eB%2fGlbVhzQg7ifGyY4n3DFLD36vWbB%2fq7M4ogZchrJ1cODu17Q14%2bVuw9I0FjC079f5clqh31YNGv6j%2fuRZhloE05cubBko2C1kn8x0rCGSzJc%2fDA6jR2uXMVmCkf5oJi4nEroXoXh9356k1uSXROsyTePKcJOBMbkmzIJWBBmzcfEtYKvVuVK5KAbFKV67zC5UsnFOJGD1zdcywF9azvys4BCzGG3YwspitVWYnlC15OUi9MuZ2m3%2fwp0RaCzJbsaZgYaNtPNEwrBYtn0%2fM3naATYF37UH0nZywE79sZCsqCSAFoNeLSlQkiQuWZf3l6k%2fazl4IJEwRqlzSQJSZ0MKiTiA51gGUpgFSQihT2hLjbAqGCMbVpxC4Q4dXiYZxMa3WKjq8YJtgTLV9vqUJUffJhBsXoIkRC5gcB%2bWeoIichcVnAVcRO1kGbGbZKKO7. Investigated: spec 100%, docs 100%. | Machine-readable rate-limit headers let agents throttle adaptively. |
| fail | Runnable collection with test scriptsvia platform | 0/9 | No public Postman workspace discovered for the org. Investigated: platform 0%. | A public, maintained collection with assertions is runnable truth agents validate against. |
| na | Idempotency documented | —/27 | No surface produced evidence for this capability in this run. | Documented idempotency lets agents retry safely. |
| na | Pagination documented & consistent | —/22 | No surface produced evidence for this capability in this run. | Consistent, documented pagination lets agents traverse collections. |
| na | Sandbox separation | —/20 | No surface produced evidence for this capability in this run. | An isolated environment lets agents exercise destructive operations safely. |
Resources Discovered
The public resources we found for Bny — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.
| APIs analyzed | 4 — BNY Asset Servicing API, BNY Asset Servicing Markets API, BNY Asset Servicing Pershing API, BNY Asset Servicing Treasury Services API |
|---|