Requesty · FinOps Profile

Requesty Finops

FinOps view of Requesty gateway spend. Requesty bills usage-based on the underlying routed model's base token rates plus a 5% routing markup, with a Free tier capped at 200 requests/day on free models. Every request returns a Requesty USD `cost` field, and per-key and organization-level usage/spend reporting supports allocation and budgeting. Caching and fallbacks reduce effective spend; BYOK shifts base model cost to the customer's own provider accounts while Requesty applies its routing fee.

Requesty Finops is the FinOps profile for Requesty on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in USD, on a monthly cycle, and pricing category usage-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include AI, LLM, Routing, Gateway, and Observability.

Category: AI and Machine Learning Pricing: Usage-Based Billing: Monthly FOCUS v1.3
AILLMRoutingGatewayObservabilityFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Requesty
PricingCategory
Usage-Based
ProviderName
Requesty
PublisherName
Requesty
ServiceCategory
AI and Machine Learning
ServiceName
Requesty Router

Meters

input_tokens
Unit: tokens
Tokens sent in routed chat/embedding requests, billed at the routed model base rate plus 5% markup.
output_tokens
Unit: tokens
Tokens generated by the routed model, billed at the base rate plus 5% markup.
routing_markup
Unit: usd
5% markup applied on top of the underlying base model cost for routed traffic.
request_cost
Unit: usd
Per-request Requesty USD cost returned in the usage.cost field of each response.
cached_requests
Unit: requests
Requests served from response cache, reducing upstream model spend.

Sources