Today we opened developers.aton-network.org. If you build an app, a site or a bot, you can now let people sign in with their Atheron account. You register the app yourself, test it the same day, and send it to us for a review when it is ready.
This post explains what you get, how it works, and what we check before an app goes live.
What you get
- Sign in with Atheron, built on OpenID Connect. Any standard OIDC library works with it.
- A test app and a live app for every registration. Only your team and up to 25 testers you name can sign in to the test app.
- Clear choices about data. You ask for the scopes you need: name, email, whether someone's age is verified, their membership plan, or the wallets they linked. People see each one on the consent screen before they agree.
- Keys, limits and usage. API keys per app, rate limits you can see, and charts of sign-ins, calls, errors and response times.
- Webhooks when someone signs in, takes back your access, or changes their membership plan. Every delivery is signed and retried.
- Docs and a sandbox. Quickstarts for Next.js, Node, Rust and mobile apps, every endpoint and claim, and a sandbox that runs real calls against your test app in the browser.
- SDKs for TypeScript and Python, with more languages to follow.
- An MCP server at `https://developers.aton-network.org/mcp`. Connect your AI coding tool and it can search the docs, write the sign-in code for your stack, check your redirect addresses and scopes, and explain an error.
Building and testing is free.
How it works
- Register your app in the developer portal. You get a test client and a live client straight away.
- Build against the test client. The Next.js quickstart takes you from nothing to a working sign-in.
- Add your homepage and your own privacy policy. Both are required to go live.
- Verify who you are. Each owner passes an identity check, or your business passes ours. A business check also puts a verified badge on your consent screen.
- Submit for review. Once we approve it, anybody with an Atheron account can sign in to your live app.
What we check, and why
People trust a sign-in button with their account. So before an app goes live, a person on our team looks at its name, logo, links and the scopes it asks for. We refuse apps that pretend to be Atheron or anybody else, and we ask you why you need a sensitive scope such as verified age or wallets. Automated checks help us find problems faster. A person makes the decision and writes the reason you see.
A few rules hold for every app:
- PKCE is required of every client, including server apps that keep a secret.
- Redirect addresses must match exactly.
- People can take back your access from their Atheron account at any time, and you hear about it by webhook.
- We never share a password, a date of birth, an identity document or a payment detail.
If an app harms people, we can suspend it at once. You see the reason in the portal and can appeal there, and people who used the app are told in their account.
The button
The branding page has our button kit: one stylesheet, our mark, dark and light themes, three sizes and the label in English, French, Spanish, German and Urdu. Copy the snippet and it looks right on your page.
Found a security problem?
Tell us first. Our disclosure page explains how to reach us and what we promise in return.
Start today
Sign in at developers.aton-network.org with your Atheron account, register your first app and follow a quickstart. If you get stuck, the docs and the MCP server are there, and so are we.
