{"uid":"cap_Mjfqaend6r7EiaflVdQG3","slug":"api-usage-two-measure-correlation-c1d11270","name":"API Usage Two-Measure Correlation","description":"API usage - Two-measure correlation: Two-measure correlation for API usage. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded two-measure correlation deliverable.","url":"https://market.datapackvibe.com/x402/assistant-sector-analytics-api-usage-correlation?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","endpoint","date","requests","latency_ms"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"endpoint":{"type":"string","default":"","maxLength":80},"requests":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"latency_ms":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","endpoint":"group-a","requests":10,"latency_ms":1},{"date":"2026-10-02","row_id":"row-2","endpoint":"group-b","requests":20,"latency_ms":2},{"date":"2026-10-03","row_id":"row-3","endpoint":"group-a","requests":15,"latency_ms":3},{"date":"2026-10-04","row_id":"row-4","endpoint":"group-b","requests":30,"latency_ms":4}],"maxItems":200,"minItems":1}}},"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_AdM2gFhs55kQ6LHpAt1Mc","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":"Computes the statistical correlation between API request counts and latency measurements across up to 200 typed records, locally, without external enrichment.","exampleAgentPrompt":"Can you run a two-measure correlation on my API usage data to see how request counts relate to latency? Here are up to 200 rows with endpoint names, dates, request counts, and latency in milliseconds — I want to know how strongly these two metrics are correlated.","exampleUseCases":[{"title":"Latency vs traffic spike analysis","prompt":"I have 150 daily records from my production API with request counts and latency values per endpoint — can you run a two-measure correlation to tell me how strongly traffic volume is correlated with response time?"},{"title":"Comparing two endpoint groups","prompt":"I want to correlate requests and latency for two endpoint groups, group-a and group-b, across the last 90 days. Can you compute the correlation coefficient between those two measures for me?"},{"title":"API performance regression check","prompt":"After our latest deployment I logged request counts and latency_ms for each day across four endpoints — can you calculate the two-measure correlation on these records so I can see if higher load is statistically linked to slower responses?"}],"resultDescription":"Returns a bounded correlation deliverable containing the computed correlation coefficient between the two supplied numeric measures (requests and latency_ms), along with data-quality metadata derived from the submitted rows. All processing is local with no external enrichment or forecasting.","failureModes":["Fewer than 1 row submitted — minimum item count not met","More than 200 rows submitted — exceeds maxItems limit","Missing required fields (row_id, endpoint, date, requests, latency_ms) — validation error","Date field not matching YYYY-MM-DD pattern — schema validation failure","Numeric values outside allowed range — schema rejection","All numeric values null — insufficient data to compute correlation"],"whenToPreferThis":"Choose this endpoint when you need a fast, local statistical correlation between exactly two numeric API usage metrics (request count and latency) across up to 200 records, without requiring external data enrichment, forecasting, or multi-measure analysis. It is ideal for lightweight performance diagnostics and load-latency relationship checks at low cost ($0.01 USDC per call).","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-19T12:47:20.917Z","isFirstParty":false,"canonicalSlug":"api-usage-two-measure-correlation-c1d11270"}