Hi everyone — I’m part of the team behind Tokatlas, a commercial multi-model API platform with usage-based billing.
We’re inviting n8n builders to test how our API fits into a small, concrete workflow and help us identify integration issues.
A starting example would be:
Sample support messages → model request → category and summary → output validation → spreadsheet
The goal is to keep inputs and expected output consistent, then evaluate compatible models on the same task. Alongside answer quality, we’d like to understand authentication, request formatting, response parsing, error handling and cost per successful workflow run.
Tokatlas provides access to models from multiple providers through one platform, with a model and pricing directory and several API formats. This is an integration-testing invitation, not an announcement of a verified n8n community node or a ready-to-import workflow. The endpoint and request format need to match the model and capabilities being tested.
Set your price ceiling. Pay the matched rate.
The attached screenshot illustrates pricing: with a ceiling of 0.85× the reference rate and “Price first” selected, the example matches a route at 0.55×. Billing uses the matched rate rather than the ceiling.
At the illustrated usage of 100 million tokens per month, the estimated cost is $137.50 versus a $250 reference cost—a 45% reduction in this example. These are illustrative figures, not a fixed discount across models. Actual charges depend on the model, input/output usage and available routes.
How to participate
Our initial community trial has 20 spots in total across the communities where we’re sharing it, with API credits provided for testing. Sample or synthetic data is enough.
Email affiliates@tokatlas.com with the subject “Tokatlas Community Trial — n8n”. Briefly describe your workflow, the model or capability you want to test, and your planned n8n node or HTTP request setup, if you have one. We’ll reply with the trial scope and participation details. No positive review or repost is required.
Website: https://app.tokatlas.com
API documentation: Docs | Tokatlas
Useful feedback includes unclear setup steps, responses that are difficult to parse or validate, failure behavior, and whether usage costs are clear. Questions are welcome here; we’ll share general setup answers and useful findings back in this thread.
Screenshot: Tokatlas pricing demonstration. Figures are illustrative.
