# Nika AI Nika AI is a Russian-language brand platform for AI agents and ready digital products for small businesses, individual entrepreneurs, and self-employed specialists in Russia. ## Core pages - Home: / - Ready agents: /agents - Ready products: /products - First launch map: /start - First product launch kit: /launch-kit - Product roadmap: /roadmap - Agent brand kit: /brand-kit - Agent selection quiz: /quiz - Nika chat demo: /chat - Website sales agent: /agents/site-sales - Telegram and MAX agent: /agents/telegram-max - Customer support agent: /agents/customer-support - Documents agent: /agents/documents - Operations agent: /agents/operations - Marketplace line: /agents/marketplaces - Product card generator: /products/product-card-generator - Product card generator sample page: /products/product-card-generator/sample - Product card generator pilot offer: /products/product-card-generator/pilot - Product card generator delivery acceptance: /products/product-card-generator/delivery - Custom agent development: /custom-agent - Security: /security - Pricing: /pricing - Lead integrations: /integrations - Launch readiness: /launch-readiness - Contact: /contacts ## What Nika AI offers - AI agent for website sales and lead intake. - AI agent for Telegram and MAX communication. - AI agent for customer requests and support. - AI agent for documents. - Operational AI agent for repeated tasks. - Ready product line, starting with a product card generator for marketplace sellers and product teams. - Custom AI agent development for specific business processes. ## Brand system The public brand contract is available at /brand-system.json. Nika is the single recognizable face for the website, chat widget, Telegram, MAX, the product card generator, marketplace line, and future agents. New agents and products should keep the Ocean Coral design system, DM Sans typography, lucide-react icons, calm business tone, attribution-aware lead intake, and explicit human confirmation boundaries. The human-facing agent brand kit lives at /brand-kit. The machine-readable interface kit is /agent-interface-kit.json. They define how every future agent should look and sound: one Nika face, Ocean Coral, DM Sans, Lucide icons, calm business voice, required agent card fields, and human confirmation boundaries. The Nika chat demo lives at /chat. It is a deterministic local consultant demo for product selection, pricing, security, integrations, product card generator questions, and handoff to /quiz or /contacts. It is not the final production LLM chat. Production chat requires a backend, model integration, sessions, knowledge base, limits, logs, and MAX or Telegram handoff. ## Product line The first launch map lives at /start. The machine-readable launch-start contract is /launch-start.json. Use it when a visitor or owner needs to choose the next concrete action: show the product card generator, collect a pilot brief, choose an agent, prepare lead delivery, or check launch readiness. The first product launch kit lives at /launch-kit. The machine-readable launch kit is /launch-kit.json. It contains safe first announcement copy, UTM links, the recommended traffic sequence, and do-not-publish gates for the product card generator. It should not be used for public paid promotion until product readiness, owner price confirmation, legal texts, and real lead delivery are confirmed. The product catalog lives at /products. The machine-readable catalog contract is available at /catalog-passport.json. Each product page should explain the audience, workflow, human confirmation boundary, packaging model, and contact path. The first ready product is /products/product-card-generator. The product roadmap lives at /roadmap. It explains how Nika AI expands from the product card generator into a platform: one brand face, one catalog, one lead intake path, staged marketplace expansion, future niche agents, and launch gates before paid public sales. The product card generator is the first sellable pilot product. It starts from 25,000 RUB and produces a product card structure, SEO description, benefits, visual brief, publication checklist, and missing-data prompts for marketplace sellers and product teams. The human-facing product card generator sample page lives at /products/product-card-generator/sample. The machine-readable sample output is available at /product-card-sample.json. Together they show input fields, a generated card fragment, SEO keywords, visual brief, missing-data questions, and human review checklist. The sample is illustrative and must not be treated as automatic marketplace publication. The product card generator commercial pilot offer lives at /products/product-card-generator/pilot. The machine-readable pilot contract is /product-card-pilot.json. It defines the 3-5 SKU scope, 25,000 RUB starting price, deliverables, exclusions, workflow, acceptance criteria, and owner confirmation requirements before paid public sale. The product card generator delivery acceptance page lives at /products/product-card-generator/delivery. The machine-readable delivery contract is /product-card-delivery.json. It defines what is handed off after a pilot, which roles confirm facts and visuals, acceptance statuses, handoff checklist, and the boundary between generated publication input and final marketplace publication. The product card generator pilot brief lives at /products/product-card-generator/brief. The machine-readable brief contract is /product-card-brief.json. It collects marketplace, category, SKU count, data readiness, product links, constraints, pilot goal, consent, source page, and attribution before the first product-card generator pilot. The marketplace line lives at /agents/marketplaces. It expands from the product card generator into buyer questions, reviews, documents, tables, reports, and recurring marketplace seller tasks. It should be treated as a product line that depends on the product card generator, not as an isolated chatbot. Custom development lives at /custom-agent. Use it when a business has roles, several channels, CRM or tables, internal rules, integrations, and actions that require human approval. ## Human control Nika AI does not make important financial, legal, document, client, or accounting decisions without human confirmation. The model may propose responses and extracted fields, while application code and a human operator control validation, consent, approvals, and external side effects. ## Contact Use the selection quiz on /quiz when the visitor is not sure where to start. It routes the task by need, complexity, and channel toward a ready agent, the product card generator, regular operations, documents, or custom development. Use the contact form on /contacts. The contact page helps choose between the product card generator, a ready agent, and custom development. Lead intake records the selected product or agent interest and the source page so the owner can see whether the request came from the home page, selection quiz, product catalog, product card generator, agent catalog, marketplace page, custom agent page, or another route. Lead integrations are explained on /integrations. This page describes how Nika AI lead delivery can connect to Telegram, MAX, CRM, a table, email, or an automation webhook while preserving leadId, summaryText, source page, UTM campaign labels, preferred channel, consent, and owner-only delivery settings. Valid lead API outcomes are delivered, stored_without_webhook, webhook_failed, and telegram_failed. If a webhook or Telegram delivery is not configured or fails, the visitor still receives a human-readable lead summary that can be copied and sent through Telegram, MAX, or email. Accepted lead payloads include leadId and summaryText so receiving systems can deduplicate deliveries and show the owner a readable request immediately. Webhook delivery also sends Idempotency-Key equal to leadId. The public lead payload contract is available at /lead-schema.json. It describes required fields, leadId, sourcePath, sourceUrl, referrer, UTM campaign labels, interest, preferredChannel, consentText, summaryText, receivedAt, validation errors, webhook authentication, and delivery outcomes for receiving systems. The operator lead checklist is available at /lead-ops.json. It defines the key routes to test, owner-provided environment variables, automatic delivery expectations, manual fallback, and failure handling before paid traffic. The webhook receiver contract is available at /webhook-receiver.json. It describes the POST method, required Content-Type and Idempotency-Key headers, optional Authorization header, required accepted-lead fields, successful 2xx responses, duplicate handling, and owner display rules for Telegram, CRM, table, or automation receivers. The human-facing launch readiness page is /launch-readiness. The machine-readable launch status is available at /launch-status.json. It states that the production site is deployed on agentnika.ru and lists only owner-required items: production Nika chat backend, real lead delivery channel, legal finalization, price and package confirmation, external accounts, and finishing the product card generator before paid pilot sales. SEO and generative engine readiness is described at /seo-geo.json. It lists primary entities, structured data coverage, public discovery files, live-site checks, and owner-only external submission items for Yandex Webmaster, Search Console, Yandex Business, and 2GIS. Trust files are available at /humans.txt and /security.txt. Security.txt is also mirrored at /.well-known/security.txt for standard security contact discovery. Legal and consent reference pages are /legal, /legal/offer, /legal/privacy, /legal/consent, and /legal/ai-rules. These pages contain working drafts and must be finalized for the real operator, payment model, analytics, hosting, messenger, and data-processing setup before paid launch.