Usage-based
Requests return usage metadata with credits charged, balance, operation key, and cache status.
// credits
Pay for API calls and productivity instead of adopting a fixed dashboard for every AI visibility, web intelligence, or agent workflow.
// model
Requests return usage metadata with credits charged, balance, operation key, and cache status.
Use one API key from apps, scripts, dashboards, agents, jobs, and internal tools.
Build the workflows you need instead of paying for unused static platform features.
// operations
Small checks charge 75 credits. Larger accepted checks charge 150 credits.
Search, extraction, context, and answer endpoints return usage fields in the response.
MCP tool calls are metered like normal API requests.
Use /pricing when you need a pricing-oriented entry point for the same credit-based model.
Kiodo uses credit-based API usage. Each successful metered request returns usage metadata so your app can track cost and balance.
Kiodo is API-first. You can use one API key across scripts, agents, internal tools, and product backends instead of forcing every user into a separate SaaS seat.