Skip to content

New pricing schema needed #290

@andreastande

Description

@andreastande

Some providers price requests based on the number of tokens in the prompt or the generated output, a pricing model that is becoming increasingly more common. The current pricing schema only supports fixed prices, which is insufficient for this case. A revised schema should allow prices to be defined with respect to specific token counts or token ranges to accurately reflect this pricing model.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions