Choose your YeboID implementation

Pick the existing application's stack before installing anything. Native apps use the system browser and secure device storage. Product APIs validate access tokens and enforce resource ownership server-side. AI coding agents can read the SDK manifest, the full text guide, and the OAuth OpenAPI contract.

Stack	Implementation	Installation / distribution
Browser, React, Vue, Svelte	Web SDK	Existing yeboid-web npm package; React is optional
Node.js, Express	Node SDK	Existing yeboid-node npm package; JWT middleware and setup CLI
Flutter, Dart	Flutter SDK	Existing yeboid_flutter Git dependency
Swift, iOS, macOS	Swift SDK	Swift Package Manager source tag 0.1.0; AuthenticationServices + Keychain
Kotlin, Android	Android SDK	Gradle composite source build 0.1.1; AppAuth + Keystore; no Maven Central release claimed
React Native, Expo development build	React Native SDK	Built GitHub release tarball 0.1.0; native AppAuth + Keychain; no npm registry release claimed
Python, FastAPI, Flask, Django	Python SDK	pip Git source tag 0.1.0; online token verification; no PyPI release claimed
Go, ASP.NET/C#, PHP/Laravel, Java servers	OAuth protocol contract	Use the framework's OAuth client or the documented online-validation contract; no dedicated YeboID package yet

The new SDK source repositories and GitHub releases are public. Swift, React Native and Python use version 0.1.0; Kotlin uses 0.1.1, which fixes Android CI setup. Use the exact distribution method in each guide.

The Swift, Kotlin, React Native and Python implementations are separate repositories with their own tests, agent instructions and CI. They are initial releases. Their automated checks do not prove a completed human sign-in or physical-device behavior. Existing SDK release status is tracked separately in release evidence.

Choose the right setup path

• New React + Node app: npx yeboid-node init generates a starter. It does not generate other platforms.
• Existing web app: use yeboid-web without replacing its routing or UI framework. Add the Node SDK only if the backend uses Node.
• Native Apple app: use Swift Package Manager and register the exact custom-scheme callback. This initial SDK does not accept HTTPS/universal-link callbacks.
• Native Android app: use the Kotlin source package and AppAuth redirect receiver. Inspect the host's merged manifest and backup exclusions.
• React Native: link AppAuth and secure storage in a native host. Expo Go is unsupported; follow the native modules' Expo development-build setup.
• Python API or server-rendered app: use the Python package. Keep PKCE transactions/tokens in encrypted server-side sessions and coordinate refresh across workers.
• Another backend: use the standard protocol contract. Never install a similarly named package that the manifest does not list.

Live capabilities and setup checks

OIDC discovery is the authoritative public endpoint catalog: /.well-known/openid-configuration. On 24 October 2026 it advertised authorization-code, refresh and business token exchange, S256 PKCE and the supported scopes. Authorization uses https://yeboid.com/oauth/authorize; token and profile calls use the API origin. Do not infer one origin from the other.

The public /oauth/scopes catalog and /oauth/clients/{clientId}/configuration registration checks are available in the final production check on 24 October 2026. The existing demo client returned its exact native callbacks and permitted scopes. All four new SDKs validate registration before starting sign-in. API failures and permission mismatches are errors; never bypass them or fabricate a successful preflight.

YeboID does not advertise device-code or client-credentials grants. Agents may implement integrations or use a consenting person's authorized session; they cannot obtain autonomous machine identity through an unsupported grant. Leave human verification and consent to the human.