Start with a concrete task: are you generating text, creating an image, or processing existing material? The task determines which capabilities, inputs and billing units you need to check.
This guide follows the tokvilo workflow, from a public catalogue request to account setup, a Playground trial and application integration. A model appearing in the catalogue does not guarantee that every request will succeed. Check the relevant service status before submitting.
What to take away
- Use the catalogue to identify the task and exact model first.
- Playground needs an active account, an available service and sufficient usage balance.
- Confirm the quote, submit once and retain the original request ID.
1. Narrow the choice with a concrete task
Turn “try AI” into an outcome you can inspect. For example: rewrite a product description in under 150 words, preserve the supplied facts, and return three points. A specific task makes the result easier to assess.
In the model library, choose text, image, video or audio, then browse creators and model families. Within a family, check the model name, version, supported inputs, pricing and interface details shown on the page.
- Input: text, images, audio or other material.
- Output: the required format, length and structure.
- Constraints: facts to preserve, language and delivery requirements.
2. Read the public catalogue
A catalogue request helps you check access to the site and inspect its public model information. The following request reads the catalogue without an API key. It does not run a model or generate content.
A successful response confirms only that the catalogue request worked. The endpoint and parameters for generation depend on the selected model's documentation.
curl --fail --show-error \
"https://tokvilo.com/api/model-catalog"3. Prepare your account and service usage
After registering and signing in, check your account and available usage balance in the console. The English site offers online checkout for tokvilo usage packs or enterprise bank transfer arrangements. Check the payment page and account for current online checkout availability.
For an enterprise transfer, contact support first to confirm company details, your account email, the amount and payment instructions. An administrator adds the agreed usage after verifying the bank receipt. An inquiry or a return from a payment page does not itself confirm delivery.
- Check the signed-in email so the right account receives usage.
- Review payment availability and your ledger to confirm that usage was added.
- Resolve any service configuration, account or insufficient-balance message before continuing.
4. Check parameters and a quote in Playground
Open Playground from the selected model and begin with a short input whose output you can check. Confirm the exact model ID, then fill in the required parameters. Forms and supported options vary by model and task.
Getting a quote and executing a request are separate steps. Review the amount and parameters, then confirm generation. Changes to text length, output limits, image specifications or video settings can change the quote; confirm it again after editing.
Keep the original request ID after submission. If the request is processing, check that request. A browser disconnection is also a reason to inspect its status before submitting a new copy of the same task.
5. Move the verified request into your application
Playground helps you understand inputs and outputs, while application integration also requires the API documentation. Different model types may use different protocols or an asynchronous submit-and-poll flow. Do not assume every model accepts the same request body.
Create a tokvilo API key for your application in the console. Keep it in your server environment, away from public repositories and browser code. Follow the selected endpoint's documentation for authentication, parameters, errors and task states.
Before releasing your integration, record the model, parameters, request ID, whether the output met the task, and the actual settlement shown in the console. That small acceptance record helps separate a request problem from application logic.
Begin with a task you can evaluate
Browse model families, check the capabilities and current interface status, then open the workspace.
Explore the model library ↗