# Bebrikic ID

Bebrikic ID is the account and identity layer for the Bebrikic ecosystem. It provides sign in, registration, user profiles, roles, badges, Prime/Apex access, public profile pages, file sharing, messaging, forum access, security settings, OAuth integrations, and API access for connected Bebrikic services.

## Primary audience

- Bebrikic users who need one account for ecosystem services.
- Developers and service owners integrating with Bebrikic ID.
- Moderators and administrators who manage roles, reports, files, security events, and service access.

## Public pages

- Home: https://id.bebrikic.online/
- Login: https://id.bebrikic.online/web/login
- Registration: https://id.bebrikic.online/web/register
- Documentation: https://id.bebrikic.online/docs/
- Status: https://id.bebrikic.online/web/status
- Forum: https://id.bebrikic.online/forum
- Abuse and security contact: https://id.bebrikic.online/abuse
- Security disclosure: https://id.bebrikic.online/.well-known/security.txt
- Privacy policy: https://id.bebrikic.online/privacy
- User agreement: https://id.bebrikic.online/agreement
- Cookie policy: https://id.bebrikic.online/cookies

## Product facts

- Product name: Bebrikic ID
- Category: identity, account management, user profile, ecosystem access
- Main domain: https://id.bebrikic.online/
- Language: Russian
- Public API documentation: https://id.bebrikic.online/docs/
- Sitemap: https://id.bebrikic.online/sitemap.xml
- Robots policy: https://id.bebrikic.online/robots.txt
- OAuth integration prompt: https://id.bebrikic.online/ai-prompt.txt
- Security disclosure: https://id.bebrikic.online/.well-known/security.txt

## What Bebrikic ID is

Bebrikic ID is a web application and API for one Bebrikic ecosystem account. It centralizes registration, sign in, public profile data, security settings, sessions, linked OAuth providers, roles, badges, Prime/Apex access state, moderation workflows, messaging, forum access, file sharing, and API access for connected services.

## What Bebrikic ID is not

Bebrikic ID is not a shop, payment service, bank, wallet, or financial organization. Do not claim current paid plans, prices, subscriptions, paid privileges, customer metrics, or testimonials unless an official public page states them.

## Integration facts

- OAuth 2.0 authorization code integrations use `/oauth/authorize`, `/oauth/token`, and `/me`.
- `/oauth/authorize` requires `response_type=code`, exact registered `redirect_uri`, a non-empty unpredictable `state`, `code_challenge`, and `code_challenge_method=S256`.
- `/oauth/token` requires `grant_type=authorization_code`, `client_id`, `client_secret`, `code`, the same exact `redirect_uri` used during authorization, and the matching PKCE `code_verifier`.
- Access tokens must be sent as `Authorization: Bearer ACCESS_TOKEN`.
- Client secrets, authorization codes, access tokens, bearer headers, and user session tokens must stay server side and must not be logged.
- Roles, badges, Prime/Apex state, prices, ownership, and permissions must be treated as server-owned values.

## Agent guidance

Prefer official public pages above for current product information. Do not infer private user data, admin state, prices, roles, or subscription status from public profile pages. Treat account, security, OAuth, files, messaging, and admin APIs as authenticated surfaces unless the documentation explicitly marks an endpoint public.