/**
 * This file was auto-generated by Fern from our API Definition.
 */
import * as environments from "../../../../environments";
import * as core from "../../../../core";
import { Scale } from "../../../..";
export declare namespace Projects {
    interface Options {
        environment?: environments.ScaleEnvironment | string;
        token?: core.Supplier<core.BearerToken | undefined>;
    }
}
export declare class Projects {
    private readonly options;
    constructor(options: Projects.Options);
    /**
     * List information for all projects. **Note:** No parameters required. Optionally, set a boolean value for `archived` to only list information for all (un)archived projects.
     */
    list(request?: Scale.ListProjectsRequest): Promise<Scale.Project[]>;
    /**
     *
     */
    create(request: Scale.CreateProjectRequest): Promise<Scale.Project>;
    /**
     * Retrieve information about a single project.
     */
    get(name: string): Promise<Scale.Project>;
    /**
     * You can set parameters on a project. Project-level-parameters will be set on future tasks created under this project if they are not set in the task request. Any parameters specified in the task request will override any project parameter. Projects keep a history of the parameters that they were set with. Tasks created under a project inherit the latest params of the project (the last entry in param_history), one can also specify project_version when creating a task to inherit from an older set of params (or use -1 to skip parameter inheritance altogether.) Tasks have a `project_param_version` field pointing to the project version in place at the time a task was created. If you haven't already, check out our [guide to using Project-level parameters](/reference/using-project-versioning) to learn more about how this workflow comes togeher. Just want to see some examples? [We've added those as well](/reference/examples-of-project-parameters).
     */
    updateParameters(name: string, request?: Scale.UpdateProjectParametersRequest): Promise<Scale.Project>;
    /**
     * You can set ontologies on a project. Ontologies will be referenced by the tasks of a project. Projects keep a history of the ontologies they were set with. The ontology can be composed of a list of strings or [OntologyChoice](/reference/ontology-nesting-and-options) objects. Ontology choices and their subchoices must be unique throughout the ontology.
     */
    setOntology(name: string, request: Scale.SetOntologyRequest): Promise<void>;
}