{
  "id": "p_dTqCugSpYx3zAt_S",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_dTqCugSpYx3zAt_S",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "You are putting together a vendor shortlist, and Workday is on it. You open the APIs.io page for the Workday estate. It rolls up 9 provider profiles and 73 APIs. The estate rates 26.4, in the thin band, and the best member scores 54.1 on the Kin Score. You nearly mark Workday down as a weak API story and move on.\n\nThen you follow a link to the Workday provider itself. It scores 57.1, in the strong band, with an agent score of 34.4 and 16 APIs. That is higher than anything the estate rating counted. The reason is that Workday is the estate's parent, and the parent sits outside the surfaces list. Neither its score nor its APIs go into the rollup.\n\nYou wonder whether this is a one-off. The post's author checked four other estates: Cisco, Broadcom, Oracle and Salesforce. They work the same way, and the effect varies. Salesforce has the wider gap, with a parent at 82.3 and a best member at 73.5. At Cisco, Broadcom and Oracle, the best member beats the parent. The post says that rating the members separately is defensible, because it asks how the rest of the company measures up. But a reader who sees \"Best: 54.1\" can still reach the wrong conclusion, so the parent's score should appear next to the rating. The post says that fix is the catalog's to make.\n\nYou scroll down to the nine members. Workday Finance leads at 54.1, then Workday Integration at 52.1 and Workday Studio at 51.0. Sana is at 44.0, Scout RFP at 41.7, Flowise at 37.1, Peakon at 32.8, Evisort at 24.2 and VNDLY at 2.9.\n\nThe last column is the one that matters to you, because you care about getting a key and making a call. Access clarity is 47.4 for the three Workday-branded surfaces and for the parent. Scout RFP, Peakon, Evisort and VNDLY score 15.8 or below, and their descriptions place them as acquired by Workday. Sana, described as now part of Workday, is the exception at 39.5. Flowise, described as an open-source builder, reaches 31.6. So acquisitions do not inherit access clarity.\n\nDiscoverability tells a different story. Scout RFP reaches 71.4, and Sana, Peakon and Evisort reach 66.1, all above the parent's 62.5. You can find these products easily. The record just says less about how you would get a key.\n\nScout RFP shows the split on its own. It has the estate's best agent score at 31.8, yet only 4.5 on contract governance, against 27.3 for the Workday-branded surfaces. Three members reach the agent-ready band: Scout RFP, Workday Integration and Workday Studio. The rest run from 24.8 down to 0.0. No member is counted as having an MCP server, though Scout RFP, Sana and Peakon carry an MCP candidate file. The post is careful about what a low access score means: the record shows little, and that does not prove a product's access process is poor.\n\nYou also notice the catalog admits some mess of its own. Workday Integration's api_count says 54, while its record lists 85 APIs and the catalog holds 88 entries with 193 operations between them. Every member's acquired field is empty, even where the description gives a year: 2019 for Scout RFP, 2021 for VNDLY and Peakon, 2024 for Evisort. And five memberships come from a parent-company property or prose instead of a declaration, so they deserve a closer look. The post says all of this is the catalog's to fix.\n\nThat candour changes how you read the page. The 26.4 is a number about the members, built on a rule that leaves out the strongest surface. It is not a verdict on Workday.\n\nWhat you take away is practical. Before you trust an estate rating, check whether the parent is counted, and look at the parent's own score. Read the access column separately from discoverability, because a product you can find is not always one you can get a key for. And treat the empty acquired fields and the 54-versus-85 count as signs that the record is still being cleaned up. For Workday, the post says the cheapest gain is carrying its access story into what it bought: one authentication path, documented in one place, on the Scout RFP, Peakon and Evisort surfaces.\n\nRead the original: https://apis.io/2026/11/04/workday-estate-rating-leaves-out-its-best-surface/",
  "title": "You Read “Best: 54.1” and Miss the Workday Surface That Scores 57.1",
  "topics": [
    "estate-ratings",
    "agent-readiness",
    "workday",
    "api-catalog"
  ],
  "published_at": "2026-11-04T19:09:45.120Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}