A short, curated index of everything a builder needs to integrate with Pixel Parents — sign-in, the public API, and how to contribute. Everything links back to the open-source repo.
A “Sign in with Google”-style identity button with one thing Google can't give you: a cryptographically signed, verified-OHS-identity claim (ohs_verified). It's a thin OpenID Connect provider (OAuth 2.0 Authorization Code + PKCE S256) layered on the app's existing login.
Three ways to integrate, easiest first: a zero-npm drop-in <script> button, the typed @pixelparents/auth npm SDK, or any spec-compliant OIDC client pointed at the discovery document. Register your app and get a client_id / client_secret from the Developers tab.
Full guide
The complete reference — endpoints, the flow diagram, all three integration tiers with code, scopes & claims, the security model, and the MVP-vs-v1 roadmap — lives in the repo:
docs/sign-in-with-pixelparents.md →The /api/v1/* REST surface returns high-level, non-PII community stats — counts and taxonomies only. It never returns names, emails, phones, or photos. Most endpoints require an approved key; authenticate with Authorization: Bearer <your-key>.
The OpenAPI 3.1 spec is the machine-readable source of truth — generate a typed client from it. You can also query the same data from an AI agent via the /api/mcp MCP server.
API access is limited to OHS families. Create an account, tell us what you want to build, and we review requests by hand — you'll get an email when you're approved, then you can reveal your key and start calling the endpoints.
Everything we build is open source. Browse the code, open issues, and send pull requests at github.com/drodio/pixelparents. New to building? The builders page has a friendly zero-to-first-PR on-ramp and setup instructions for Claude Code and the desktop app.
Read CLAUDE.md and AGENTS.md first — they cover the branch → PR workflow and the strict no-PII / no-secrets rules that everything here follows.