Contract
{
"type": "object",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Target currency (e.g. USD)"
},
"from": {
"type": "string",
"description": "Source currency (e.g. EUR)"
},
"end_date": {
"type": "string"
},
"start_date": {
"type": "string"
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"max": {
"type": "number"
},
"min": {
"type": "number"
},
"rates": {
"type": "array",
"items": {
"type": "object",
"properties": {
"date": {
"type": "string",
"description": "'YYYY-MM-DD'."
},
"rate": {
"type": "number"
}
},
"additionalProperties": true
},
"description": "One entry per trading day with a published rate. Observed 6 entries for a 7-calendar-day request (weekend/holiday gaps skipped) and 22 entries for the endpoint's own default ~1-month range -- day count is not guaranteed to match the calendar span requested."
},
"average": {
"type": "number",
"description": "Mean rate across all returned days."
},
"end_date": {
"type": "string",
"description": "End of the date range covered, 'YYYY-MM-DD'. Defaults to the current date when the caller omits it."
},
"start_date": {
"type": "string",
"description": "Start of the date range covered, 'YYYY-MM-DD'. When the caller omits start_date/end_date, this is the endpoint's own default range start, observed as one calendar month before the default end_date on the gbp-jpy-default fixture."
},
"data_points": {
"type": "number",
"description": "Count of entries in `rates`."
},
"to_currency": {
"type": "string",
"description": "Echoed target currency code, e.g. 'USD'."
},
"from_currency": {
"type": "string",
"description": "Echoed source currency code, e.g. 'EUR'."
},
"change_percent": {
"type": "number",
"description": "Percent change from the first to the last rate in the range; can be negative."
}
},
"description": "The forex history result, as returned at routing.responseResultPath ($.output).",
"additionalProperties": true
}Pricing
Every real charge, itemised. A model that quietly omits one is a slow financial leak, so nothing here is rolled up, and a charge that only applies to some inputs says so rather than being added in.
Prices in this catalog are the provider's own list price, not your bill: Omnial MCP charges provider cost plus a platform markup on top, so what you are charged is higher than the figure shown. For the exact amount a specific call will cost, run omnial_execute with dry_run: true; that number includes the markup and is what we hold while the call runs. It is a quote, not a cap on the charge.
| Charge | Rate |
|---|---|
Per call Flat, regardless of what comes back | $0.081081 |
- Cost basis
- Not recorded
This tool's catalog entry does not record how its final bill is determined, so we will not tell you whether its cost is fixed before the call or reported by the provider afterwards. Either way what is held is a quote rather than a cap: you are charged what the call actually costs, bounded at 2x the quote.
- Updated
- Sep 23, 2026
