{"uid":"cap_Ym8wDXEjU28JldBwy7U7Q","slug":"mining-pool-shares-string-normalisation-numeric-row-ordering-13be548c","name":"Mining Pool Shares — String Normalisation + Numeric Row Ordering","description":"Mining pool shares — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied mining pool shares records (accepted_shares, rejected_shares). 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-finance-02-025?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","instrument_group","date","accepted_shares","rejected_shares"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"accepted_shares":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"rejected_shares":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"instrument_group":{"type":"string","default":"","maxLength":80}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","accepted_shares":10,"rejected_shares":1,"instrument_group":"group-a"},{"date":"2026-10-02","row_id":"row-2","accepted_shares":20,"rejected_shares":2,"instrument_group":"group-b"},{"date":"2026-10-03","row_id":"row-3","accepted_shares":15,"rejected_shares":3,"instrument_group":"group-a"},{"date":"2026-10-04","row_id":"row-4","accepted_shares":30,"rejected_shares":4,"instrument_group":"group-b"}],"maxItems":200,"minItems":1},"field":{"enum":["accepted_shares","rejected_shares"],"type":"string","default":"accepted_shares"}}},"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_6QOsAt_bdzAB6QcwQ5wUX","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 applies numeric row ordering to mining pool share records (accepted_shares, rejected_shares) for up to 200 rows, producing 2 analytical reports.","exampleAgentPrompt":"Can you normalise the string fields and sort rows numerically by accepted_shares for my mining pool data? I have 4 records: row-1 on 2026-10-01 with 10 accepted and 1 rejected for group-a, row-2 on 2026-10-02 with 20 accepted and 2 rejected for group-b, row-3 on 2026-10-03 with 15 accepted and 3 rejected for group-a, and row-4 on 2026-10-04 with 30 accepted and 4 rejected for group-b — I need 2 reports back.","exampleUseCases":[{"title":"Daily mining pool share cleanup","prompt":"I have a week's worth of mining pool share records across two rigs — can you normalise the instrument group strings and order all rows by accepted_shares so I can see which days performed best? Here are my 7 rows: row-1 2026-10-01 group-a 500 accepted 12 rejected, row-2 2026-10-02 Group-A 480 accepted 8 rejected, row-3 2026-10-03 group-b 620 accepted 20 rejected, row-4 2026-10-04 GROUP-B 590 accepted 15 rejected, row-5 2026-10-05 group-a 510 accepted 10 rejected, row-6 2026-10-06 group-b 630 accepted 18 rejected, row-7 2026-10-07 group-a 470 accepted 9 rejected."},{"title":"Rejected shares anomaly ordering","prompt":"Sort my mining pool records by rejected_shares so I can spot which pools had the most rejects — here are my 5 rows: row-1 2026-11-01 pool-alpha 1000 accepted 45 rejected, row-2 2026-11-02 pool-beta 980 accepted 12 rejected, row-3 2026-11-03 pool-alpha 1050 accepted 60 rejected, row-4 2026-11-04 pool-gamma 900 accepted 5 rejected, row-5 2026-11-05 pool-beta 1020 accepted 30 rejected. Also normalise the pool name strings."},{"title":"Multi-group share data standardisation","prompt":"I've got mining share data from three instrument groups with inconsistent casing in the group names — please normalise the strings and give me both reports ordered numerically by accepted_shares. My 6 rows: row-1 2026-09-01 RIG-One 200 accepted 8 rejected, row-2 2026-09-02 rig-one 180 accepted 5 rejected, row-3 2026-09-03 Rig-Two 300 accepted 10 rejected, row-4 2026-09-04 RIG-TWO 290 accepted 7 rejected, row-5 2026-09-05 rig-three 150 accepted 3 rejected, row-6 2026-09-06 Rig-Three 160 accepted 4 rejected."}],"resultDescription":"Returns 2 analytical reports: one covering string-normalised instrument_group and related string fields across the supplied rows, and one providing numerically ordered rows ranked by the selected field (accepted_shares or rejected_shares). Results are based entirely on the supplied data — no external lookups or live data.","failureModes":["Submitting more than 200 rows causes a validation error","Missing required fields (row_id, date, instrument_group, accepted_shares, rejected_shares) on any row causes rejection","Invalid date format (not YYYY-MM-DD) causes schema validation failure","Providing an unsupported field enum value causes a bad request","Numeric values outside ±1,000,000,000,000 are rejected","Empty rows array is not accepted (minItems: 1)"],"whenToPreferThis":"Choose this endpoint when you have up to 200 rows of mining pool share data (accepted_shares, rejected_shares) that need string field normalisation and numeric ordering in a single call for a flat $0.01 USDC fee. It is well-suited for offline batch processing of pool share records where no live data, predictions, or external lookups are needed. Prefer it over general-purpose analytics tools when you specifically need the two bundled reports (string normalisation + numeric ordering) delivered together for crypto mining share data.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-11-02T12:34:50.163Z","isFirstParty":false,"canonicalSlug":"mining-pool-shares-string-normalisation-numeric-row-ordering-13be548c"}