Clipper agent

[twolfson]

I have had this idea for a while and figured I would act on it but still haven't due to barrier to entry of learning ruby. Anyway, here it goes:

The Clipper card is a multi-transit system paycard for the SF Bay Area. The system has an autoload feature but it only works when the balance goes below $10.

The basic idea is to create an agent which:

• Monitors balance for threshold
• When below threshold, auto-deposit pre-defined amount
• Bonus: Could track daily transit usage
• Bonus: There is a delay of up to 5 days when depositing online, Huginn could be smart and pre-determine when the threshold will be reached and deposit 5 days early

This is a little short sighted as it only applies to the Bay Area but it probably could serve a nice boilerplate for other transit systems.

As far as implementation goes, some options are scripted purely in Ruby (depends how much AJAX happens on page), scripted via PhantomJS, or we create an API wrapper for Clipper and hit that.

[cantino]

Hey @twolfson, that seems like an excellent usage for Huginn. Does Clipper have an API? If so, adding either a "Clipper Agent" or a more generic REST API Agent should be fairly easy to integrate with their API. If they don't have an API, you might have to fall back to scraping. Let me know how I can help!

[0xdevalias]

@twolfson Did you ever look into this more/implement anything?

[twolfson]

I started to reverse engineer their web interface but did not complete it due to slowless of current toolset. It is still on my TODO list but feel free to pick it up

http://undocumented.io/clipper/

[0xdevalias]

@twolfson Fair call :) I probably won't personally (Australian, so not a huge benefit to me :p) Btw, I love the idea with undocumented.io!!! Would be super keen to see what happens with it if you decide to expand on it.

Will close this for now as i've added it to the agent suggestions list in #353

[twolfson]

Works for me. Thanks for reaching out to get the status =)

[0xdevalias]

No worries :)