Response time (ms)
msAverage API response time in milliseconds
What is response time (ms)?
Average API response time in milliseconds
Why it matters
Understanding response time (ms) helps developers make informed decisions when evaluating models and providers. This metric provides a concrete, comparable data point — removing guesswork from the selection process. When you know the numbers, the data decides.
Where models stand
No data available yet for this metric.
How sourc.dev tracks this
sourc.dev tracks response time (ms) through its automated monitoring pipeline. Data is collected on a regular schedule, compared against previous values, and any changes are recorded in the history table with full provenance — source URL, effective date, and verification timestamp. Nothing is overwritten. The pipeline ensures this attribute stays current without manual intervention.
Related
Frequently asked questions
How does sourc.dev measure response time (ms)?
sourc.dev monitors this attribute automatically via pipeline. Every data point includes a source URL and verification date. Changes are recorded in the history table — nothing is overwritten.
How often is response time (ms) updated?
This attribute is monitored on a regular schedule by automated pipeline. Changes are detected and recorded automatically.
Why does response time (ms) matter for developers?
Understanding response time (ms) helps developers make informed decisions when choosing between models and providers. Rather than relying on marketing claims, sourc.dev provides verified, dated, source-linked data so the data decides.