I’m just guessing here, but I can’t imagine @manton caring what web browser or agent (like curl) you’re using, as long as you follow the terms of service and stay within the rate limit, etc. But that’s just my guess. 
I don’t know of any documentation on how the web app works, so you’ll probably have to reverse-engineer which requests to make. The authentication cookie is called rack.session.