Skip to content
View ApexAiOfficial's full-sized avatar
6 followers · 17 following

Achievements

Achievement: Pair Extraordinairex3Achievement: Pull Sharkx3Achievement: QuickdrawAchievement: YOLO

Achievements

Achievement: Pair Extraordinairex3Achievement: Pull Sharkx3Achievement: QuickdrawAchievement: YOLO

Block or report ApexAiOfficial

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
ApexAiOfficial/README.md

ApexAi: web data, communications, operations, and commerce. Operators, software through ApexAPI, and AI agents through ApexMCP reach Scrawl, Communications, DevOps, and Shop Bot, each through its own authority gate; DevOps access through ApexAPI and ApexMCP is planned, and Shop Bot is used in Telegram only. Opening for business soon.

Visit apexaiofficial.com Follow launch updates on Telegram Follow ApexAi on Facebook Request a custom build

ApexAi builds guarded products for web data, business communications, autonomous operations, and Telegram commerce, with operator, API, and agent interfaces. Scrawl turns web pages into clean, versioned data you own and can cite, with crawling built on Scrapy and extraction on the AI provider you bring. Communications is one support inbox for SMS, WhatsApp, and Telegram on your own Twilio, SendGrid, and Telegram accounts, with consent and audit built in. DevOps corrects failures in the systems a customer connects, using only actions the customer allows, and proves each fix by observing the system again; its engine is in development and the managed service is planned. Shop Bot sells digital products inside Telegram: customers pay in Telegram Stars and receive files, license keys, and memberships once per payment, with every charge on a ledger and a dedicated instance for each merchant; it is built, and a managed white-label service is in development.

Each product owns its rules. A person working in Telegram, an application calling ApexAPI, and an AI agent using ApexMCP all pass the same product policy before anything runs, and all get evidence back. DevOps will be reached the same way, but its ApexAPI and ApexMCP access is planned, not available yet. Shop Bot is used in Telegram only.

Scrawl and DevOps also publish developer kits, collected in ApexSDK: Scrawl's Python and TypeScript SDKs, command-line tool, and agent plugin for Claude Code and OpenAI Codex, and DevOps' integration SDK and read-only agent plugin for Claude Code. Each kit belongs to one product and talks only to that product. An agent plugin brings a product into an AI coding agent; it is not a product plugin, which is an operator surface of the product itself.

No product is generally released yet: none has a public sign-up, hosted service, or price. The developer kits are open source on GitHub, but none is on a package registry or in an official plugin directory yet, and each works only with its product as an ApexAi-operated service, which is not offered publicly yet.

Scrawl, web-data operations: turn web pages into clean, versioned data you own and can cite. Workflow from a URL to structured data: send a URL and a schema, pass the egress gate, fetch the page once, convert to Markdown, extract with your AI, then validate against the schema.

Communications, customer support and business messaging: one support inbox for SMS, WhatsApp, and Telegram, on your own provider accounts. Workflow for a support conversation: the customer writes in, the conversation opens or reopens, a teammate or automation answers, the consent and Trust and Safety gate, the reply goes out from the number they wrote to, then the reply and its provenance are kept in history.

DevOps, autonomous operations: find what broke, fix it within the authority you grant, and prove the fix held. Workflow from incident to verified resolution: a declared condition fails, one incident is opened, an allowed remedy is selected, a single-use grant is issued, the action runs within its bound, a fresh verification, the stability window holds, then it is closed with evidence. Engine in development; managed service planned.

Shop Bot, digital commerce on Telegram: sell digital products inside Telegram, paid in Stars and delivered once per payment. Workflow from order to delivery: the customer checks out, a signed Stars invoice, the pre-checkout check, Telegram charges Stars, the receipt is recorded on the ledger, then files and keys are delivered. Built; managed white-label service in development, with no sign-up, plan, or price yet.

