Introduction

Auth314 is verification infrastructure for Pi Sign-in. It handles the Pi Network OAuth flow on your behalf and delivers a single signal to a webhook you control: whether a given user successfully verified their Pi account.

It's built for bots, apps, and websites that want to check whether someone is a real Pi Pioneer without implementing and maintaining a Pi OAuth integration themselves.

Auth314 is not affiliated with Pi Network or the Pi Core Team.

What you get

• A hosted verification page your users complete Pi Sign-in on
• A webhook callback with a verified: true / false result
• One-to-one enforcement: a Pi account maps to exactly one platform identity at a time, with automatic revocation if someone re-verifies elsewhere
• A dashboard for managing API keys and viewing usage

What you don't get

Per Pi's Developer Terms of Use, Auth314 does not forward a user's Pi UID or username to your webhook. You only learn that a user verified, not who they are on Pi Network. This is a hard constraint of the platform, not a limitation specific to Auth314 — see How verification works for why.

Where to start

• Quickstart — call /verify/init, get a link, receive a webhook
• API Reference — full request/response shapes
• Discord bot — Auth314's hosted Discord integration, if you don't want to build your own