Official 0.1.0 Release.

The VigLink class now does things.

Added a client property to VigLink class, holds Guzzle client, only need one.

Added an apiKey property to VigLink class, gets set as first parameter in
  constructor or, if the __VIGLINK_PHP_API_KEY__ magic constant is set, it gets
  set to that magic constant.

Added a secretKey property to VigLink class, gets set as second parameter in
  constructor or, if the __VIGLINK_PHP_SECRET_KEY__ magic constant is set, it
  gets set to that magic constant.

Added a locUrl property to VigLink class, gets set as third parameter in
  constructor or, if the __VIGLINK_PHP_LOC_URL magic constant is set, it gets set
  to that magic constant.

All above properties are protected.

Added a monetizeURL method to the VigLink class, takes these parameters:
  - url - URL to monetize
  - loc - the location the user will come FROM when they click this link, usually
          your sites URL. If the locUrl property is set during construction, this
          can be left null, otherwise it MUST be passed.
  - ref - Default: null; Not Required; The referrer for this link, generally your
          site
  - return_string - Default: true; Should we return the response body as a string
                    or a Guzzle Response object? Up to you, if its returned as
                    a string, you will get the monetizied URL (or the original
                    if the monetization process failed) AND THAT'S ALL. With the
                    Guzzle Response object you get the whole shebang.

Also... VigLink Customer Support is... amazing.