$HEADLESS SYSTEMS
03 / Scorecard / Payments

Yapily

C
Headless Index
44/100
denominator 80
JAIRF
95.4/100
Agent-Optimized
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Yapily is partially headless and partly UI-led. The Headless Index thesis-fit score of 44/100 puts it mid-table on the index, and JAIRF v1.0.0 puts it at 95.4/100 (Level 4, Agent-Optimized). In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where Yapily lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Yapily is European open-banking infrastructure. REST API exposes account-data, payment-initiation, and KYB-style identity flows across 100+ EU banks. SDKs in Node, Python, Java, Ruby, PHP.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at docs.yapily.com. OpenAPI references exist.[2] An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Authorizations, payments, account data, and institution discovery are programmable. The Yapily Console handles compliance review.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Yapily MCP server.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: integrators can build agent flows against Yapily, but the rough edge to plan around is MCP posture[5]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent5/20
scored

Yapily is European open-banking infrastructure. REST API exposes account-data, payment-initiation, and KYB-style identity flows across 100+ EU banks. SDKs in Node, Python, Java, Ruby, PHP.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPI specPublished, 97 operations
  • ·GraphQL endpointDiscovered at https://www.yapily.com/graphql, introspection disabled or scoped
  • −SDKs maintainedNone detected in vendor org
cite (3)
  • openapi.url@2026-05-21
  • graphql.url@2026-05-21
  • github.sdks@2026-05-21
Headless operation15/20
scored

Authorizations, payments, account data, and institution discovery are programmable. The Yapily Console handles compliance review.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +API operations exposed97 operations in OpenAPI spec
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.pages_crawled@2026-05-21
  • docs.topics_found.setup@2026-05-21
  • docs.topics_found.billing@2026-05-21
  • docs.topics_found.teams@2026-05-21
  • docs.topics_found.cli@2026-05-21
  • docs.topics_found.schema@2026-05-21
MCP & agent posture0/20
scored

No first-party Yapily MCP server.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • −Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)
cite (3)
  • mcp.registry_query@2026-05-21
  • mcp.github_search_query@2026-05-21
  • github.sdks@2026-05-21
Schema observability15/20
scored

REST documented at docs.yapily.com. OpenAPI references exist.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • +OpenAPIPublished at https://docs.yapily.com/openapi.json (OpenAPI 3.0.1, 97 operations)
  • ·GraphQL introspectionGraphQL endpoint at https://www.yapily.com/graphql but introspection is disabled, scoped, or behind authentication
cite (2)
  • openapi.url@2026-05-21
  • graphql.url@2026-05-21
Webhooks & eventsUnknown
Unknown

Authorization and payment webhooks. Catalog matches open-banking.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-21
JAIRF · 6 dimensions
FCFoundational Compliance
100/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility
97.6/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience
78.9/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability
100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity
100/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability
99.8/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:C band: scores 40-75 range

04 / Embed

Show Yapily's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Yapily mini badge preview
Get embed code
Calibration

How THI compares to external scorers

SourceScoreMeasuresLast checked
Fern Agent Scorenot foundDocumentation completeness and SDK shape (~22 checks)—
CLIRank Agent Friendlinessnot foundCLI readiness, docs quality, and overall agent affordances—
Cloudflare Is It Agent Ready?blockedCloudflare's manual agent-readiness heuristic per vendor URL—
Jentic Scorecard—JAIRF-based scorecard requiring a public OpenAPI specification—
THI 44 vs external median 0

No external scores available to calibrate against.

Peers in Payments
IncreaseC
Headless Index 44/100
OrbC
Headless Index 43/100
Authorize.NetC
Headless Index 48/100
See full Payments ranking →