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

Helicone Experiment API

The Experiment API from Helicone — 40 operation(s) for experiment.

Helicone Experiment API is one of 33 APIs that Helicone publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Experiment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, pricing, an API reference, and an engineering blog.

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

Requests are made against 2 base URLs: https://api.helicone.ai/, http://localhost:8585/.

44 operations 40 paths 72 schemas 6 DELETE9 GET1 PATCH28 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://ai-gateway.helicone.ai
Authentication
API Key
License
MIT
Resource Areas
1

Authentication & Security 1

Helicone Experiment API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_key).

  • api_key — Bearer token authentication. Format: 'Bearer YOURAPIKEY'

Paths & Operations 44

Across 40 paths, the API surfaces 44 operations — 6 DELETE, 9 GET, 1 PATCH, 28 POST. Each is listed below with its method, path, parameters, and response codes.

Experiment 44
POST
/v2/experiment/create/empty
Create empty experiment
CreateEmptyExperiment → 200
POST
/v2/experiment/create/from-request/{requestId}
Create experiment from request
CreateExperimentFromRequest 1 param → 200
POST
/v2/experiment/new
Create new experiment
CreateNewExperiment body → 200
GET
/v2/experiment
Get experiments
GetExperiments → 200
DELETE
/v2/experiment/{experimentId}
Delete experiment
DeleteExperiment 1 param → 200
GET
/v2/experiment/{experimentId}
Get experiment by id
GetExperimentById 1 param → 200
POST
/v2/experiment/{experimentId}/prompt-version
Create new prompt version for experiment
CreateNewPromptVersionForExperiment 1 param body → 200
DELETE
/v2/experiment/{experimentId}/prompt-version/{promptVersionId}
Delete prompt version
DeletePromptVersion 2 params → 200
GET
/v2/experiment/{experimentId}/prompt-versions
Get prompt versions for experiment
GetPromptVersionsForExperiment 1 param → 200
GET
/v2/experiment/{experimentId}/input-keys
Get input keys for experiment
GetInputKeysForExperiment 1 param → 200
POST
/v2/experiment/{experimentId}/add-manual-row
Add manual row to experiment
AddManualRowToExperiment 1 param body → 200
POST
/v2/experiment/{experimentId}/add-manual-rows-batch
Add manual rows to experiment batch
AddManualRowsToExperimentBatch 1 param body → 200
DELETE
/v2/experiment/{experimentId}/rows
Delete experiment table rows
DeleteExperimentTableRows 1 param body → 200
POST
/v2/experiment/{experimentId}/row/insert/batch
Create experiment table row batch
CreateExperimentTableRowBatch 1 param body → 200
POST
/v2/experiment/{experimentId}/row/insert/dataset/{datasetId}
Create experiment table row from dataset
CreateExperimentTableRowFromDataset 2 params → 200
POST
/v2/experiment/{experimentId}/row/update
Update experiment table row
UpdateExperimentTableRow 1 param body → 200
POST
/v2/experiment/{experimentId}/run-hypothesis
Run hypothesis
RunHypothesis 1 param body → 200
GET
/v2/experiment/{experimentId}/evaluators
Get experiment evaluators
GetExperimentEvaluators 1 param → 200
POST
/v2/experiment/{experimentId}/evaluators
Create experiment evaluator
CreateExperimentEvaluator 1 param body → 200
DELETE
/v2/experiment/{experimentId}/evaluators/{evaluatorId}
Delete experiment evaluator
DeleteExperimentEvaluator 2 params → 200
POST
/v2/experiment/{experimentId}/evaluators/run
Run experiment evaluators
RunExperimentEvaluators 1 param → 200
GET
/v2/experiment/{experimentId}/should-run-evaluators
Should run evaluators
ShouldRunEvaluators 1 param → 200
GET
/v2/experiment/{experimentId}/{promptVersionId}/scores
Get experiment prompt version scores
GetExperimentPromptVersionScores 2 params → 200
GET
/v2/experiment/{experimentId}/{requestId}/{scoreKey}
Get experiment score
GetExperimentScore 3 params → 200
POST
/v1/experiment/new-empty
Create new empty experiment
CreateNewEmptyExperiment body → 200
POST
/v1/experiment/table/new
Create new experiment table
CreateNewExperimentTable body → 200
POST
/v1/experiment/table/{experimentTableId}/query
Get experiment table by id
GetExperimentTableById 1 param → 200
POST
/v1/experiment/table/{experimentTableId}/metadata/query
Get experiment table metadata
GetExperimentTableMetadata 1 param → 200
POST
/v1/experiment/tables/query
Get experiment tables
GetExperimentTables → 200
POST
/v1/experiment/table/{experimentTableId}/cell
Create experiment cell
CreateExperimentCell 1 param body → 200
PATCH
/v1/experiment/table/{experimentTableId}/cell
Update experiment cell
UpdateExperimentCell 1 param body → 200
POST
/v1/experiment/table/{experimentTableId}/column
Create experiment column
CreateExperimentColumn 1 param body → 200
POST
/v1/experiment/table/{experimentTableId}/row/new
Create experiment table row
CreateExperimentTableRow 1 param body → 200
DELETE
/v1/experiment/table/{experimentTableId}/row/{rowIndex}
Delete experiment table row
DeleteExperimentTableRow 2 params → 200
POST
/v1/experiment/table/{experimentTableId}/row/insert/batch
Create experiment table row with cells batch
CreateExperimentTableRowWithCellsBatch 1 param body → 200
POST
/v1/experiment/update-meta
Update experiment meta
UpdateExperimentMeta body → 200
POST
/v1/experiment
Create new experiment old
CreateNewExperimentOld body → 200
POST
/v1/experiment/hypothesis
Create new experiment hypothesis
CreateNewExperimentHypothesis body → 200
POST
/v1/experiment/hypothesis/{hypothesisId}/scores/query
Get experiment hypothesis scores
GetExperimentHypothesisScores 1 param → 200
GET
/v1/experiment/{experimentId}/evaluators
Get experiment evaluators
getV1ExperimentByExperimentIdEvaluators 1 param → 200
POST
/v1/experiment/{experimentId}/evaluators
Create experiment evaluator old
CreateExperimentEvaluatorOld 1 param body → 200
POST
/v1/experiment/{experimentId}/evaluators/run
Run experiment evaluators old
RunExperimentEvaluatorsOld 1 param → 200
DELETE
/v1/experiment/{experimentId}/evaluators/{evaluatorId}
Delete experiment evaluator old
DeleteExperimentEvaluatorOld 2 params → 200
POST
/v1/experiment/query
Get experiments old
GetExperimentsOld body → 200

