title: Domain availability checks through a REST API
body: <p>Note: i'm not looking for a domain availability webservice! Now that we got that out of the way ...</p>
  
  <p>How would I architect a system that both allow us to retrieve resources from our domain portfolio through our REST API and also perform domain availability checks in the same API? Is it a good idea to use the same URI for both cases or should I use a different resource for this?</p>
  
  <p>For example:  </p>
  
  <p>If I want information on example.com (which is a domain in our portfolio) I would <code>GET /domains/example.com/</code> to retrieve our information on it (registration info like nameservers, contacts, etc ... but also internal information like our client record, invoice number, etc ...) .</p>
  
  <p>If I would want to get the domain availability for example.org (which is not registered with us so not in our portfolio) I would also call <code>GET /domains/example.org/</code> which then would return wether or not the domain is available.</p>
  
  <p>In short: is it a good idea to use the same URI for these two things (which basically both return info on a domain?) or should I use a different resource for this? <code>/domainregistration/example.com/</code> for example?</p>