Score Interpreter FAQ

The Score Interpreter consists of Scoring Service REST API, Forecasting REST API, and State Performance Standards Database.

What is the MetaMetrics Score Interpreter and how is it used?

The MetaMetrics Score Interpreter comprises three components:
  • Scoring Service REST API
  • Forecasting REST API
  • State Performance Standards Database

For computer-based assessments developed by MetaMetrics and for tests that we link to, our Score Interpreter immediately delivers student Lexile® reading measures and Quantile® measures for math, forecasts an individual student or group performance on an upcoming assessment, and aligns results to partner state performance standards.

Where can I find more information about the individual MetaMetrics Score Interpreter components?

You can find more information about the individual MetaMetrics Score Interpreter components here:

What is the MetaMetrics Scoring Service REST API and how is it used?

The MetaMetrics Scoring Service REST API has been designed to simplify assigning an ability estimate to a test-taker. As students take assessments, test results can be sent to the Scoring Service API, providing real-time estimates of student ability.

What is the difference between the Scoring Service REST API and the Scoring Service XML-RPC API?

In December of 2020, MetaMetrics released a new REST-based Scoring Service API. Both APIs serve the same purpose and functionality; to assign measures to test takers with or without prior performance information. Migrating to REST improves security, is more consistent with industry standards, provides more comprehensive documentation, helps with support, and is simpler and more efficient for your technical staff to use. The XML-RPC API will be sunsetted in the summer of 2022. Existing XML-RPC users will need to migrate to the REST version before then. New users will only use the REST version.

Do I need to install or manage any Scoring Service REST API software?

MetaMetrics provides highly available and scalable services using Amazon Web Services (AWS) in geographically-diverse data centers. The Scoring Service API is a MetaMetrics-managed web service. Clients using the service are not required to install or manage anything.

What kinds of calls are supported by the Scoring Service REST API?

There are two different types of API calls supported by the Scoring Service. The first type provides a student measure for an assessment when there is no prior information available about the student (i.e., measures, uncertainties). The second group of calls provides a student measure that accounts for a student’s previous performance using Bayesian scoring.

How do I know which call to use?

When a student is administered an assessment that can report Lexile reading or Quantile mathematics measures, estimates of the student's ability (Lexile reading/Quantile mathematics measure) must be calculated. An estimate of a student's ability comprises an ability measure (i.e., Lexile reading or Quantile mathematics measure) and associated uncertainty. If prior ability information about the student is not available, the student's performance on the singular assessment can be used to estimate a measure and associated uncertainty. When a student's prior ability measure and associated uncertainty are available and used with a Bayesian scoring function call, they represent an estimate of ability given all of the student's previous testing experiences and are referred to as priors. When this prior student data is available, the Scoring Service API can provide a more accurate estimate of a student's current ability by using Bayesian scoring. The Scoring Service API will need the student's latest ability information, or priors, as well as how long ago the priors were calculated. Bayesian scoring uses the time elapsed since the last test or age of the estimate to determine how much additional uncertainty should be associated with the current estimates. The Scoring Service API will return an updated estimate of the student's ability (Lexile reading/Quantile mathematics measure) and its associated uncertainty.

How do I report Scoring Service REST API measures?

The calls in the Scoring Service API return a measure and uncertainty. If the measures are being used for research or institutional purposes, they can be used as reported. Measures provided by the standard calls can also be used when making Bayesian calls. If the measures are used for reporting to teachers, parents, and students, then proper branding needs to be applied. See Reporting Scoring Service Measures for specific information on reporting measures.

What kind of performance can I expect from the Scoring Service REST API?

See Service Level Agreement for Scoring Service API for performance commitments, problem reporting and escalation, maintenance information, and more.

What is the Forecasting REST API and how is it used?

The Forecasting API forecasts an individual student or group performance on an upcoming assessment. To accomplish this, the API uses a proprietary growth model, prior information about a student or group of students, and information about an examination to be taken in the future.

What is the difference between the Forecasting REST API and the Forecasting XML-RPC API?

In December of 2020, MetaMetrics released a new REST-based Forecasting API. Both APIs serve the same purpose and functionality; to forecast an individual student or group performance on an upcoming assessment. Migrating to REST improves security, is more consistent with industry standards, provides more comprehensive documentation, helps with support, and is simpler and more efficient for your technical staff to use. The XML-RPC API will be sunsetted in the summer of 2022. Existing XML-RPC users will need to migrate to the REST version before then. New users will only use the REST version.

Do I need to install or manage any software for the Forecasting REST API?

The Forecasting API is a MetaMetrics-managed web service. Clients using the service are not required to install or manage anything. MetaMetrics provides highly available and scalable services using Amazon Web Services (AWS) in geographically-diverse data centers.

What kinds of calls are supported by the Forecasting REST API?

There are two different types of API calls supported by the Forecasting API. The first type forecasts an individual student performance on an upcoming assessment. The second type forecasts a group's performance on an upcoming assessment.

How do I report Forecasting REST API measures?

If the measures are being used for research or institutional purposes, they can be used as reported. If the measures are used for reporting to teachers, parents, and students, then proper branding needs to be applied. See Reporting Scoring Service Measures for specific information on reporting measures.

What kind of performance can I expect out of the Forecasting REST API?

See Service Level Agreement for Scoring Service API for performance commitments, problem reporting and escalation, maintenance information, and more.

What is the MetaMetrics Score Interpreter and how is it used?

The State Performance Standards Database is a data file that aligns Lexile and Quantile measures with state proficiency standards for those states whose assessments are linked with the Lexile and or Quantile Frameworks and decide to use the database.

How is the State Performance Standards Database delivered to MetaMetrics partners?

The State Performance Standards Database is sent to MetaMetrics as a .csv file that contains five tabs:
  • Cut Scores Summary
  • Cut Scores
  • Extrap-Interp Summary
  • Extrap-Interp Cut Scores
  • Change History Log

Forecasting files, information about the Forecasting API and how it relates to the State Performance Standards Database, explanations of each tab in the State Performance Standards Database, and examples of how to use the performance level cut scores and interpolation/extrapolation values are included in a technical report that is prepared for each MetaMetrics partner using the MetaMetrics Score Interpreter.