Schemas 72

The contract defines 72 schemas that model the data the API accepts and returns. The most detailed are ExperimentV2PromptVersion (11 properties), PromptVersionResult (11 properties), EvaluatorResult (9 properties), Experiment (8 properties). Each schema is shown below with its type and property counts.

ResultSuccess_ExperimentTable_
object
2 properties 2 required
Result__tableId-string--experimentId-string_.string_
Result_Experiment-Array.string_
ExperimentDatasetRow
object
5 properties 5 required
Result_ExtendedExperimentData.string_
ResultSuccess_ExperimentTableSimplified_
object
2 properties 2 required
Result_ExperimentTableSimplified.string_
ExtendedExperimentData
object
7 properties 7 required
PromptVersionResult
object
11 properties 8 required
FilterLeafSubset_experiment_
Result_string.string_
Result__experimentId-string_.string_
Result_ScoreV2-or-null.string_
Record_string.string_
object
Construct a type with a set of properties K of type T
Record_string.ScoreV2_
object
Construct a type with a set of properties K of type T
CreateNewPromptVersionForExperimentParams
object
6 properties 2 required
Result_EvaluatorResult-Array.string_
Result_Record_string.ScoreV2_.string_
Partial_TextOperators_
object
Make all properties in T optional
6 properties
Result_ExperimentTableSimplified-Array.string_
Pick_FilterLeaf.experiment_
object
From T, pick a set of properties whose keys are in the union K
1 property
Result_PromptVersionResult.string_
ExperimentV2
object
6 properties 6 required
Result_ExperimentTable.string_
ExperimentTableSimplified
object
6 properties 5 required
ResultSuccess_null_
object
2 properties 2 required
ExperimentFilterBranch
object
3 properties 3 required
ResultSuccess_ExperimentTableSimplified-Array_
object
2 properties 2 required
Result_boolean.string_
ResultSuccess_string-Array_
object
2 properties 2 required
ResultSuccess_ExtendedExperimentData_
object
2 properties 2 required
ResultSuccess_Record_string.ScoreV2__
object
2 properties 2 required
ResultError_string_
object
2 properties 2 required
ExperimentTable
object
5 properties 4 required
ExperimentV2Row
object
5 properties 5 required
ResultSuccess_ExperimentV2PromptVersion-Array_
object
2 properties 2 required
ResponseObj
object
8 properties 8 required
ScoreV2
object
4 properties 4 required
ExperimentV2PromptVersion
object
11 properties 11 required
Record_string.any_
object
Construct a type with a set of properties K of type T
Result__hypothesisId-string_.string_
ExperimentFilterNode
Partial_ExperimentToOperators_
object
Make all properties in T optional
2 properties
ResultSuccess__experimentId-string__
object
2 properties 2 required
NewExperimentParams
object
5 properties 4 required
ExperimentV2Output
object
6 properties 6 required
ResultSuccess__tableId-string--experimentId-string__
object
2 properties 2 required
EvaluatorResult
object
9 properties 9 required
ResultSuccess_string_
object
2 properties 2 required
ExperimentScores
object
2 properties 2 required
IncludeExperimentKeys
object
4 properties
CreateExperimentTableParams
object
7 properties 6 required
Experiment
object
8 properties 8 required
ResultSuccess_ExperimentV2-Array_
object
2 properties 2 required
Result_string-Array.string_
Result_ExperimentV2-Array.string_
ExperimentTableColumn
object
6 properties 4 required
RequestObj
object
2 properties 2 required
ResultSuccess_PromptVersionResult_
object
2 properties 2 required
Result__runsCount-number--scores-Record_string.Score__.string_
ResultSuccess_unknown_
object
2 properties 2 required
Result_ExperimentV2PromptVersion-Array.string_
ResultSuccess_EvaluatorResult-Array_
object
2 properties 2 required
Result_null.string_
ResultSuccess__runsCount-number--scores-Record_string.Score___
object
2 properties 2 required
Json
ResultSuccess_Experiment-Array_
object
2 properties 2 required
Record_string.Score_
object
Construct a type with a set of properties K of type T
ResultSuccess__hypothesisId-string__
object
2 properties 2 required
ResultSuccess_boolean_
object
2 properties 2 required
Score
object
2 properties 2 required
ResultSuccess_ScoreV2-or-null_
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

helicone-experiment-api-openapi.yml Raw ↑

Other APIs Helicone publishes across the network.

Helicone Agent API
Helicone API Key API
Helicone Comparison API
Helicone Credits API
Helicone Customer API
Helicone Dashboard API
Helicone Dataset API
Helicone Evals API
Helicone Evaluator API
Helicone HeliconeSql API
Helicone Integration API
Helicone Metrics API
Where this information came from

This is an independent, third-party profile of Helicone Experiment 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.