Now I'm between a rock and a hard place. One the one hand some parts of the MapQuest Open API are extremely bad, on the other hand Google has an all-or-nothing license for their geo data, and their native iOS maps component sucks.
MapQuest's cycling directions in Manhattan is worse than having no directions at all. They have a specific cycling flag you can set, but results will blatantly ignore bike lanes and send you down extremely wide avenues with no bike lanes and heavy traffic. IMO using MapQuest's cycling directions, at least in NYC, is an extreme hazard, and I can't in good conscience integrate it into my app.
http://www.yournavigation.org/
Despite the clunky interface, I was pleasantly surprised by its biking directions: not as good as Google, but not terrible either. (I was in NYC when I tried using it for awhile.) It's fully open-source.
The former seems to disregard bike lanes entirely and generates some pretty hazardous recommendations (including cycling down 5th Ave, or busy sections of Park Ave in Midtown).
The "bicycle (routes)" mode does better and seems to respect bike lanes, but not consistently. There are some endpoints where it still maneuvers you into dense traffic with no bike infrastructure, when a bike-laned street is nearby and takes only marginally longer. I just checked the OSM's dataset and the data is good - so it isn't a matter of someone inserting a bike lane where one doesn't actually exist.
The app I'm working on is for NYC's new bikeshare system... Still not an acceptable alternative unfortunately. I may just give up and use Google Maps in the iOS app, but the performance of Google's native map component is extremely, extremely bad.
You could either take their code and run an instance for NYC, or smile sweetly at them and ask if they might host one themselves. Github link: https://github.com/cyclestreets
And yes, more municipalities need to start releasing open data.