Rate
by LatAm Official FX in Markets & finance
Official central-bank exchange rate for one Latin American currency against USD (BRL PTAX, ARS BCRA, COP TRM, PEN BCRP, MXN FIX), with source, date and staleness flag.
https://latam-fx.latamfx.workers.dev/v1/rate/:var1- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 1 h ago, next any minute now
Reliability
Latest check failed 1 h ago: Expected HTTP 402, got 400
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://latam-fx.latamfx.workers.dev/v1/rate/:var1
Each call costs $0.002 in USDC on Base, 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://latam-fx.latamfx.workers.dev/v1/rate/:var1Example response
The provider's example. We can't check it without paying.
{
"ageDays": 1,
"currency": "BRL",
"date": "2026-10-14",
"perUsd": 5.4321,
"rateType": "PTAX (venda)",
"source": "Banco Central do Brasil",
"sourceUrl": "https://olinda.bcb.gov.br/olinda/servico/PTAX/versao/v1/aplicacao",
"stale": false
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.002.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://latam-fx.latamfx.workers.dev/v1/rate/:var1'
# 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://latam-fx.latamfx.workers.dev/v1/rate/:var1' \
| 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 $0.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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 $0.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Flatam-fx.latamfx.workers.dev%2Fv1%2Frate%2F%3Avar1
const res = await pay("https://latam-fx.latamfx.workers.dev/v1/rate/:var1");
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 $0.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://latam-fx.latamfx.workers.dev/v1/rate/:var1")
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 |
|---|---|---|---|---|
| 1 h ago | Expected HTTP 402, got 400 | 400 | 224 ms | - |
| 7 h ago | Expected HTTP 402, got 400 | 400 | 190 ms | - |
| 13 h ago | Expected HTTP 402, got 400 | 400 | 320 ms | - |
| 19 h ago | Expected HTTP 402, got 400 | 400 | 165 ms | - |
| 24 h ago | Expected HTTP 402, got 400 | 400 | 331 ms | - |
Show 10 older checks
| 30 h ago | Expected HTTP 402, got 400 | 400 | 235 ms | - |
| 35 h ago | Expected HTTP 402, got 400 | 400 | 218 ms | - |
| 41 h ago | Expected HTTP 402, got 400 | 400 | 188 ms | - |
| 46 h ago | Expected HTTP 402, got 400 | 400 | 192 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 267 ms | - |
| 2 days ago | Expected HTTP 402, got 400 | 400 | 234 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 282 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 160 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 220 ms | - |
| 3 days ago | Expected HTTP 402, got 400 | 400 | 228 ms | - |