MacroPulse: Real-time macro intelligence for forex and CFD traders. All endpoints require x402 payment (USDC on Base mainnet) via the PAYMENT-SIGNATURE header. Coverage: Global Endpoints: • session-brief ($0.10): Forex session brief • event-pulse ($0.20): Economic event deep-dive • crypto-pulse (...
AI agents use macropulse to commit financial operations through Pulsenetwork — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
lang | string | — | Response language code (en | es | fr | de | zh | hi | ar | pt | ja | ko | etc.) |
pair | string | — | pair |
event | string | — | Economic event identifier |
action | string | Yes | Which endpoint to call. Options: session-brief | event-pulse | crypto-pulse | commodities-pulse | equities-pulse | calendar | cot | eia-inventory | intermarket |
session | string | — | Trading session. Auto-detected from UTC time if omitted. |
Parameters from the server's own tool schema.
Every invocation of this tool commits a real financial transaction, spending USDC on Base mainnet. An AI agent autonomously calling these endpoints would repeatedly spend cryptocurrency on each query, making this a Financial category tool. The blast radius is critical because an agent could rack up unbounded financial expenditure across 825 endpoints if misused or looping.
From the tool's definition 'agents pay per query via x402 USDC on Base', 'All endpoints require x402 payment (USDC on Base mainnet) via the PAYMENT-SIGNATURE header', endpoint costs listed ($0.05–$0.20 per call)
Attacks that exploit this kind of access
MacroPulse: Real-time macro intelligence for forex and CFD traders. All endpoints require x402 payment (USDC on Base mainnet) via the PAYMENT-SIGNATURE header. Coverage: Global Endpoints: • session-brief ($0.10): Forex session brief • event-pulse ($0.20): Economic event deep-dive • crypto-pulse ($0.05): Crypto market context • commodities-pulse ($0.10): Commodities brief • equities-pulse ($0.10): Equities pulse • calendar ($0.10): Weekly economic calendar • cot ($0.15): CFTC Commitment-of-Traders positioning for FX and commodity agents — institutional net positioning and weekly shifts across 7 major pairs plus gold and WTI, with crowding and contrarian signals. • eia-inventory ($0.10): Weekly EIA petroleum inventory intelligence for energy and macro agents — crude, gasoline and distillate builds and draws versus expectations, with the oil-price and CAD/NOK implications. • intermarket ($0.15): Cross-asset intermarket synthesis for macro agents — bond yields, equities, commodities and FX read together to surface the dominant regime and the divergences that tend to lead price. • rates-differential ($0.10): Interest-rate differential and carry intelligence for FX agents — G10 policy rates, yield spreads and the carry-trade map that drives durable currency trends. • regime ($0.10): Macro regime classifier for multi-asset agents — labels the current environment (risk-on/off, reflation, stagflation, tightening) and its directional implications for FX, rates and equities. • sentiment ($0.05): Real-time directional sentiment for any forex pair or gold — retail crowd positioning, COT institutional alignment, and a clear contrarian bias call. Built for FX trading and advisor agents. It is categorised as a Financial tool in the Pulsenetwork MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
macropulse accepts 5 parameters: lang, pair, event, action, session. 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 macropulse: 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.
macropulse is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the macropulse 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 macropulse. 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.
macropulse 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.
macropulse 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 →