Remit Rights Letter
by RemittancePulse in Documents & files
Citation-locked remittance document (Reg E Subpart B) — error notice with elected remedy and the provider's 90-day/3-day/1-day deadlines, the five-prong §1005.33(h) rebuttal to "you typed the wrong number" denials, or the 30-minute cancellation refund demand; California senders get the Fin. Code §2102 10-day-refund section. Fee-and-tax add-back computed for late/never-arrived transfers. Honest-no when the 180-day window is dead.
https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter- Price
- $2.00
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 258 ms
- 454 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter
Each call costs $2.00 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter?issue=never_arrivedParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
date_available | string | No | Disclosed Date Available (YYYY-MM-DD) |
issue | string | Yes | never_arrived | arrived_late | arrived_short | wrong_person_paid | sender_typo_number | want_to_cancel | want_documentation |
lang | string | No | Letter language (default English) |
principal | string | No | Transfer amount USD |
provider | string | No | Provider name for the letter |
remedy_choice | string | No | refund | resend (default refund) |
sender_name | string | No | Your name (placeholder if omitted) |
Example response
The listing has no example response.
Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $2.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter?issue=never_arrived'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter?issue=never_arrived' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $2 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$2" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $2 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fremittancepulse.theaslangroupllc.com%2Fapi%2Fremit%2Frights-letter
const res = await pay("https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter?issue=never_arrived");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $2 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$2"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://remittancepulse.theaslangroupllc.com/api/remit/rights-letter?issue=never_arrived")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 257 ms | $2.00 |
| 7 h ago | Passed | 402 | 261 ms | $2.00 |
| 12 h ago | Passed | 402 | 262 ms | $2.00 |
| 17 h ago | Passed | 402 | 229 ms | $2.00 |
| 23 h ago | Passed | 402 | 320 ms | $2.00 |
Show 8 older checks
| 28 h ago | Passed | 402 | 277 ms | $2.00 |
| 33 h ago | Passed | 402 | 454 ms | $2.00 |
| 38 h ago | Passed | 402 | 258 ms | $2.00 |
| 43 h ago | Passed | 402 | 202 ms | $2.00 |
| 2 days ago | Passed | 402 | 201 ms | $2.00 |
| 2 days ago | Passed | 402 | 280 ms | $2.00 |
| 2 days ago | Passed | 402 | 223 ms | $2.00 |
| 3 days ago | Passed | 402 | 245 ms | $2.00 |