MODULE INTEGRATION TEST HUB  ·  intergrations.anrick.ai

Test the Anrick integration fabric against your client's framework.

A live, production-grade harness to onboard, connect and verify every Anrick AI module from a client's own stack — via REST API, webhooks and n8n workflows.

Every paid module is ready the moment payment is verified: it runs on Anrick-hosted data (READY) and you call its actions with POST /api/mcp/tool. Optionally connect your own system (INTEGRATION_IN_PROGRESS → test → CONNECTED). WhatsApp Automation connects through your own Meta WhatsApp Cloud API app. Below: each module's requirements, disclaimer and full action contract, loaded live from /api/modules/catalog.

15 integration modules in the catalog
7+integration lifecycle states
REST+WHAPI & webhook bindings
n8n workflow-driven callbacks
HOW IT CONNECTS

Four layers between your framework and the live module.

The fabric is deliberately thin and transparent: every call is observable, every state is checkable, and nothing is fabricated — a module is only LIVE when the integration genuinely answers.

🛰️

Client Framework

Your app, POS, or ERP initiates. Over HTTPS.

POST /api/mcp/tool
→
🔌

Anrick API

Auth, tenant scoping, and module entitlement handled server-side.

api/anrick-mcp.mjs
→
⚙️

n8n Workflow

External hand-offs: M-Pesa STK, payment callbacks, webhook delivery.

