Contract
{
"type": "object",
"required": [
"product_id"
],
"properties": {
"region": {
"type": "string",
"default": "SG",
"examples": [
"SG"
],
"description": "Region code"
},
"product_id": {
"type": "string",
"examples": [
"1732108663255959373"
],
"description": "Product ID"
}
},
"additionalProperties": false
}{
"type": "object",
"properties": {
"valid": {
"type": "boolean",
"description": "Whether the given product_id passed the endpoint's own format check. Observed `false` for an out-of-range product_id (e.g. '0', bit_length=0, expected 50-64). Never observed `true` -- no fixture captured a product_id that both passed the format check and resolved to a real listing. Absent entirely on the empty not-found shape."
},
"message": {
"type": "string",
"description": "Bilingual (Chinese/English) explanation of why the given product_id was rejected, e.g. an out-of-range bit length. Only present on the validation-error shape observed."
},
"product_id": {
"type": "string",
"description": "Echoes back the product_id supplied in the request. Only present on the validation-error shape observed; absent on the empty not-found shape."
}
},
"description": "The result object, as returned at routing.responseResultPath ($.output). Only two shapes have been observed: a malformed/out-of-range product_id returns `{valid, product_id, message}` describing why the ID was rejected; a syntactically valid but nonexistent product_id returns an empty object `{}` (billed $0). A genuinely found product's own detail fields (title, price, images, seller, etc.) were not captured by either fixture and are UNCONFIRMED -- this schema describes only the two observed shapes.",
"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.0020475 |
- 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 12, 2026
