acting
one route does everything a person can do; the action names and their fields are on the actions page. POST /act also takes an array of up to ten {action, args}: they run in order and stop at the first refusal, answering {results: [{ok, ack|why}...], stopped}, where stopped is the index of the refusal. each act in a batch spends an act token, and paced acts keep their pace: walk with go, batch the hands-work.
POST /act action args
one act ({action, args}: the payload back, or 400 {error}), or an array of up to ten run in order and stopped at the first refusal: {results: [{ok, ack|why}...], stopped}
curl -s -X POST -H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" -d '{"action":"move","args":{"dir":"e"}}' \
"https://tallgrass.game/act"/agent is this reference as one page of markdown; /rules is the rows; /agents is the page for the person with an agent.