How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Eigenpal Evaluation API

Manage datasets, examples, evaluators, experiment batches, evaluator scores, and run promotion workflows.

Eigenpal Evaluation API is one of 6 APIs that Eigenpal publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Evaluation. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 29 operations across 18 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://studio.eigenpal.com.

29 operations 18 paths 29 schemas 3 DELETE14 GET3 PATCH8 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://studio.eigenpal.com
Authentication
HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 1

Eigenpal Evaluation API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API key issued from Settings → API Keys. Pass as Authorization: Bearer .

Paths & Operations 29

Across 18 paths, the API surfaces 29 operations — 3 DELETE, 14 GET, 3 PATCH, 8 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Evaluation 29

Manage datasets, examples, evaluators, experiment batches, evaluator scores, and run promotion workflows.

GET
/api/v1/automations/{id}/dataset/export
Export automation dataset
automations.dataset.export 2 params → 200400401403404413429500
POST
/api/v1/automations/{id}/dataset/import
Import automation dataset
automations.dataset.import 1 param body → 200400401403404413429500
GET
/api/v1/automations/{id}/evaluators
Get evaluators
automations.evaluators.get 1 param → 200400401403404413429500
PUT
/api/v1/automations/{id}/evaluators
Replace evaluators
automations.evaluators.update 1 param body → 200400401403404413429500
GET
/api/v1/automations/{id}/examples
List dataset examples
automations.examples.list 3 params → 200400401403404413429500
POST
/api/v1/automations/{id}/examples
Create dataset example
automations.examples.create 1 param body → 201400401403404413429500
GET
/api/v1/automations/{id}/examples/{exampleId}
Get dataset example
automations.examples.get 2 params → 200400401403404413429500
PATCH
/api/v1/automations/{id}/examples/{exampleId}
Update dataset example
automations.examples.update 2 params body → 200400401403404413429500
DELETE
/api/v1/automations/{id}/examples/{exampleId}
Delete dataset example
automations.examples.delete 2 params → 200400401403404413429500
GET
/api/v1/automations/{id}/examples/{exampleId}/expected
List expected files
automations.examples.expected.files.list 2 params → 200400401403404413429500
POST
/api/v1/automations/{id}/examples/{exampleId}/expected
Upload expected files
automations.examples.expected.files.create 2 params body → 201400401403404413429500
GET
/api/v1/automations/{id}/examples/{exampleId}/expected/{path}
Download expected dataset file
automations.examples.expected.file.get 3 params → 200400401403404413429500
PATCH
/api/v1/automations/{id}/examples/{exampleId}/expected/{path}
Rename expected file
automations.examples.expected.file.update 3 params body → 200400401403404413429500
DELETE
/api/v1/automations/{id}/examples/{exampleId}/expected/{path}
Delete expected file
automations.examples.expected.file.delete 3 params → 200400401403404413429500
GET
/api/v1/automations/{id}/examples/{exampleId}/input
List input files
automations.examples.input.files.list 2 params → 200400401403404413429500
POST
/api/v1/automations/{id}/examples/{exampleId}/input
Upload input files
automations.examples.input.files.create 2 params body → 201400401403404413429500
GET
/api/v1/automations/{id}/examples/{exampleId}/input/{path}
Download input file
automations.examples.input.file.get 3 params → 200400401403404413429500
PATCH
/api/v1/automations/{id}/examples/{exampleId}/input/{path}
Rename input file
automations.examples.input.file.update 3 params body → 200400401403404413429500
DELETE
/api/v1/automations/{id}/examples/{exampleId}/input/{path}
Delete input file
automations.examples.input.file.delete 3 params → 200400401403404413429500
POST
/api/v1/automations/{id}/examples/{exampleId}/run
Run dataset example
automations.examples.run 2 params → 201400401403404413429500
GET
/api/v1/automations/{id}/experiments
List experiments
automations.experiments.list 5 params → 200400401403404413429500
POST
/api/v1/automations/{id}/experiments
Create experiment
automations.experiments.create 1 param body → 202400401403404413429500
GET
/api/v1/automations/{id}/experiments/{experimentId}
Get experiment
automations.experiments.get 2 params → 200400401403404413429500
POST
/api/v1/automations/{id}/experiments/{experimentId}/cancel
Cancel experiment
automations.experiments.cancel 2 params → 200400401403404413429500
GET
/api/v1/automations/{id}/experiments/{experimentId}/export
Export experiment eval results
automations.experiments.export 4 params → 200400401403404413429500
GET
/api/v1/automations/{id}/experiments/export
Export all experiment eval results
automations.experiments.exportAll 2 params → 200400401403404413429500
POST
/api/v1/automations/{id}/experiments/stream
Create automation experiment with NDJSON progress
automations.experiments.createStream 1 param body → 200400401403404413429500
GET
/api/v1/experiments/{experimentId}
Resolve experiment by id
experiments.resolve 1 param → 200400401403404413429500
GET
/api/v1/runs/{id}/scores
List run evaluator scores
runs.scores.list 1 param → 200400401403404413429500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are DatasetExample (14 properties), ExperimentDetail (14 properties), EvalResult (14 properties), Experiment (12 properties). Each schema is shown below with its type and property counts.

ApiErrorEnvelope
object
4 properties 2 required
ExampleRunResponse
object
4 properties 4 required
DatasetExample
object
One input/expected-output row in an automation dataset.
14 properties 12 required
ExperimentRef
object
2 properties 2 required
DatasetImportResponse
DatasetExampleExpectedFileList
object
1 property 1 required
ExperimentCreate
object
Request body for starting an experiment batch.
3 properties
DatasetExampleInputFileRenameRequest
object
1 property 1 required
DatasetExampleMutation
object
Fields used to create or update a dataset example.
7 properties
ApiErrorIssue
object
4 properties 4 required
DatasetExampleInputFileUploadRequest
object
1 property 1 required
DatasetExampleExpectedFileRenameResponse
object
3 properties 3 required
AutomationType
string
DatasetExampleInputFileRenameResponse
object
3 properties 3 required
DatasetExampleExpectedFileUploadResponse
object
1 property 1 required
DatasetExampleInputFileList
object
1 property 1 required
ExperimentCreateResponse
object
Accepted experiment batch and the runs it enqueued.
3 properties 3 required
DatasetExampleExpectedFileRenameRequest
object
1 property 1 required
DatasetExampleInputFileUploadResponse
object
1 property 1 required
RunScoresResponse
object
Automated evaluator results attached to a run.
1 property 1 required
DatasetExampleList
object
4 properties 4 required
EvalResult
object
Automated evaluator result for one run.
14 properties 14 required
DatasetExampleUpdate
object
Partial update for a dataset example. Omitted fields are preserved.
7 properties
DatasetExampleExpectedFileUploadRequest
object
1 property 1 required
EvaluatorConfigResponse
object
Evaluator YAML and parsed evaluator configuration for an automation.
4 properties 4 required
ExperimentDetail
object
Experiment batch detail.
14 properties 14 required
EvaluatorConfigUpdate
object
Replacement evaluator configuration.
1 property 1 required
AutomationDatasetImportMultipartRequest
object
2 properties 1 required
Experiment
object
Experiment batch summary for an automation dataset run.
12 properties 12 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eigenpal-evaluation-api-openapi.yml Raw ↑

Other APIs Eigenpal publishes across the network.

Eigenpal Automations API
Eigenpal Files API
Eigenpal Metadata API
Eigenpal Reviews API
Eigenpal Runs API
Where this information came from

This is an independent, third-party profile of Eigenpal Evaluation API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.