Kaltura publishes 222 APIs on the network with a composite of 48.6 — the developing band — and an agent-readiness score of 30.6 (agent-aware). Its agentic-access contract enumerates 1,250 operations, of which 1,250 are acting and 41 are human-in-the-loop.
Read that again. Twelve hundred and fifty operations, and every single one of them classifies as acting.
One hundred percent acting
Across every provider profiled this week the acting ratio has hovered near half — GitHub 49%, Telnyx 53%, Grafana 54%. Kaltura is at 100%.
That is not a company recklessly exposing writes. It is a consequence of API shape. Kaltura is an RPC-style service API: the surface is organised as service.action — accessControl, accessControlProfile, adminUser, analytics, annotation, announcement, appToken, asset, baseEntry, batch, bookmark, and 211 more, each with actions hanging off it. Everything is a POST to an action endpoint, including the ones that just read.
So the classifier that separates safe reads from state changes has nothing to work with. In REST, GET /entries is self-evidently a read. In RPC, POST /service/baseEntry/action/list is indistinguishable at the protocol level from POST /service/baseEntry/action/delete.
This is the most concrete cost of RPC-over-HTTP that I have seen quantified. It is not aesthetic. An agent given this surface cannot tell, without reading prose documentation, which of 1,250 operations are safe to try — so a cautious agent treats all of them as dangerous, and a careless one treats none of them that way. 41 human-in-the-loop markers out of 1,250 is what is left doing the work.
The facet spread
| Facet | Score |
|---|---|
| Contract quality | 61.7 |
| Governance | 58.3 |
| Operational transparency | 52.6 |
| Discoverability | 50.0 |
| Commercial clarity | 50.0 |
| Developer ergonomics | 21.7 |
Contract quality at 61.7 says the definitions exist and are well-formed. Developer ergonomics at 21.7 is the floor of this profile and it is downstream of the same problem: a 222-entry RPC surface with 1,250 actions is genuinely hard to onboard onto, and the catalog finds little in the way of examples or getting-started paths to soften it.
What is actually in there
Kaltura is an open-source video platform — ingest, transcoding, live streaming, player customisation, analytics, and virtual classroom integration, across web, mobile, and OTT. Access is free with self-serve signup, and you can try it without a sales conversation.
The surface is genuinely comprehensive. Access control profiles, admin users, asset structures, attachments, audit trails, bookmarks, batch control — this is a platform that exposed its whole internal model, which is a real and increasingly rare kind of generosity. It just exposed it in a shape built for its own SDKs rather than for strangers.
Takeaway
222 APIs, 1,250 operations, and 100% of them classified as acting because RPC-over-HTTP erases the read/write distinction the protocol was designed to carry. Kaltura’s contracts are sound and its ergonomics score 21.7 — this is what a comprehensive platform looks like when the surface was designed for the vendor’s own client libraries.
See the full profile at apis.io/providers/kaltura/.