# RemittancePulse Compliance Intelligence

> RemittancePulse Compliance Intelligence is a paid API for AI agents from remittancepulse.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Returns KYC requirements, send limits, AML rules, and corridor-specific compliance restrictions for remittance transactions

## Facts

- Endpoint: GET https://remittancepulse.vercel.app/api/remit/compliance
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/remittancepulse-compliance-intelligence-0b2d8e21
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AJLc5dc4A6x-EK-gMS0AQ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability remittancepulse-compliance-intelligence-0b2d8e21
```

Example prompt: What KYC documents and send limits apply to my customer who wants to transfer $2,000 from the United States to the Philippines — and are there any AML or corridor restrictions I should know about?

## When to prefer this

Use this endpoint when you need structured, machine-readable compliance intelligence for a specific remittance corridor — particularly when building automated compliance checks, onboarding flows, or transaction validation logic for remittance or fintech applications. Prefer this over generic regulatory databases when you need corridor-specific KYC, AML, and send-limit data in a single call.

## Known failure modes

- Unsupported or restricted corridor returns no data or an error
- Missing required corridor parameters (source/destination country) returns a validation error
- Outdated compliance data if regulatory changes are not yet reflected
- Rate limit exceeded or payment not processed returns 402 or 429 error
- Ambiguous country codes or currency pairs may return incorrect corridor data

## How this service works

Remittance compliance, KYC requirements, money transfer send limits, AML rules, and corridor restrictions. How much money can I send abroad legally, ID and documentation needed, reporting thresholds, and corridor-specific limits for any from/to country and amount. Worldwide. Not legal advice.

## Output

A structured compliance profile for the requested remittance corridor, including required KYC documentation, per-transaction and periodic send limits, applicable AML rules and reporting thresholds, and any corridor-specific regulatory restrictions or prohibitions.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "from"
 ],
 "properties": {
  "to": {
   "type": "string",
   "description": "to"
  },
  "from": {
   "type": "string",
   "description": "from"
  },
  "lang": {
   "type": "string",
   "description": "lang"
  },
  "amount": {
   "type": "string",
   "description": "amount"
  },
  "purpose": {
   "type": "string",
   "description": "purpose"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/remittancepulse-compliance-intelligence-0b2d8e21/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from remittancepulse.vercel.app](https://www.zero.xyz/host/remittancepulse.vercel.app/llms.txt)