However, I found a few flaws after a couple of minutes of testing.
1. Neither search nor autocomplete appears to support filtering by fields other than country? We have an app that needs to filter autocompletions by state. A focus point might be sufficient if the autocompleter aggressively sorts results based on distance, but I have yet to meet one that does this (or allows a tuning of the distance function). A rectangular bounding box filter doesn't cut it. I guess I'll have to check out the code and see if this can be added/improved.
2. The API only returns points, with no boundary information, for street addresses. We have an app that uses geocoding to match street addresses to points. But if your address is a bit imprecise and matches an entire stretch of highway (it happens a lot!), that's obviously not a valid match — something like "Highway 66" is just wrong. Google will wisely return a bounds object that you can compute the area for and determine if it's small enough that it's likely a precise enough location (we use 10m2 as the maximum). Unlike Google, Mapzen doesn't even tell you that your match is a "route" — everything is an individual street address. Not sure how trivial this would be to implement, as boundaries would need support from datasets; OSM has the required data, OpenAddresses might not.
3. Street address matching seems a bit patchy. I tried my Brooklyn street address, and it didn't find it. The building was constructed last year, though, so maybe it's old data. Can someone from Mapzen comment?