# BotMarketing.pro

> Business setup through an owner-authorized MCP server and REST API: company profile, catalog, loyalty, availability schedules, automatic messages and channel settings.

## MCP and API

- [MCP connection guide in English](https://botmarketing.pro/en/developers/mcp): capabilities, prerequisites and connection steps.
- [MCP connection guide in Russian](https://botmarketing.pro/developers/mcp): возможности и подключение.
- [Agent reference in Markdown](https://botmarketing.pro/en/developers/mcp.md): endpoints, scopes, restrictions and the current MCP tool catalog.
- [OpenAPI contract](https://botmarketing.pro/api/v1/openapi.json): public REST schemas for /api/v1.
- [OAuth protected resource metadata](https://botmarketing.pro/.well-known/oauth-protected-resource/mcp): protected MCP endpoint and authorization server.
- [OAuth authorization server metadata](https://botmarketing.pro/.well-known/oauth-authorization-server): authorization, token and dynamic client registration endpoints.

## Connection

Start by asking the user for the task, not by asking them to fill website forms. Call get_connection_guide on public onboarding MCP for the workflow. Register a new account if needed, wait for the owner to confirm email and grant access, then perform company setup and verify results yourself. Do not create a duplicate account for an existing user.
Protected MCP: https://botmarketing.pro/mcp (Streamable HTTP; OAuth Authorization Code with PKCE S256, or an owner-issued Sanctum bearer key).
Public onboarding MCP: https://botmarketing.pro/mcp/onboarding (registration and reference data only; no company access).
Existing users sign in on the website and grant scopes. New users must verify email before accessing company data. One owned company per account; current subscription features and limits apply.
After connecting, call get_setup_status to read the granted abilities, actual subscription limits and remaining setup steps. Reference dictionaries are available on the protected server too. Use tools/list for argument schemas. Creation requires an idempotency_key; REST uses Idempotency-Key. API keys do not expire and remain valid until revoked.
Chat clients need HTTP MCP and OAuth support. DeepSeek can be used through a custom function-calling agent or MCP client; direct web-chat integration is not advertised.

## Access and side effects

Read and write scopes are separate for company, catalog, loyalty, schedule, messages and channels. Activation can start automatic messaging. Only activate a feature when requested by the owner.
This API excludes CRM operations, order and reservation processing, staff management, financial transactions, customer loyalty balance adjustments, one-off bulk messaging and Instagram post publication.