API + MCP
Query Pulse intelligence from your own workflow.
Salubrum gives agencies, activation partners, and AI systems a direct path to Pulse outputs. Query audiences, target lists, readiness signals, and predictions, then execute through your own tools.
API
Agency or platform system
Pull audiences and readiness signals into your own workflow.
MCP
Your agent
Your agents ping Pulse for healthcare intelligence.
Two access layers
API for your systems. MCP for your agents.
Two programmatic paths into the same intelligence layer, built for firms that want Pulse outputs while owning execution themselves.
API
Data access
Query Pulse for audiences, target lists, readiness signals, and category intelligence your team can use in its own activation workflow.
MCP
Agent access
Give your own agents a governed path to Pulse intelligence for campaign planning, audience decisions, and optimization workflows.
Use cases
Built for firms that bring their own execution.
API and MCP access is for teams that want Salubrum intelligence as the data layer, while their own people, tools, or agents run the work.
Healthcare agencies
Use Pulse audiences and readiness signals while your agency owns strategy, execution, and client relationships.
Activation partners
Pull Healthcare Consumer intelligence into the planning, buying, and measurement systems your team already operates.
Enterprise AI teams
Let internal agents query Pulse as a healthcare intelligence source while execution stays inside your own environment.
How it works
Request, infer, return, learn.
A clean path from request to intelligence, built for healthcare products and AI workflows.
01
Query
Your system requests intelligence for a population, market, category, or decision moment.
02
Infer
Pulse interprets behavioral signals, readiness, demand, and approaching care decision windows.
03
Return
The API or MCP layer returns audiences, target lists, predictions, or next action intelligence.
04
Execute
Your team or system runs the campaign, workflow, or analysis inside its own execution stack.
Infrastructure posture
One intelligence layer, multiple routes into it.
Pulse remains the intelligence model. API and MCP give agencies, activation partners, and AI systems clean ways to query it.
Pulse remains the underlying model.
API and MCP expose that intelligence to teams and systems that own execution.
Built for privacy-safe intelligence rather than exposing raw Healthcare Consumer records.
The Healthcare Consumer universe is refreshed every 36 hours.
Product paths
Need a different path into Pulse?
Use API + MCP when your team wants Pulse outputs and owns execution. Explore other paths when you want a workspace, managed operation, or embedded partner product.
Bring Pulse into your own execution stack.
Use API and MCP access to query healthcare audience intelligence while your team, platform, or agent handles execution.