MarketPulse: Marketing intelligence API for the AI era. LLM visibility, channel mix, content briefs, ad copy, local SEO, email sequences, competitor gap analysis, social strategy, ROI forecasting, and technical SE Coverage: Global Endpoints: • llm-visibility ($0.15): LLM visibility analysis • con...
AI agents call marketpulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
goal | string | — | What the content should accomplish |
lang | string | — | Language to respond in — defaults to English |
brand | string | — | The brand to assess AI-answer visibility for — provide brand and/or topic |
goals | string | — | Primary marketing goal to optimize the mix around |
stage | string | — | Business stage — startup, growth, or scale |
topic | string | — | The topic or category to assess AI visibility within — provide brand and/or topic |
action | string | Yes | Which endpoint to call. Options: llm-visibility | content-brief | channel-mix | roi-forecast | competitor-gap | ad-copy | email-sequence | social-strategy | loc |
budget | string | — | Monthly marketing budget, with currency and period |
product | string | — | The product or service being advertised |
website | string | — | The website domain to review |
audience | string | — | Who this content is written for — sharpens tone and structure |
business | string | — | The type of business to build a local SEO plan for |
Parameters from the server's own tool schema.
This is a read-only intelligence/analytics API. All endpoints return data-driven insights (visibility, forecasts, analysis, copy recommendations) without side effects. The per-query USDC payment model indicates metered access to data retrieval, not state-changing operations. No data is modified, deleted, or executed; only marketing intelligence is surfaced to inform decision-making.
From the tool's definition MarketPulse endpoints are all informational queries: 'LLM visibility analysis', 'content brief', 'channel mix strategy', 'ROI forecast', 'competitor gap analysis', 'ad copy variants', 'email sequence'.
Risk signalsHigh parameter count (19 properties)
Attacks that exploit this kind of access
MarketPulse: Marketing intelligence API for the AI era. LLM visibility, channel mix, content briefs, ad copy, local SEO, email sequences, competitor gap analysis, social strategy, ROI forecasting, and technical SE Coverage: Global Endpoints: • llm-visibility ($0.15): LLM visibility analysis • content-brief ($0.15): Dual-optimized content brief • channel-mix ($0.10): Marketing channel mix strategy • roi-forecast ($0.08): Marketing ROI forecast • competitor-gap ($0.10): Competitor gap analysis • ad-copy ($0.08): Ready-to-use ad copy variants • email-sequence ($0.15): Email nurture sequence • social-strategy ($0.08): Platform social media strategy • local-seo ($0.08): Local SEO optimization guide • seo-audit ($0.10): Technical SEO review • seo-review ($0.10): Technical SEO review. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.
marketpulse accepts 12 parameters: goal, lang, brand, goals, stage, topic, action, budget, product, website, audience, business. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Pulsenetwork MCP server in PolicyLayer and add a rule for marketpulse: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulsenetwork. Nothing to install.
marketpulse is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the marketpulse rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for marketpulse. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
marketpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
marketpulse is one line of Pulsenetwork's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →