One client for the three Demografix APIs — gender, age, and nationality prediction from names — reporting the remaining quota carried on every response.

Lorem Ipsum generator

Configure your application to send signals to a constellation of other 'apps'

sms-sdk-ruby

A parser DENSO calendar

A ruby interface to the Desk.com API V2

Desmos API Wrapper

Bungies Destiny API in an easily consumable ruby gem!

Detect language for given text.

Enables sending simple emails to app owners. Wraps [Leadersend](http://www.leadersend.com) mail delivery service and defines a DevelopmentNotification::Email model for logging.

Develoz Rails provides a CLI and composable generators for creating Rails 8.1 applications with a tested core stack and opt-in API, authentication, UI, deployment, and operations features.

A Ruby interface to the deviantART API, with some tokens from OAuth API.

A Ruby wrapper for the Etherios Device Cloud

REST Wrapper for Etherios Devicecloud

Communication helper gem for talking to Device Database

Auth0 authentication for devise

A gem to support duosecurity 2 factor auth.

Integrates devise authentication with iOS

Interacts with the ruby-jira gem to provide authentication of a login against a JIRA system.

There are plenty of gems out there that deal with being an OAuth2 "consumer", where you redirect users to an OAuth2 "provider", allowing you to hand off authentication to a separate service. There are also plenty of gems that set you up as your own OAuth2 provider. ***BUT***, what happens when you want to separate your "authentication" server from your "resource" server? This gem is meant to be used on an API "resource" server, where you want to accept OAuth Access Tokens from a client, and validate them against a separate "authentication" server. This communication is outside the scope of the official OAuth 2 spec, but there is a need for it anyway.