title: Routes for MVC 4 Web APIs?
body: <p>In my initial stab at creating a MVC4 Web API. I've noticed a few things about the way routes are handled that seems a little off:</p>
  
  <ul>
  <li>Controllers no longer ever have more than 4 actions?</li>
  <li>A resource that only supports one HTTP verb still gets it's very own controller?</li>
  <li>The route hierarchy tends to be very flat, OR</li>
  <li>An extremely large number of routes must be specified/maintained compared to MVC apps for humans.</li>
  </ul>
  
  <p>I've created fairly large sites that use only two or three routes, but I'm just starting on my API and I'm up to almost a dozen. I guess APIs by their nature lend themselves to deeper URLs than websites, but this seems a little excessive.</p>
  
  <p>I feel like I'm missing a namespace somewhere or a routing convention. I attribute nearly all of this to the fact that action names are no longer part of the route, just the HTTP method. Is there a way to support routes by anything other than parameter matching, controller name, and HTTP method?</p>