Blog
Notes on building an AI API marketplace
Reliability, pricing, routing, and the trust signals behind every call routed through Onlist.
How to use Claude Code with Onlist
Point Claude Code at Onlist with two environment variables: no local proxy, competing providers for the same models, wallet billing, and full usage logs.
You can't review a provider you haven't paid
Every review on Onlist requires at least one billed API call with that provider. How the payment gate works, what shows next to each review, and what it still cannot fix.
Chat: same models, same prices, in the browser
Web chat on Onlist runs through the same billing pipeline as the API: same listings, same prices, same wallet. What it supports today and what it does not do yet.
Onlist vs OpenRouter: When to use which
A practical, non-marketing comparison of two AI API gateways covering pricing model, provider routing, reviews, and migration.
How we score AI provider reliability
The layered trust signal model behind every routing decision on Onlist: objective fulfillment, automated checks, and real-usage reviews.
Why prepaid wallets fit AI APIs better than subscriptions
AI calls have variable per-request cost. Subscriptions misprice the long tail and lock users into wasted commitment. Prepaid wallets fit better.