RemittancePulse: Global remittance intelligence API covering the $700B+ annual global remittance market. 8 endpoints: corridor analysis (200+ corridors), provider comparison with true total cost (fee + FX markup), liv Coverage: Global Endpoints: • corridor ($0.08): Corridor intelligence • compare...
AI agents use remittancepulse 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 |
|---|---|---|---|
to | string | — | Receiving country — e.g. Philippines, India, Mexico, Nigeria, Bangladesh |
from | string | — | Sending country — e.g. USA, UAE, UK, Canada, Germany |
lang | string | — | lang |
issue | string | — | issue |
topic | string | — | regulatory | providers | fees | technology | all |
action | string | Yes | Which endpoint to call. Options: corridor | compare | rate | receive | mobile | compliance | news | diaspora | stablecoin-rails | rights | rights-letter |
amount | string | — | Amount to send in source currency |
method | string | — | bank | cash | mobile | wallet — or omit for all methods |
region | string | — | East Africa | West Africa | South Asia | Southeast Asia | Latin America | Middle East |
country | string | — | country |
purpose | string | — | purpose |
platform | string | — | Specific platform — e.g. M-Pesa, GCash, bKash |
Parameters from the server's own tool schema.
This tool operates in the financial domain — remittances involve moving money across borders — and each query incurs a real USDC payment on Base blockchain. While the tool appears primarily to provide intelligence/data about remittance corridors and providers rather than directly executing transfers, it commits financial obligations (USDC payments per query) and provides data that directly facilitates financial…
From the tool's definition 'Global remittance intelligence API covering the $700B+ annual global remittance market', 'agents pay per query via x402 USDC on Base', endpoints include 'Provider comparison with true total cost (fee + FX markup)', 'corridor analysis', 'FX rate and markup…
Risk signalsHigh parameter count (42 properties)
Attacks that exploit this kind of access
RemittancePulse: Global remittance intelligence API covering the $700B+ annual global remittance market. 8 endpoints: corridor analysis (200+ corridors), provider comparison with true total cost (fee + FX markup), liv Coverage: Global Endpoints: • corridor ($0.08): Corridor intelligence • compare ($0.10): Provider comparison • rate ($0.05): FX rate and markup analysis • receive ($0.08): Receive-country guide • mobile ($0.08): Mobile money ecosystem • compliance ($0.10): Compliance and KYC intelligence • news ($0.08): Remittance industry news • diaspora ($0.10): Diaspora community intelligence • stablecoin-rails ($0.12): Stablecoin remittance rail comparison • rights ($0.10): Remittance-transfer rights check (Reg E Subpart B) — deterministic, no LLM • rights-letter ($2.00): Citation-locked remittance document — error notice / §1005.33(h) rebuttal / cancellation demand ($2). 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.
remittancepulse accepts 12 parameters: to, from, lang, issue, topic, action, amount, method, region, country, purpose, platform. 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 remittancepulse: 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.
remittancepulse 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 remittancepulse 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 remittancepulse. 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.
remittancepulse 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.
remittancepulse 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 →