Procore and Bentley Systems are the two providers the Construction tag page ranks first, at 63.9 and 62.9 on the Kin Score, both strong, 1.0 point apart. The Kin Score measures the public API surface, not the product and not the company. In a tag of 314 providers whose 312 scored members average 15.6, both sit more than 47 points above their own category. Bentley wins five of the six facets. Procore finishes first on the sixth, and the sixth was built almost entirely by us.
The business. These are not the same purchase. Procore is the construction management platform, the system of record for a job: project management, financials, quality and safety, field productivity. Bentley is infrastructure engineering software, the design, construction and operation of roads, bridges, rail, water and energy, and it reaches developers through iTwin, a digital twin platform. So the tag holds two senses of the word: running the job, and modelling the asset. Access differs too. Bentley publishes its developer pricing, a free Community tier with 100 credits a month and a Standard tier at $199 a month with credits at $1.20, and signup is self-serve. Procore’s pricing page gives no numbers and asks you to get a custom quote. Its catalog record still reads freemium, which the pricing page does not support, so we are filing that. Bentley states its limits, 500 calls a minute on Community and 5,000 on Standard. Procore flags rate limiting on 3,292 of 3,296 operations in a 60-minute window per token, with three response headers, but we hold no numeric limit for it.
The APIs. This is a real difference in scale, and it is the one thing the score does not reward. Procore has 534 API pages carrying 3,391 operations, against Bentley’s 87 pages and 299 operations. Procore declares one API and the catalog splits it by resource group, so read pages as resources and operations as the honest unit. On one side are the Budget, Change Orders, Daily Logs and Drawings APIs. On the other are Changesets, Briefcases and iTwin Visualization. Bentley’s page lists 8 Arazzo workflows, 149 collections and a 319-operation agentic access profile, against none of those for Procore. Do not read that as Bentley’s work. All 8 workflows and the access profile were derived by the catalog, so they say what we have done for Bentley, not what Bentley ships.
The experience, facet by facet. Bentley takes discoverability 78.6 to 67.9, contract quality 51.8 to 46.5, operational transparency 65.8 to 47.4, developer ergonomics 82.1 to 77.9, and access clarity 64.5 to 60.5. Those five facets carry 0.88 of the weight. Procore takes contract governance, 79.1 to 13.6, at a weight of 0.12. That one gap of 65.5 points is worth about 7.9 on the composite, more than Bentley’s five wins combined, and it is why Procore leads the six-facet base 61.7 to 60.3. The conditional layers then move Procore up 2.2 and Bentley up 2.6, which leaves the 1.0 point on the page.
Whose governance is it? Procore’s ruleset is marked as generated by API Evangelist tooling. Its conformance declaration and its vocabulary are marked as derived. All of them are dated 2026-10-20, the day its profile was rebuilt and its score moved up 34.6 points. The page records 0.0 first-party catalog points for Procore, against a floor of 24.0 for Bentley. So the lead reflects how recently we profiled each company, not a governance program at Procore, and these pages are still scored on rubric 0.24.0. The current rubric, 0.25.0, discounts credit for derived work, and this order should not be expected to survive it.
Agent readiness goes the other way and holds up better. Procore scores 45.6 and is agent-ready, Bentley 24.8 and agent-aware. Procore’s contract carries verified examples and an idempotency token, though on only 9 of 1,667 mutating operations, and its band was gated down from agent-native because its error semantics are derived rather than a stable published envelope. Bentley lights neither examples nor idempotency. Two Procore lights need a caveat. Its protected resource metadata comes from a trust-center subdomain and describes a vendor’s service, not the Procore API, and the page’s documented MCP server conflicts with our own probe, which found none. We are filing both.
The verdict. If you are building on the job, the budgets, change orders and daily logs, Procore is the only one of these with that surface, and its 3,391 operations are the reason to choose it. If you are building on the model of an asset, Bentley is the only choice, and it is the easier one to start with, with public prices and self-serve access. Nobody should choose between them on a 1.0-point gap that our own files created. Procore’s path is publishing numeric rate limits and prices, and writing a ruleset of its own. Bentley’s is adding examples and a stable error envelope to its contracts, then an idempotency key on writes, which is what moves its agent readiness.