We were hoping for a quiet soft-launch so we could get more API feedback before a real launch (including use-cases like you suggested.)
The events are pushed back to a webserver, and you decide what to do there. If you already have an application and data storage etc already, this is basically the easiest thing to do. We felt this flexibility would lead to the most interesting initial apps; additionally, the vast majority of early adopters would probably not love being sandboxed.
 we also have a hanging HTTP api; call /next_event and it hangs until it has events for you. this lets you talk to the system without having a public open port.