Namecheap Instant Answer

**What does your Instant Answer do?**
When a user's query begins with "namecheap", we do a domain lookup to the NC API. If the domain is available, a purchase link to Namecheap is provided. If not, a link to make an offer to the owner is provided via DomainAgents.

**What problem does your Instant Answer solve (Why is it better than organic links)?**
The instant answer provides a simple way of purchasing domains straight from a user's DDG query.

**What is the data source for your Instant Answer? (Provide a link if possible)**
[NameCheap API](https://www.namecheap.com/support/api/intro.aspx)

**Why did you choose this data source?**
It provides responses for TLDs that relate to NameCheap. Modular + expandable :+1: 

**Are there any other alternative (better) data sources?**
Many alternative domain services with APIs... wouldn't say any are better but NameCheap has most relevant data

**What are some example queries that trigger this Instant Answer?**
`namecheap qwoenqwe.com`

**Which communities will this Instant Answer be especially useful for? (gamers, book lovers, etc)**
Domain enthusiasts, web power users, programmers, business owners

**Is this Instant Answer connected to a DuckDuckHack [Instant Answer idea](https://duck.co/ideas)?**
No

**Which existing Instant Answers will this one supersede/overlap with?**
None

**Are you having any problems? Do you need our help with anything?**
We are using jQuery to parse XML into JSON. This works fine, but it may be better as a backend Perl service.

**What are the terms of use for the API? Will DuckDuckGo need specific authorization (e.g. an API key)? Are there any costs associated with API usage?**
No costs. DuckDuckGo needs to acquire [NameCheap API](https://www.namecheap.com/support/api/intro.aspx) keys as instructed in documentation.

**Where did you hear about DuckDuckHack? (For first time contributors)**
Zaahir from DuckDuckGo

### Screenshots
https://imgur.com/I2MHif1,JxbJfEH#0
Should probably use a `startend` trigger so it will only handle "namecheap <url>" and "<url> namecheap "

If "namecheap" is in the middle of the query, it means the remainder won't just be a domain. We could definitely handle that though and parse the remainder for a domain if you'd like. Then we would be able to handle queries like, "is <url> available on namecheap".