API agnostic
handles a wide range of API and protocol types beyond REST/SOAP
Description
Volt4AI is not tied to any one API style. Out of the box it supports REST, WebSocket, gRPC, Volt Wires and Synapse, and new APIs or data protocols are added simply by creating a new agent in the Cortex framework. NQM’s BAE combat-system work, for example, adds AIS (multiple formats), ADS-B, InteACT, FedNet and the OMG specs OARIS, ALMAS and TEX.
Importance
Real system estates speak many protocols; supporting them all — and adding more as agents — avoids rip-and-replace integration. Volt surfaces services over multiple transports (Volt: Wire, Volt API).
Benefit
- Integrates heterogeneous systems that speak different protocols, not just modern REST APIs.
- New protocols are an additive agent, not a re-architecture.
Defence Relevance
Defence integration spans many legacy and specialist protocols, not just REST/SOAP. Maps to DTW Cycle 0 criterion 6 (ability to handle a wide range of API types beyond just REST or SOAP) and supports Challenge 5 (upgrade, integrate and interoperate at pace) — new protocols can be unified without disrupting existing consumers.
Civilian & Enterprise Relevance
Enterprises integrate legacy systems, industrial/IoT protocols and modern APIs through one fabric — protecting existing investments while modernising, without a forced migration.
Related
Sources
- NQM DTW Response §API types
- DTW Cycle 0 Challenge