Compare Yes and No trading volumes for one Polymarket market. Returns market volume-chart points with Yes/No volume breakdowns and the selected granularity and window. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Up to 0.0288 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
Surf
Polymarket Volume YES vs NO Split | Surf
Compare Yes and No trading volumes for one Polymarket market. Returns market volume-chart points with Yes/No volume breakdowns and the selected granularity and window. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
You receive
Returns market volume-chart points with Yes/No volume breakdowns and the selected granularity and window. Use the returned window boundaries when comparing sides. This series measures trading activity, not the number of voters or final settlement confidence.
Start with your task
For [Polymarket question link], compare how much trading there was on Yes and No over [the past 7 days], shown [day by day]. If the page lists multiple questions, ask which one I mean. Explain that the numbers show trading activity, not how many people voted or which answer will win.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
End time (Unix seconds). 0 means current time. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result.
Minimum
0
Maximum
9007199254740991
start_timequeryParams.start_time
integer
Optional
Start time (Unix seconds). 0 means no lower bound. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result.
Minimum
0
Maximum
9007199254740991
granularityqueryParams.granularity
string
Optional
Time granularity for volume aggregation. Defaults to "hour".
Default
hour
Options
hour, day, week
View raw JSON
{
"type": "object",
"required": [
"pathParams"
],
"properties": {
"pathParams": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"condition_id"
],
"~standard": {
"vendor": "zod",
"version": 1,
"jsonSchema": {}
},
"properties": {
"condition_id": {
"type": "string",
"minLength": 1,
"description": "Polymarket condition ID. Example: 0x6fefc0438c7598b23531457c8c60541990d0786bd4bd9dfc3eabc8d95c291092."
}
},
"additionalProperties": false
},
"queryParams": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"~standard": {
"vendor": "zod",
"version": 1,
"jsonSchema": {}
},
"properties": {
"end_time": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "End time (Unix seconds). 0 means current time. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result."
},
"start_time": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0,
"description": "Start time (Unix seconds). 0 means no lower bound. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result."
},
"granularity": {
"enum": [
"hour",
"day",
"week"
],
"type": "string",
"default": "hour",
"description": "Time granularity for volume aggregation. Defaults to \"hour\"."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
Result schema
Output fields have not been documented yet.
Additional notes
Compare Yes and No trading volumes for one Polymarket market
How to use this Tool
Use the deployed input fields below. Required fields must be supplied; optional filters narrow the result.
queryParams.end_time (Optional): End time (Unix seconds). 0 means current time. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result.
queryParams.start_time (Optional): Start time (Unix seconds). 0 means no lower bound. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result.
queryParams.granularity (Optional): Time granularity for volume aggregation. Defaults to "hour".
What this Tool returns
Returns market volume-chart points with Yes/No volume breakdowns and the selected granularity and window.
Response fields and how to read them
The table follows the official response contract, including nested fields and useful response metadata. [] denotes an array item. Required means required within its parent object, not that a conditional parent always exists. A nullable type permits null; an optional field can be absent. Use the documented conditions below to distinguish missing, empty and zero values. Units and reporting windows apply only where explicitly documented.
Field, type and presence
Meaning and conditions
condition_id
string; Required within parent
The official contract declares this field but does not explain its meaning or units. Treat its interpretation as unverified; do not infer completeness or a unit from the field name.
data_points
array | null; Required within parent
The official contract declares this field but does not explain its meaning or units. Treat its interpretation as unverified; do not infer completeness or a unit from the field name.
data_points.[].no_volume
number; Required within parent; format: double
No-side volume in USD
data_points.[].timestamp
integer; Required within parent; format: int64
Unix timestamp (seconds)
data_points.[].total_volume
number; Required within parent; format: double
Total volume in USD
data_points.[].trades_count
integer; Required within parent; format: int64
Number of trades
data_points.[].yes_volume
number; Required within parent; format: double
Yes-side volume in USD
end_time
integer; Required within parent; format: int64
The official contract declares this field but does not explain its meaning or units. Treat its interpretation as unverified; do not infer completeness or a unit from the field name.
granularity
string; Required within parent
The official contract declares this field but does not explain its meaning or units. Treat its interpretation as unverified; do not infer completeness or a unit from the field name.
start_time
integer; Required within parent; format: int64
The official contract declares this field but does not explain its meaning or units. Treat its interpretation as unverified; do not infer completeness or a unit from the field name.
Coverage, units and freshness
Use the returned window boundaries when comparing sides. This series measures trading activity, not the number of voters or final settlement confidence.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
Data source and references
Surf supplies this endpoint through its Data API. Response contract and deployed Tool inputs reviewed on 2026-10-03 against official OpenAPI v0.2.102. This is a contract review date, not a data observation time. Coverage depends on the selected endpoint and request.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Try [the past 7 days] shown [day by day], or [the past 30 days] shown [week by week].
For [Polymarket question link], compare how much trading there was on Yes and No over [the past 7 days], shown [day by day]. If the page lists multiple questions, ask which one I mean. Explain that the numbers show trading activity, not how many people voted or which answer will win.
Compare the two sides
Ask: [How much was traded on Yes compared with No over the past 24 hours?] The numbers show trading activity, not voter counts or a guaranteed winner.
Questions about this tool.
Inputs, results and details to know before running it.
pathParams.condition_id (Required): Polymarket condition ID. Example: 0x6fefc0438c7598b23531457c8c60541990d0786bd4bd9dfc3eabc8d95c291092. queryParams.end_time (Optional): End time (Unix seconds). 0 means current time. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result. queryParams.start_time (Optional): Start time (Unix seconds). 0 means no lower bound. Cache aligns to 5-minute buckets, so two requests within the same bucket return the same cached result. queryParams.granularity (Optional): Time granularity for volume aggregation. Defaults to "hour".
Returns market volume-chart points with Yes/No volume breakdowns and the selected granularity and window.
Use the returned window boundaries when comparing sides. This series measures trading activity, not the number of voters or final settlement confidence.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0288 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Ask your agent to Compare Yes and No trading volumes for one Polymarket market. Provide the required inputs above. If Toolmu is already connected, reuse that connection; otherwise use the setup instructions on this page. Before a paid execution, the agent must read the current Tool contract and check availability, the credit ceiling, balance, budget and your authorization. It should then execute the Tool and explain the returned fields and limitations.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
