Records
Create Record
Create a new Record in a Run.
POST
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Path Parameters
The ID of the Run.
Example:
"135"
Body
application/json
The actual inputs sent to the system, which should match the system's input schema.
The expected outputs for the Testcase.
The actual outputs from the system.
The ID of the Testcase.
Response
201
application/json
Record created successfully
A record of a system execution in the Scorecard system.
The ID of the Record.
The ID of the Run containing this Record.
The actual inputs sent to the system, which should match the system's input schema.
The expected outputs for the Testcase.
The actual outputs from the system.
The ID of the Testcase.
Previous
Create systemCreate a new system definition that specifies the interface contracts for a component you want to evaluate.
A system acts as a template that defines three key contracts through JSON Schemas:
1. Input Schema: What data your system accepts (e.g., user queries, context documents)
2. Output Schema: What data your system produces (e.g., responses, confidence scores)
3. Config Schema: What parameters can be adjusted (e.g., model selection, temperature)
This separation lets you evaluate any system as a black box, focusing on its interface rather than implementation details.
Next