{"uid":"cap_4etVfOmtBTrTJvo3PMWSw","slug":"render-farm-usage-string-normalisation-numeric-row-ordering-086f2407","name":"Render Farm Usage — String Normalisation + Numeric Row Ordering","description":"Render farm usage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied render farm usage records (node_hours, job_count). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.","url":"https://market.datapackvibe.com/x402/assistant-ib26-creative-24-025?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","asset_group","date","node_hours","job_count"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"job_count":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"node_hours":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"asset_group":{"type":"string","default":"","maxLength":80}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","job_count":1,"node_hours":10,"asset_group":"group-a"},{"date":"2026-10-02","row_id":"row-2","job_count":2,"node_hours":20,"asset_group":"group-b"},{"date":"2026-10-03","row_id":"row-3","job_count":3,"node_hours":15,"asset_group":"group-a"},{"date":"2026-10-04","row_id":"row-4","job_count":4,"node_hours":30,"asset_group":"group-b"}],"maxItems":200,"minItems":1},"field":{"enum":["node_hours","job_count"],"type":"string","default":"node_hours"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_8jaZ_Tsi8jh7Pq2NiDEa4","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Normalises string fields and sorts rows by numeric value for up to 200 render farm usage records (node_hours, job_count), returning two analytical reports per call.","exampleAgentPrompt":"Can you normalise the string fields and rank the rows by node_hours for my render farm usage data? I have 4 records: row-1 for group-a on 2026-10-01 with 10 node_hours and 1 job, row-2 for group-b on 2026-10-02 with 20 node_hours and 2 jobs, row-3 for group-a on 2026-10-03 with 15 node_hours and 3 jobs, row-4 for group-b on 2026-10-04 with 30 node_hours and 4 jobs — give me both the string normalisation and numeric ordering reports.","exampleUseCases":[{"title":"Rank studio renders by node hours","prompt":"I've got a list of 50 render farm jobs across different asset groups from last month — can you normalise the asset group names and rank all the rows by node_hours so I can see which jobs consumed the most compute?"},{"title":"Sort VFX jobs by job count","prompt":"Here are 120 rows of our render farm usage data with dates, node hours, and job counts per asset group — please normalise the string fields and sort everything by job_count so I can identify our busiest production days."},{"title":"Clean render farm logs before billing","prompt":"Before I send our render farm usage report to finance, can you normalise the asset group strings and order the rows numerically by node_hours for these 80 records? I want both the normalisation and ordering reports."}],"resultDescription":"Two analytical reports per call: (1) a string normalisation report cleaning and standardising the asset_group and related string fields across all supplied rows, and (2) a numeric row ordering report ranking the rows by the selected numeric field (node_hours or job_count). No external data is fetched; all analysis is performed on the supplied rows only.","failureModes":["More than 200 rows submitted — request rejected with validation error","Missing required fields (row_id, asset_group, date, node_hours, job_count) — row rejected or error returned","Invalid date format (not YYYY-MM-DD) — validation failure","Numeric values outside allowed range (±1,000,000,000,000) — validation error","Invalid field enum value (not node_hours or job_count) — error returned","Empty rows array — minimum 1 item required"],"whenToPreferThis":"Choose this endpoint when you have render farm usage records (with node_hours and job_count fields) and need both string normalisation and numeric ordering in a single low-cost call. It is ideal for pre-billing data cleanup, production reporting pipelines, or any workflow that requires standardising asset group labels and ranking compute usage rows without any live lookups or external dependencies. Best suited for batches of up to 200 rows.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-11-03T12:43:03.949Z","isFirstParty":false,"canonicalSlug":"render-farm-usage-string-normalisation-numeric-row-ordering-086f2407"}