The Workday estate rolls up 9 provider profiles and 73 APIs. Its best member scores 54.1 on the Kin Score, and the estate rates 26.4, in the thin band. But the Workday provider itself scores 57.1, in the strong band, with an agent score of 34.4 and 16 APIs. It is the estate’s parent and sits outside the surfaces list, so neither its score nor its APIs count.
The other estates I checked work the same way (Cisco, Broadcom, Oracle and Salesforce), and the effect varies. Salesforce has the wider gap: a parent at 82.3 and a best member at 73.5. At Cisco, Broadcom and Oracle the best member beats the parent. Rating the members separately is defensible, because it asks how the rest of the company measures up. A reader who sees “Best: 54.1” can still reach the wrong conclusion, so the parent’s score should appear next to the rating. That one is ours to fix.
The nine members
| Member | Kin Score | Agent | APIs | Access clarity |
|---|---|---|---|---|
| Workday Finance | 54.1 | 24.1 | 2 | 47.4 |
| Workday Integration | 52.1 | 28.9 | 54 | 47.4 |
| Workday Studio | 51.0 | 28.9 | 2 | 47.4 |
| Sana | 44.0 | 24.8 | 1 | 39.5 |
| Scout RFP | 41.7 | 31.8 | 11 | 15.8 |
| Flowise | 37.1 | 21.3 | 1 | 31.6 |
| Peakon | 32.8 | 22.3 | 1 | 0.0 |
| Evisort | 24.2 | 19.6 | 1 | 5.3 |
| VNDLY | 2.9 | 0.0 | 0 | 0.0 |
Acquisitions do not inherit access
The last column is the story. The three Workday-branded surfaces and the parent all score 47.4 on access clarity. 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, and Flowise, described as an open-source builder, reaches 31.6.
On discoverability the acquired products do fine: 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, and the record says less about getting a key.
Scout RFP makes the point on its own. It has the estate’s best agent score at 31.8 and 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 other scores 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.
A low access score means the record shows little. It does not prove that a product’s access process is poor.
Three other things in the record
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. All of this is ours to fix.
Takeaway
Workday’s 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. See the rollup at apis.io/estates/workday/.