Originally Posted by
SparseFlyer
If you coded the whole thing, why don't you just add a price aggregator and add a constraint for $/badge?
Do you know how hard it is to price out a 60 segment itinerary?
You can only price out a limited number of segments at once, and you have to know where to split it.
The best option I found was an ITA QPX pricing API that cost something like $0.001 per query. I'd need to spend about $30,000 to run my algorithm with that
Also, from Twitter:
You'll find several new badges and cities in this version, as well as badges from the previous edition!
Anyone want to save me time and tell me what changed?
