Observe
See operating state
Health and readiness of the product and everything it depends on, with alerts when something degrades.
Product plugins / operators
Operator control for the product you run.
A product plugin gives the people responsible for a Scrawl or Communications deployment one place to see its health, prove it works, correct it with approval, and keep evidence of every step.
What a plugin is for
Different caller, different job.
ApexAPI and ApexMCP let software and agents use a product. A product plugin serves the operator whose job is to keep that product working.
| Surface | Caller | What it is for |
|---|---|---|
| ApexAPI | Software | An application does product work: submit jobs, send communications, read results. |
| ApexMCP | AI agents | An agent discovers, inspects, retrieves, and takes named actions inside the product. |
| Product plugin | Operators | The people responsible for a deployment keep it healthy, verified, and correctable. |
Capability families
Observe, verify, control, record.
Every product plugin offers the same four kinds of operator control. What each one checks and changes is defined by its product.
product identity + policy→operator control→evidence + bounded action
Verify
Prove it works
Registered smoke tests and checks that exercise the real product path, plus the identity of what is deployed.
Control
Correct, with approval
Maintenance actions the product defines and bounds, gated by product permissions and explicit approvals.
Record
Leave evidence
Redacted diagnostics, action outcomes, and an operator-visible history of what was checked and changed.
Public plugins
Two products, two plugins.
Each plugin speaks its own product's language: crawlers, proxies, and datasets for Scrawl; providers, webhooks, and consent for Communications.
Web-data operationsIn development
Scrawl Plugin
Operator control attached to Scrawl's crawlers, jobs, proxies, artifacts, datasets, and deployment identity.
- Observe
- Product and crawler health · Proxy pool readiness · Job and queue health · Alerts on degraded state
- Verify
- Registered smoke tests · Artifact, storage, and dataset checks · Deployment and version identity
- Control
- Approvals for operator actions · Bounded maintenance and cleanup
- Record
- Redacted diagnostics · Evidence for every check and action
Business communicationsPlanned
Communications / Twilio Plugin
Operator control for Communications and the provider accounts it runs on: Twilio, SendGrid, and Telegram, plus the support backlog they carry.
- Observe
- Provider readiness · Webhook and delivery health · Queue, worker, and dead-letter state · Support backlog and stuck replies · Operator alerts
- Verify
- Delivery smoke tests · Credential-vault and storage checks · Consent, suppression, and limit checks
- Control
- Approvals for operator actions · Bounded, product-defined maintenance
- Record
- Diagnostics and delivery evidence · Action outcomes and history
Operator workflow
From an alert to a recorded outcome.
A typical correction loop. Reading and verifying never change the product; the one maintenance step waits for approval and is limited to actions the product defines.
- 01Alert or scheduled check
- 02Read health and readiness
- 03Run a smoke test
- 04Review redacted evidence
- 05Approve bounded maintenance
- 06Record the outcome
Where DevOps fits
A plugin looks after its product. DevOps is a product.
A product plugin keeps one ApexAi product's deployment healthy, with an operator in the loop. DevOps is a separate product that supervises and corrects the systems a customer connects, so there is no plugin for it.
| Question | Product plugin | DevOps |
|---|---|---|
| What it looks after | One ApexAi product's deployment: Scrawl or Communications. | The systems a customer connects to the DevOps service. |
| Who acts | An operator, with explicit approval for maintenance. | The controller, within standing policy, escalating to a person when no allowed remedy fits. |
| How a fix is proven | Smoke tests and checks an operator runs and reviews. | A fresh observation after every change, then a stability window. |
| How it is offered | As part of its product. | As its own product, planned as a managed service. |
Authority
A plugin carries its product's authority—no more.
A plugin asks its product for state and uses operations the product defines, under the product's own permissions. It is not a general shell, an infrastructure console, or a way to act across products.
Commercial access follows each product's offering. There is no separate subscription for ApexAPI, ApexMCP, or a product plugin; details arrive with product pricing.