ApexAi
Contact

Opening soon

ApexAi is opening for business soon.

Scrawl and Communications are in development with their core capabilities built, and Shop Bot is built with its managed service in development; the DevOps engine is in development, and the managed DevOps service is planned. Sign-up, hosted access, and pricing open at launch.

Follow launch updates Request a custom build

ApexAi · operating products

Web data, communications, operations, and commerce.

Four products that do real operating work: turning web pages into data you can cite, answering customers as a team on your own provider accounts, keeping systems in their intended state, and selling digital products inside Telegram. People operate all four; Scrawl, Communications, and DevOps are also built for software that integrates through ApexAPI and AI agents that act through ApexMCP.

Explore the products Ask about access

Products

Four products, four operating jobs.

Each is an independent product with its own deployment, identity, and policy, and each page opens with a worked example of what it does.

DATA · Web-data operations

Scrawl

Turn web pages into clean, versioned data you own and can cite.

Collect web content reliably and keep what was collected: the files, the records, and the evidence of how they were produced.

In developmentNot publicly hostedPricing coming soon

Explore Scrawl See it work
URL to structured data
  1. 01Send a URL and a schema
  2. 02Pass the egress gate
  3. 03Fetch the page once
  4. 04Convert to Markdown
  5. 05Extract with your AI
  6. 06Validate against the schema
  • One call, usable content
  • Your AI, governed
  • Versioned datasets
  • Jobs that finish once
  • Artifacts and media
  • Your proxies, explicit egress

COMMS · Customer support and business messaging

Communications

One support inbox for SMS, WhatsApp, and Telegram, on your own provider accounts.

Answer and reach customers on the right channel, with permission, and know afterward exactly what was sent, what came back, who wrote it, and why each send was allowed.

In developmentNot publicly hostedPricing coming soon

Explore Communications See it work
Support conversation
  1. 01Customer writes in
  2. 02Conversation opened or reopened
  3. 03Teammate or automation answers
  4. 04Consent and Trust and Safety gate
  5. 05Sent from the number they wrote to
  6. 06Reply and provenance in history
  • A shared support inbox
  • Three conversation channels, one inbox
  • Your providers, set up for you
  • Your team, wherever it works
  • Contacts, consent, suppression
  • Trust, history, and audit

OPS · Autonomous operations

DevOps

Find what broke, fix it within the authority you grant, and prove the fix held.

Keep systems in their intended state without giving automation open-ended power: notice what is wrong, apply only a remedy that is allowed, and call it fixed only when a fresh observation shows that it is.

EngineIn developmentServicePlannedNot yet priced

Explore DevOps See it work
Incident to verified resolution
  1. 01Declared condition fails
  2. 02One incident opened
  3. 03Allowed remedy selected
  4. 04Single-use grant issued
  5. 05Action run within its bound
  6. 06Fresh verification
  7. 07Stability window held
  8. 08Closed with evidence
  • Detection with one identity per incident
  • Remedies in a fixed order
  • Authorized, bounded execution
  • Verification by observation
  • Rollback, compensation, escalation
  • Supervision that survives restarts

SHOP · Digital commerce on Telegram

Shop Bot

Sell digital products inside Telegram, paid in Stars and delivered once per payment.

Sell digital products where customers already are, take payment in Telegram Stars, and deliver exactly what was paid for, once, with a record of every charge, delivery, and refund.

BuiltNot publicly hostedNot yet priced

Explore Shop Bot See it work
Order to delivery
  1. 01Customer checks out
  2. 02Signed Stars invoice
  3. 03Pre-checkout check
  4. 04Telegram charges Stars
  5. 05Receipt on the ledger
  6. 06Files and keys delivered
  • A store inside Telegram
  • Stars payments on a ledger
  • Delivery on payment
  • Memberships
  • Refunds that revoke access
  • Run the store from Telegram

How the products are built

Every caller passes the product's own gate.

People, software, and agents reach each product through its own authority gate, then execution, then evidence. Select a caller to trace its routes.

Authority path

Select a caller to trace its route

DATAWeb-data operations

Scrawl

Authority
identityownershiptargetegress
Execution
scrapemapcrawlextract
Evidence
artifactsdataset versions

PluginScrawl Plugin

COMMSCustomer support and business messaging

Communications

Authority
workspaceconsenttrust and safety
Execution
SMSWhatsAppTelegramemail
Evidence
conversationsdelivery stateaudit

PluginCommunications / Twilio Pluginplanned

OPSAutonomous operations

DevOps

Authority
policygrantfence
Execution
remedyrollbackcompensation
Evidence
verificationaudit

SHOPDigital commerce on Telegram

Shop Bot

Authority
signed invoicepre-checkoutstaff role
Execution
checkoutdeliveryrefund
Evidence
Stars ledgeraudit
Each product owns its gate. Every caller—person, software, or agent—passes the same product policy before execution and gets evidence back.in the productplanned

How the products are operated

Three kinds of caller. One product in charge.

Choose the surface by who is calling. Software and agents get product-specific contracts; operators get the controls their product defines.

HTTP · software

ApexAPI

Typed, scoped HTTP contracts for applications that submit work, send communications, answer support conversations, and read results.

Scrawl contractPOST /v1/scrape

Explore software access

MCP · agents

ApexMCP

Product-native tools and resources that let agents inspect work and retrieve data without a raw terminal.

Scrawl toolsscrape · ask · fetch

Explore agent access

Human · operators

Operator surfaces

The Communications web console and its shared inbox, Telegram for work on the move and for running a Shop Bot store, and product plugins for Scrawl and Communications deployments, in development and planned.

Operator surfacesinbox · Telegram · plugins

Explore product plugins

Building in code, or with an AI coding agent? Scrawl and DevOps have open-source SDKs and agent plugins on GitHub; each needs its product, which is not publicly offered yet. See ApexSDK

Custom builds

Need something outside the packaged products?

Submit a project for review. ApexAi considers bespoke bots, integrations, automation, and agent tooling close to what it builds in its products, and scopes each request individually before anything is agreed.

Request a custom build
  • MSGTelegram and messagingTelegram bots · Telegram Business workflows
  • COMCommunications automationTwilio integrations · Email and provider integrations
  • WEBWeb dataScraping and crawling systems · Extraction pipelines
  • INTIntegrations and APIsAPI integrations · Connecting existing services
  • AGTAgents and AI toolingMCP servers and agent integrations · AI-assisted operator tooling
  • OPSOperations and controlAdmin and control surfaces · Business process automation

Next step

Bring the operating problem you want solved.

Contact ApexAi Request a custom build

Launch news: ApexAi Official · Discussion: ApexAi Central

ApexAi
Contact