Retrieve historical exchange rates for 150+ currencies via pay-per-call MPP endpoint.
What it does
This MPP endpoint returns historical foreign-exchange rates for a given base currency and date. It is part of the Abstract Exchange Rates service hosted on the Locus MPP gateway, which also offers live rates and currency conversion endpoints. The service covers 150+ currencies.
To call the historical rates endpoint, send a POST request with a JSON body containing a required `base` currency code (e.g. "USD"), a required `date` in YYYY-MM-DD format, and an optional `target` currency code to narrow results to a single pair. Payment is settled per-call via the Tempo method (pathUSD on Tempo L2) at 6,000 base units, which equals $0.006 per request (pathUSD uses 6 decimals).
The probe returned 404 on HEAD/GET because this endpoint only accepts POST requests. The OpenAPI spec clearly defines the POST method with a full request schema and payment metadata, so the endpoint is expected to be live when called correctly with the proper HTTP method and payment headers.
Capabilities
Use cases
- —Fetching exchange rates for a specific past date to reconcile financial records
- —Building historical currency charts or trend analysis dashboards
- —Back-testing trading strategies with historical FX data
- —Calculating past-date invoice amounts in a different currency
Fit
Best for
- —Agents needing on-demand historical FX rates without API key management
- —Micro-payment workflows where per-call billing at $0.006 is economical
- —Applications requiring rates for 150+ currencies on arbitrary past dates
Not for
- —Streaming or real-time tick-level FX data (this is a request/response endpoint)
- —Free or bulk historical data downloads (each call costs $0.006)
Quick start
curl -X POST https://abstract-exchange-rates.mpp.paywithlocus.com/abstract-exchange-rates/historical \
-H "Content-Type: application/json" \
-d '{"base": "USD", "date": "2024-01-15", "target": "EUR"}'Example
Request
{
"base": "USD",
"date": "2024-01-15",
"target": "EUR"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema, pricing metadata, and endpoint structure. However, no response schema or example response is documented, the probe did not capture a 402 challenge (endpoint is POST-only and was probed with HEAD/GET), and crawled pages returned only generic 404 JSON. Docs are referenced but not crawled.
Warnings
- —Probe returned 404 because HEAD/GET were used; endpoint requires POST — liveness not directly confirmed by probe
- —No response schema or example response available in the OpenAPI spec
- —Referenced documentation pages (abstractapi.com, docs.abstractapi.com, beta.paywithlocus.com) were not crawled so feature details are inferred from the spec alone
- —Currency token address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo convention
Citations
- —The endpoint accepts POST with base (required), date (required), and optional target parametershttps://abstract-exchange-rates.mpp.paywithlocus.com
- —Payment is 6000 base units via Tempo method with currency 0x20c000000000000000000000b9537d11c60e8b50https://abstract-exchange-rates.mpp.paywithlocus.com
- —The service covers 150+ currencies with live, historical, and conversion endpointshttps://abstract-exchange-rates.mpp.paywithlocus.com
- —API reference docs are at https://docs.abstractapi.com/exchange-rateshttps://abstract-exchange-rates.mpp.paywithlocus.com