Lanyard vs Open Collective

Lanyard exposes a Discord user's live presence — online status, current activities (games, Spotify listening data), and any custom key-value data set via their Discord bio — over a free public REST endpoint or a subscribable WebSocket feed, with no authentication required. The catch is that both the requester and the target user must share a Discord server with Lanyard's bot, since Discord's gateway only surfaces presence data for mutual-guild members.

Open Collective's GraphQL API (v2) queries collectives, expenses, transactions, and members for the platform's transparent nonprofit/open-source funding model, and public collective data is readable with no authentication at all. Its own docs flag the older REST API as still running but no longer developed, pointing new integrations at the GraphQL surface and a companion PDF service (for receipts and invoices) that accepts either a personal token or an OAuth bearer token. A personal access token, not a full OAuth app-review flow, is the documented way to authenticate for private or write access.