Pi Sign-in Launches as OAuth Login for Third-Party Apps

High attention and emotional sentiment detected.

The Pi Core Team first released the feature on June 28, 2026, during Pi2Day. Then, on June 30, the team promoted it through an official tweet. Today it runs in its initial form for developers who configure their apps.

What Pi Sign-in Actually Is

Pi Sign-in is an OAuth 2.0 single sign-on, or SSO. In short, it works much like “Sign in with Google” or “Sign in with Apple.” Instead of building their own login, apps can recognize a user through a Pi account.

According to the Pi Core Team, the goal is broad reach. The official tweet says the feature helps “applications and services to recognize, connect, and serve users across and outside the ecosystem.”

The team also frames this release as a starting point. In the Pi2Day 2026 blog post, the Core Team calls it “the initial version of Pi Sign-in which will be iterated and improved over time.”

How the Pi Sign-in Login Works

First, a user clicks “Sign in with Pi” on a supported site. Next, the browser redirects to the Pi authorization server at accounts.pinet.com. The request carries a client_id, a redirect_uri, a scope, and a state value.

Then the user approves the request. They can authenticate inside the Pi Browser, or they can scan a QR code. After approval, the server sends the user back to the app with a short-lived access token.

Finally, the app reads that token and verifies the state value. So the app then calls the endpoint at api.minepi.com/v2/me. As a result, it receives an app-specific user ID plus any consented data.

For now, the release uses the OAuth implicit flow, so no client secret is required. According to the developer documentation, an authorization code flow with PKCE is planned for later.

What Data Pi Sign-in Shares

By default, an app receives only the user’s username. Optionally, a developer can also request the wallet_address scope. In every case, the user must give explicit consent before any data moves.

The handshake also returns an app-specific uid. Because that ID stays unique per app, two apps cannot easily link the same person. So the design limits cross-app tracking by default.

Notably, Pi Sign-in is an off-chain feature. The login itself never touches the Pi blockchain, and no contract records the handshake. Even the optional wallet_address scope simply returns an address, nothing more.

How Pi Sign-in Compares to Google Sign-In and World ID

Why Pi Sign-in Matters for the Ecosystem

Pi Network grew a large base of Pioneers since its 2019 launch. Many of those accounts also passed KYC checks over the years. As a result, the network now holds a pool of verified human identities.

For developers, that pool lowers a real barrier. Instead of building their own login and identity stack, apps can tap Pi accounts directly. So onboarding friction drops for both sides.

To use it in production, though, a developer must register first. Specifically, they verify their domain and register a redirect URI in the Pi Developer Portal. Therefore the feature is not fully open to anyone without setup.

Crypto outlets covered the rollout quickly. For example, MEXC News and KuCoin News described Pi Sign-in as a “major leap for Web3 identity” and a “professional Web3 login.” Both outlets are exchange-affiliated, so their framing leans positive.

What Pi Sign-in Does Not Solve

Still, the launch leaves open questions. The Core Team has not released figures for supported apps or active users. So real adoption remains unclear for now.

Pi’s mainnet also stays in its enclosed phase, even as apps and payments run on it. Meanwhile, critics continue to question the project’s decentralization and its team-controlled servers. Because the OAuth server sits with the Core Team, some observers flag centralization concerns.

Loyal Pioneers, by contrast, frame the feature as clear utility progress. On X, supporters called it a “game changer” and “a win for users and developers.” Outside skeptics, however, remain cautious about Pi’s broader legitimacy.

Market Reaction and What Comes Next

The PI token saw a muted market response. According to CoinGecko, PI traded near $0.1178 around June 30, with one 24-hour reading up about 4.4%. Yet broader reports noted a dip near 5% across the Pi2Day period.

Market cap sat near $1.27 billion at the time, according to CoinGecko data. Reported 24-hour volume ranged widely, from several million dollars to roughly $18 million across trackers. None of this counts as financial advice, so always do your own research.

Next, the team plans to iterate on the feature over time. Additional OAuth flows and new scopes could follow, according to the developer docs. For now, developers can explore the integration through the Pi developer portal and start testing Pi Sign-in today.