About 296 results: "api.duckduckgo.com"
Page 4 of 15
Filter Results
Sources
Languages
Filter Results
Try Search On




  1.     <DL><p>
  2.         <DT><A HREF="http://www.google.com/search?hl=en&q=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="g">Google</A>
  3.         <DT><A HREF="http://images.google.com/images?hl=en&q=%s&gbv=2" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="img">Google Images</A>
  4.         <DT><A HREF="http://video.google.com/videosearch?q=%s&sitesearch=" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="vid">Google Video</A>
  5.         <DT><A HREF="http://news.google.com/news?hl=en&ned=us&q=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="news">Google News</A>
  6.         <DT><A HREF="http://www.bing.com/search?q=%s&form=QBLH&qs=n" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="bing">Bing</A>
  7. <DD>Bing is a search engine that finds and organizes the answers you need so you can make faster, more informed decisions.
  8.         <DT><A HREF="http://www.bing.com/images/search?q=%s&form=QBIL&qs=n" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="bingimg">Bing Images</A>
  9.         <DT><A HREF="http://www.bing.com/videos/search?q=%s&form=VBREQY" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="bingvideo">Bing Video</A>
  10.         <DT><A HREF="http://www.bing.com/news/search?q=%s&form=QBNB" ADD_DATE="1325958071" LAST_MODIFIED="1325958071" SHORTCUTURL="bingnews">Bing News</A>
  11.         <DT><A HREF="http://duckduckgo.com/?q=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="d">DuckDuckGo</A>
  12.         <DT><A HREF="http://clusty.com/search?input-form=clusty-simple&v%3Asources=webplus&query=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="c">Clusty</A>
  13.         <DT><A HREF="http://labs.powerset.com/wikisearch/search?q=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="p">Powerset</A>
  14.         <DT><A HREF="http://en.wikipedia.org/wiki/Special:Search?search=%s" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="w">Wikipedia</A>
  15.         <DT><A HREF="http://www.answers.com/main/ntquery?s=%s&gwp=8" ADD_DATE="1325958072" LAST_MODIFIED="1325958072" SHORTCUTURL="a">Answers.com</A>
  16. <DD>Answers.com - the ultimate answer engine, with quick accurate dictionary, thesaurus, encyclopedia, bios, tech terms, news, sports, weather, and much more.










  1. 
                        
  2. At DuckDuckGo, we truly appreciate our community members taking the time to contribute to our open-source repositories. In an effort to ensure contributions are easy for you to make and for us to manage, we have written some guidelines that we ask our contributors to follow so that we can handle pull requests in a timely manner with as little friction as possible.
  3. 
                        
  4. Before you can do anything, you first need a [GitHub account](https://github.com/signup/free). This is required because we use GitHub to handle all incoming *Pull Requests* (code modifications) and *Issues* (bug reports) which cannot be made without a GitHub account.
  5. 
                        
  6. - Firstly, please make sure the bug is related to the **Fathead** repository. If this bug is about the DuckDuckGo API, or the relevancy of our search results, please visit our feedback page at <https://duckduckgo.com/feedback>. If you're unsure, its best to use the feedback page (your message will be passed along to the correct people).
  7. 
                        
  8. - Check the **Fathead** [issues](https://github.com/duckduckgo/zeroclickinfo-fathead/issues) to see if an issue already exists for the given bug or suggestion
  9.     - Clearly describe the bug/improvemnt, including steps to reproduce when it is a bug
  10.   - If one already exists, please add any additional comments you have regarding the matter
  11. 
                        
  12. - Before making any changes, refer to the [DuckDuckHack Styleguide](https://dukgo.com/duckduckhack/styleguide_overview) to ensure your changes are made in the correct fashion
  13. - Make sure your commits are of a reasonable size. They shouldn't be too big (or too small)
  14. 
                        
  15. 4. Add your info to the instant answer so we can give you credit for it on the [Goodies page](https://duckduckgo.com/goodies). You'll see your name or handle on the live site!
  16. Check out the [Metadata documentation](https://dukgo.com/duckduckhack/metadata) for detailed instructions on how to include your name and links.

  1. 
                        
  2. At DuckDuckGo, we truly appreciate our community members taking the time to contribute to our open-source repositories. In an effort to ensure contributions are easy for you to make and for us to manage, we have written some guidelines that we ask our contributors to follow so that we can handle pull requests in a timely manner with as little friction as possible.
  3. 
                        
  4. Before you can do anything, you first need a [GitHub account](https://github.com/signup/free). This is required because we use GitHub to handle all incoming *Pull Requests* (code modifications) and *Issues* (bug reports) which cannot be made without a GitHub account.
  5. 
                        
  6. - Firstly, please make sure the bug is related to the Goodie repository. If this bug is about the DuckDuckGo API, or the relevancy of our search results, please visit our feedback page at <https://duckduckgo.com/feedback>. If you're unsure, its best to use the feedback page (your message will be passed along to the correct people).
  7. 
                        
  8. - Check the Goodie [issues](https://github.com/duckduckgo/zeroclickinfo-goodies/issues) to see if an issue already exists for the given bug or suggestion
  9.     - Clearly describe the bug/improvemnt, including steps to reproduce when it is a bug
  10.   - If one already exists, please add any additional comments you have regarding the matter
  11. 
                        
  12. - Before making any changes, refer to the [DuckDuckHack Styleguide](https://dukgo.com/duckduckhack/styleguide_overview) to ensure your changes are made in the correct fashion
  13. - Make sure your commits are of a reasonable size. They shouldn't be too big (or too small)
  14. 
                        
  15. 4. Add your info to the instant answer so we can give you credit for it on the [Goodies page](https://duckduckgo.com/goodies). You'll see your name or handle on the live site!
  16. Check out the [Metadata documentation](https://dukgo.com/duckduckhack/metadata) for detailed instructions on how to include your name and links.




  1. 
                        
  2. At DuckDuckGo, we truly appreciate our community members taking the time to
  3. 
                        
  4. Before you can do anything, you first need a [GitHub account](https://github.com/signup/free). This is required because we use GitHub to handle all incoming *Pull Requests* (code modifications) and *Issues* (bug reports) which cannot be made without a GitHub account.
  5. 
                        
  6. - Firstly, please make sure the bug is related to the **Spice** repository. If this bug is about the DuckDuckGo API, or the relevancy of our search results, please visit our feedback page at <https://duckduckgo.com/feedback>. If you're unsure, its best to use the feedback page (your message will be passed along to the correct people).
  7. 
                        
  8. - Check the **Spice** [issues](https://github.com/duckduckgo/zeroclickinfo-spice/issues) to see if an issue already exists for the given bug or suggestion
  9.     - Clearly describe the bug/improvemnt, including steps to reproduce when it is a bug
  10.   - If one already exists, please add any additional comments you have regarding the matter
  11. - Before making any changes, refer to the [DuckDuckHack Styleguide](https://duck.co/duckduckhack/styleguide_overview) to ensure your changes are made in the correct fashion
  12. - Make sure your commits are of a reasonable size. They shouldn't be too big (or too small)
  13. - Make sure your commit messages effectively explain what changes have been made, and please identify which instant answer or file has been modified:
  14. 
                        
  15. 4. Add your info to the instant answer so we can give you credit for it on the [Goodies page](https://duckduckgo.com/goodies). You'll see your name or handle on the live site!
  16. 
                        
  17. 5. Go into GitHub and submit a [pull request!](http://help.github.com/send-pull-requests/) to the **Spice** repository, making sure to use the **Spice** repository's **[Pull Request Template](https://github.com/duckduckgo/zeroclickinfo-spice/blob/master/pull_request_template_spice.md)**. This will let us know about your changes and start the conversation about integrating it into the live code.

Back to Top