M2P Fintech is Not Agent-Ready to agents.
Discry independently scored how well an AI agent can discover and understand the M2P Fintech API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.
Discovery
45% of score · 45/100Comprehension
55% of score · 6/100What we found
- An agent that reaches M2P's developer portal (developers.m2pfintech.com) is stopped at a sign-in wall: the Stoplight-hosted API reference shows only the operation tree and base URLs, while every endpoint's parameters, examples, and error docs require a workspace account — so the API is effectively unreadable to an unauthenticated agent.
- The one strong discovery signal, m2pfintech.com/llms.txt (32KB, well-structured with descriptions and last-updated metadata), is a marketing/product/blog site map — it never links to the actual API docs (docs.m2pfintech.com or developers.m2pfintech.com), so it points agents at product pages, not endpoints.
- The primary docs host docs.m2pfintech.com (Theneo) returns HTTP 403 to non-browser user agents and its root resolves to 'no project found', so an agent following the obvious 'docs.' subdomain lands on an empty, bot-blocked shell.
- No publicly accessible OpenAPI spec: specs clearly exist inside the Stoplight workspace (Export button, mock server) but are gated; direct spec/export and mock-root probes returned 404/422.
- Positive: the accessible portal home is cleanly structured (product catalog, Getting Started, base URLs, mock server) and the API is organized by product and operation group — the raw material for a good agent experience is present, just locked behind auth and scattered across three doc hosts.
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Make the API reference readable without sign-in. Publish the Stoplight/Theneo endpoint docs (parameters, examples, error tables) to a public URL so agents can comprehend the API before onboarding — this is the single biggest score driver and currently zeroes out comprehension.
- 02Publish a public OpenAPI spec per product at a stable, linkable path (e.g. developers.m2pfintech.com/openapi/upi.json) and reference it from the docs — the specs already exist in Stoplight, they just need to be exposed.
- 03Stop docs.m2pfintech.com returning 403 to non-browser clients and fix the empty root project — the 'docs.' subdomain is the first place an agent looks; it should serve real, crawlable documentation.
- 04Add an API-focused llms.txt on the developer portal that links directly to each product's endpoint docs and OpenAPI spec, instead of relying on the marketing-site llms.txt that only lists product and blog pages.
- 05Consolidate the fragmented doc surface (docs.m2pfintech.com, developers.m2pfintech.com, docs.yappay.in) behind one canonical, unauthenticated developer portal with getting-started guides, worked multi-step workflows, and error-recovery guidance.
Execution coverage · INFORMATIONAL, UNSCORED
Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.
Execution characteristics are not publicly assessable. The Stoplight developer portal exposes each product's base URL (e.g. https://upi-ppi-demo.m2pfintech.com), a Prism mock server, and a section tree (Profile, Transaction, PPI, Notification, Schemas), but all endpoint-level detail — auth scheme, error format, rate limits, pagination, idempotency — sits behind a workspace sign-in. An agent cannot determine how to authenticate or handle errors without credentials.