Question 1

Which tokenizer does Recursive use?

Accepted Answer

Recursive uses its own tokenizer, which is not publicly available to run in a browser. This counter estimates counts with OpenAI's cl100k_base encoding, which is typically within roughly 10 to 20 percent of the real count for English text.

Question 2

Are these Recursive token counts exact or estimated?

Accepted Answer

Estimated. Recursive has not released its tokenizer for browser use, so this tool approximates counts with OpenAI's cl100k_base encoding. Estimates are usually close for English text but can drift for code, JSON, and non-English languages. Estimated counts are marked with a tilde (~).

Question 3

How is Recursive API cost calculated?

Accepted Answer

Cost equals tokens divided by one million, multiplied by the model's per-million-token rate. Each Recursive model has separate input and output rates, and this page shows both: what your text would cost as a prompt (input) and what the same number of tokens would cost as a response (output).

Question 4

Why do token counts matter for Recursive API costs?

Accepted Answer

Recursive bills API usage per token, not per word or character. A token is roughly 4 characters or about three quarters of a word in English. Knowing the token count of your prompts lets you predict spend, stay inside context windows, and compare Recursive models like Recursive Flint before you commit.

Recursive Token Counter

Recursive Model Pricing

Frequently Asked Questions

Related Tools