Small, working Replit templates that call paid APIs through TaskFuel.
Each one opens in Replit with a single click, runs on your own key, and costs cents per use. No provider accounts, no per-API keys, no subscriptions.
Type one brief. It goes to four image models at once and you get four takes back, each labelled with the price it actually charged. Around 48 cents for the set.
Every paid call goes to one endpoint. TaskFuel pays the provider's HTTP-402 charge from your prepaid balance and passes the response straight back:
await fetch("https://app.taskfuel.ai/v1/call", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.TASKFUEL_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
url: "https://some-provider.example/endpoint",
method: "POST",
body: { /* the provider's own parameters */ },
maxAmountUsd: 0.25,
}),
});The response headers say what it cost (x-taskfuel-cost) and what is left
(x-taskfuel-balance). GET /v1/discover?q=... searches every provider in the
catalog, around 90 of them, covering search, market data, email, phone calls,
images and more.
Full guide: app.taskfuel.ai/building-apps.md
Get one at app.taskfuel.ai. The first $5 is on the house.
In Replit, put it in the Secrets tab as TASKFUEL_API_KEY rather than in a
file. Secrets are not copied when someone else imports your project.
These templates run on your own key, and a key can spend the whole balance with nobody watching at call time. Every showcase here sets two limits in code, and you should keep them when you adapt one:
- A per-call ceiling (
maxAmountUsd), so a single call cannot run away. - A daily budget that fails closed once it is reached.
If you make a project public and let strangers trigger paid calls, they are spending your balance. Keep the budget low, or have each visitor bring their own key.
One repo per showcase, because Replit's import URL takes a whole repository and
.replit names a single entrypoint. A repo holding several templates would
hand every importer all of them, with only one of them running.
So: create taskfuel/<showcase-name>, make it public, and add a section here
pointing at it.