n8n.anrick.ai/webhook/*
→
✅

Live State

Callback writes state; module flips to LIVE only on verified reality.

integration_state
MODULE CATALOG

15 modules, one contract.

Each entry below is the authoritative catalog record from the live API (GET /api/modules/catalog). Open Requirements, disclaimer & actions on any module to see what it needs before you buy and every action you can run. Filter by functional area.

loading live catalog…

INTEGRATION LIFECYCLE

From first touch to LIVE — observably.

Every module follows the same state machine. The console runs each step as a real API call, and you read the transition back.

1
Pay (M-Pesa) → PAYMENT_VERIFIEDDashboard → Billing. Until then, actions return HTTP 402 PAYMENT_REQUIRED. Billing is monthly per module (no free trial): access runs until paid_until, then returns 402 SUBSCRIPTION_EXPIRED until renewed — data is kept. Demo accounts activate modules for free with POST /api/demo/pay, which runs against the in-memory sandbox.
2
Ready on Anrick-hosted dataState READY. Nothing to install. Run any action with POST /api/mcp/tool {"module","tool","args"} and your Anrick bearer token.
3
Optional: connect your own systemPOST /api/integrations/:module/connect {"mode":"connect_own_system","service_url","token"} → INTEGRATION_IN_PROGRESS. Anrick will then call POST {service_url}/{action} (public HTTPS, 2xx JSON within 8 s). Switch back with {"mode":"hosted"}.
4
Test → CONNECTED / FAILEDPOST /api/integrations/:module/test. Hosted modules: a data round-trip check. Own system: Anrick calls the module's first read-only action on your endpoint. WhatsApp: sends an approved template to your test number.
5
LiveState LIVE. Only promoted when the integration genuinely answers. LIVE modules are protected against deletion (409 LIVE_MODULE).
LIVE TEST CONSOLE

Drive a module like a client would.

Pick a module, then run a lifecycle step or any of the module's actions. The console calls the real Anrick API and prints the actual HTTP response. Success is never mocked.

anrick_integration_fabric — live connected
demo resolves server-side from subscription_status (internal_demo/demo) and runs on an in-memory sandbox with sample data. Every module must be PAYMENT_VERIFIED before its actions run, otherwise the API returns HTTP 402 PAYMENT_REQUIRED. That is correct behaviour: demo accounts use demo: activate module first. ⚡ demo token mints a demo bearer token (fills the shared token field and localStorage) so the console works instantly. With ENVIRONMENT = production, the console uses the token from your paid-account sign-in in the WhatsApp section, if you have signed in there.
WHATSAPP AUTOMATION SETUP

Connect your own Meta WhatsApp Cloud API number.

WhatsApp works differently from the other modules. You bring your own Meta app and WhatsApp Business Account, and Anrick sends and receives through Meta's Cloud API for you. Meta bills message fees directly to you. Setup needs a paid WhatsApp Automation module and the Meta prerequisites below.

whatsapp::integrations/whatsapp — Meta Cloud API meta
Paste both, click “Verify and save”, then subscribe to the messages field.
Free text only works within 24 h of the customer's last message. After that, send an approved template with send_notification and template:{name,language,params}. Credentials are encrypted and never shown again; only the verify token is shown again, and only to you.
LIVE DEMO — INVOICING MODULE

Create a branded, AI-refined invoice, in demo mode, free.

This runs against the live Anrick API. The demo environment (demo@anrick.ai) is resolved server-side, so it's free: no payment gate, no production integration, and demo invoices are never emailed. Anrick automatically pulls the tenant's business profile (logo / business name / tax ID) and the Groq AI rewrites your rough line descriptions into professional invoice copy — without ever touching the amounts.

invoicing::invoices/ai — branded + AI groq
One click signs into the internal_demo account server-side and fills the token above — no password needed, no copy-paste. Demo-scoped: safe for live demos (cannot bill or touch production data). Valid 24h.
Alternatively, run once on any machine with curl (own account or demo password): curl -s -X POST https://anrick.ai/api/login -H "Content-Type: application/json" -d '{"email":"YOUR_EMAIL","password":"YOUR_PASSWORD"}'
...or skip it entirely with the ⚡ Get demo token button above. Token lives only in this browser tab (localStorage), valid 24h. Uses POST /api/invoices/ai → returns a persisted invoice (environment:"demo") plus a branded HTML doc rendered live below. Groq refines wording; amounts are preserved exactly and never invented. With a demo token, send_email returns email.skipped = "DEMO_NO_EMAIL": nothing is emailed.
⤵ BRANDED INVOICE PREVIEW generated from the business profile + AI line refinement
API SURFACE

Bind these from your client framework.

The same surface the console uses. All responses are tenant-scoped and JWT-protected where marked.

ENDPOINTMETHODPURPOSEAUTH
GET /api/modules/catalogGETPublic catalog: every module's requirements, disclaimer, modes and action contract.none
POST /api/loginPOSTGet a bearer token (valid 24 h).email + password
POST /api/mcp/toolPOSTRun a module action: {"module","tool","args"}. Hosted, own-system or demo sandbox. 402 PAYMENT_REQUIRED if the module isn't activated.Bearer
GET /api/integrations/:moduleGETMode, payment/integration state, requirements, guidance (WhatsApp: webhook details).Bearer
POST /api/integrations/:module/connectPOST{"mode":"hosted"} · {"mode":"connect_own_system","service_url","token","display_name"} · WhatsApp: {"waba_id","phone_number_id","access_token","app_secret"}.Bearer
POST /api/integrations/:module/testPOSTTest the integration (WhatsApp: {"test_to","template","language"}).Bearer
POST /api/integrations/whatsapp/settingsPOST{"auto_reply": true|false}.Bearer
POST {service_url}/{action}POSTWhat Anrick calls on your system when connected: JSON args + Authorization: Bearer <your token>, X-Anrick-Client, X-Anrick-Module, X-Anrick-Tool. Reply 2xx JSON within 8 s.your token
PUT /api/module-config/:modulePUTActivate / configure a module.Bearer
GET /api/module-config/:moduleGETInspect current config + integration_state.Bearer
POST /webhook/mpesa/stk-pushPOSTInitiate M-Pesa STK push via n8n (Daraja live).n8n
GET /api/invoicesGETTenant's own invoice rows (production persistence).Bearer
GET /api/export?format=GETTenant-scoped export (JSON / CSV).Bearer