README.md in evervault-1.0.0 vs README.md in evervault-1.1.0

@@ -94,11 +94,11 @@
 Evervault.run(cage_name = String, data = Hash[, options = Hash])
 ```
 
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
-| cageName | String | Name of the Cage to be run |
+| cage_name | String | Name of the Cage to be run |
 | data | Hash | Payload for the Cage |
 | options | Hash | [Options for the Cage run](#Cage-Run-Options) |
 
 #### Cage Run Options
 
@@ -115,11 +115,24 @@
 Evervault.encrypt_and_run(cage_name = String, data = Hash)
 ```
 
 | Parameter | Type | Description |
 | --------- | ---- | ----------- |
-| cageName | String | Name of the Cage to be run |
+| cage_name | String | Name of the Cage to be run |
 | data | dict | Data to be encrypted |
+
+### Evervault.create_run_token
+
+`Evervault.create_run_token` creates a single use, time bound token for invoking a cage.
+
+```ruby
+Evervault.create_run_token(cage_name = String, data = Hash)
+```
+
+| Parameter | Type   | Description                                          |
+| --------- | ------ | ---------------------------------------------------- |
+| cage_name | String | Name of the Cage the run token should be created for |
+| data      | Hash   | Payload that the token can be used with              |
 
 ### Evervault.cages
 
 Return a hash of your team's Cage objects in hash format, with cage-name as keys