Public availability. Scrawl: Telegram operator, ApexAPI, ApexMCP, SDK, and agent plugin are built, and its product plugin for operators, the Scrawl Plugin, is in development. Communications: Telegram operator, web console, ApexAPI, and ApexMCP are built, and its product plugin, the Communications / Twilio Plugin, is planned; it has no SDK or agent plugin. DevOps: the operations engine, SDK, and agent plugin are in development, and ApexAPI and ApexMCP access are planned; it has no product plugin. Shop Bot: the Telegram operator surface is built; it has no ApexAPI, ApexMCP, SDK, agent plugin, or product plugin surface. The managed Shop Bot service is in development, and the managed DevOps service is planned. No product is publicly hosted yet.

Access layers. ApexAPI: typed HTTP for applications. ApexMCP: tools and resources for AI agents. Product plugins: operator control with approvals and evidence. Each product owns its contracts, and there is no shared gateway. DevOps access through ApexAPI and ApexMCP is planned; Shop Bot is used in Telegram only.

Developer kits. ApexSDK: SDKs and agent plugins for Scrawl and DevOps. Each kit belongs to one product and talks only to that product. All four are open source on GitHub under the Apache License 2.0, and none is on a package registry or in an official plugin directory yet. Each works only with its product as an ApexAi-operated service, which is not offered publicly yet.

scrawl-sdk: Python and TypeScript SDKs and a command-line tool that call Scrawl's ApexAPI. Open source, not on PyPI or npm yet; it works only with Scrawl as a service ApexAi operates, which is not publicly hosted yet. scrawl-plugin: Scrawl's agent plugin for Claude Code and OpenAI Codex. Open source, not in an official plugin directory yet; it works only with Scrawl as a service ApexAi operates, which is not publicly hosted yet. devops-sdk: an integration SDK for connecting your systems to the DevOps engine. Open source, not on PyPI yet; the DevOps engine runs only in environments ApexAi operates, is in development, and is not distributed. devops-plugin: read-only inspection of a DevOps engine installation from Claude Code. Open source, not in an official plugin directory yet; it works only where ApexAi operates the DevOps engine, which is in development and not distributed.

Custom orders: bespoke software, scoped before it is built. Telegram and messaging, communications automation, web data, integrations and APIs, agents and AI tooling, and operations and control.

Open source from ApexAi: guides, kits, and tools you can use today.

privacy-chain: a guide to how online identity leaks across devices, networks, browsers, and accounts, and the controls that reduce it. telegram-bot-tutorial: build a Telegram bot in Python from zero to deployed. termux-kit: turn Android Termux into a practical workbench. termux-telegram-bot: deploy and operate one Python Telegram bot on Android Termux. cookie-manager: inspect, export, and replay browser cookies you control. All ApexAi public repositories

ApexAi: web-data, business communications, autonomous operations, and Telegram commerce products for operators, software, and AI agents.

apexaiofficial.com
Sales: sales@apexaiofficial.com
Support: support@apexaiofficial.com
Direct: @ApexAiAdmin on Telegram
On Telegram: official updates · community
On Facebook: @ApexAiOfficial

Popular repositories Loading

  1. ytdlnis ytdlnis Public

    Forked from deniscerri/ytdlnis

    Unmodified fork of deniscerri/ytdlnis. No changes are published here; see upstream for the current app.

    Kotlin

  2. git-sms git-sms Public

    Forked from github/git-sms

    Contribution fork of github/git-sms. Branch revival/pr-1-restore-prototype restores the SMS prototype with regression tests and CI, proposed upstream in github/git-sms#1.

    Python

  3. ua-rotator ua-rotator Public

    Framework-agnostic weighted User-Agent rotation with an optional Scrapy adapter

    Python

  4. DeepSeek-Reasonix DeepSeek-Reasonix Public

    Forked from esengine/DeepSeek-Reasonix

    Fork of esengine/DeepSeek-Reasonix (main-v2) with one change: sha256sum -c manifest checks now count as delivery verification in the evidence gate. Otherwise identical to upstream main-v2.

    Go

  5. termux-kit termux-kit Public

    Practical Termux foundation for Android: local services, dev stack, helper scripts, and safe backups

    Shell

  6. termux-telegram-bot termux-telegram-bot Public

    Deploy and operate a single Python Telegram bot on Android Termux with strict token safety

    Shell