FOOTPRINT
<10 MB
The whole SDK, on-device model included.
Scenario 1. The river crossing
Give
the
order.
VerbKit lets players command their units in plain words, spoken or typed. Every order is understood on the phone or headset itself and carried out by your engine.
DISPATCH 0:08
“Wolves, hold the gate. Bears, hold the bridge.”
UNDERSTOOD ON DEVICE
Specifications
Chart 1. The runtime
PLATFORMS
iOS. Android. Quest. Vision Pro.
Swift for Apple platforms, a C API on every target, and one Unity package for all four. Typed orders everywhere. Spoken orders through each platform’s own on-device speech: Apple’s on iOS 26 and visionOS 26, Google’s on Android phones that have it, and VerbKit’s own transcriber on Quest.
HOST CALL
46 µs
Per call into your engine, measured on iPhone. Safe in the hot path.
ORDERS
If. When. Until.
Conditional and standing orders, played out over time by the SDK.
TOOLCHAIN
Agentic
Your coding agent designs the orders and wires the SDK into your game.
Sequence
of play
1
The player says or types the order.
2
VerbKit reads it on the device, into orders you designed. When it isn’t sure, it asks.
3
Your engine carries it out: now, on a signal, or when a condition holds.