Documentation

Runink PULSE (the Prescriptive Unified Lead & Social Engine) is Runink’s marketing-analysis application. You give it a website. It audits the site, writes a multichannel diagnosis, and turns that diagnosis into a working plan: draft content waiting for approval, a draft campaign, a 30-day follow-up cycle, market research, audience profiles, and leads.

Every AI step runs on the platform’s own inference server (mistral.rs’s mistralrs-server). PULSE calls no third-party LLM API.

What PULSE is, and what it is not

PULSE is application code only: a Go gRPC backend (grpc/) and a Flutter client (flutter/) for web, Linux, and Android. The platform around it lives in other Runink repositories:

• CORE runs the deploy and dev loop (the core CLI), the operator that reconciles a PULSE instance, the shared model weights, and the native inference builds.
• The extracted libraries security, mesh, inference, store, and ui supply authentication, interceptors and self-healing, the inference engine wrappers, persistence, and the shared Billing, Profile, Admin, and Data sources pages.

The API is gRPC. Browsers reach it over gRPC-Web on the same port. There is no REST API for campaigns, content, or leads. A few plain HTTP endpoints exist (health, sign-in, media, voice, the podcast feed, A2A); the API reference lists every one.

Quick reference