Skip to content
View ApexAiOfficial's full-sized avatar

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 and business communications. Operators, software through ApexAPI, and AI agents through ApexMCP reach Scrapy and Communications, each through its own authority gate. Opening for business soon.

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

ApexAi builds guarded web-data and business communications products with operator, API, and agent interfaces. Scrapy turns web sources into owned artifacts and versioned datasets. Communications runs business conversations on your own Twilio, SendGrid, and Telegram accounts, with consent and history built in.

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.

Scrapy, web-data operations: turn web sources into owned artifacts and versioned datasets. Workflow from source to dataset: choose a cataloged source, pass the policy and egress gate, crawl, fetch, or render, classify and store artifacts, publish a dataset version, then search and fetch records.

Communications, business communications: on your own provider accounts, with consent and history built in. Workflow from intent to evidence: communication intent, workspace and role, consent and suppression, the Trust and Safety gate, the workspace provider, then delivery and history.

Public availability. Scrapy: Telegram operator, ApexAPI, ApexMCP, and Scrapy Plugin are in development. Communications: Telegram operator, Web Admin, and ApexAPI are in development; ApexMCP and the Communications / Twilio Plugin are planned. Neither 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 ships its own contracts; there is no shared gateway.

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 and business communications products for operators, software, and AI agents.

apexaiofficial.com · support@apexaiofficial.com
On Telegram: official updates · community · Scrapy bot · Communications bot

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. 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

  4. termux-kit termux-kit Public

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

    Shell

  5. termux-telegram-bot termux-telegram-bot Public

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

    Shell

  6. telegram-bot-tutorial telegram-bot-tutorial Public

    Beginner-to-deployable Telegram bot tutorial in Python with runnable examples

    Python