Services

Service-oriented entry points for Sometic engines that sit beside UI components: authentication orchestration and the HTTP client.

These pages mirror the deeper guides under Authentication and Utilities. Use this hub when navigating from architecture or API maps.

Inventory

Service	Package	Deep docs
Auth controller	@sometic/auth	Authentication · Auth service
HTTP client	@sometic/http	HTTP utility · HTTP service
Auth HTTP seam	@sometic/http/auth	Interceptors

When to use this hub

• You need the package-oriented view of auth / HTTP next to Primitives
• You are wiring createAuth + createHttp without opening every auth subguide first
• You want the provider capability matrix in one place

When to use the deep guides instead

• Full session, refresh, authorization, and provider setup → Authentication
• Full HTTP recipes, retries, and SSR fetch injection → HTTP utility

Honesty

• Provider SDKs (Firebase, Supabase) are optional peers on @sometic/auth-firebase and @sometic/auth-supabase.
• @sometic/auth core has no Firebase / Supabase / OIDC lock-in.
• @sometic/http optionally peers on @sometic/auth; it never embeds provider SDKs.
• Client can() and HTTP status handling do not secure APIs. Servers enforce authorization.

Capability matrix (auth providers)

Capability	test	local	firebase	supabase	oidc
signIn	✓	✓	✓	✓
signOut	✓	✓	✓	✓	✓
register	✓	✓	✓	✓
getSession	✓	✓	✓	✓	✓
refresh	✓	✓	✓	✓	✓
getUser	✓	✓	✓	✓	✓
passwordReset	✓	✓	✓	✓
emailVerification	✓		✓
oauth				✓*	✓
mfa

* When signInWithOAuth exists on the injected Supabase client.

Related

• Auth service
• HTTP service
• Primitives
• Utilities
• API packages
• Beta maturity