Echo
Open-source user-pays LLM inference SDK — your users pay per token, you never front the AI bill.
Echo's 5-line Vercel AI SDK swap and 2.5%-on-profits-only fee mean an indie dev can test user-pays billing with almost no downside. The tradeoff is structural: your users see the meter, so anyone who wants AI costs buried in a subscription should look elsewhere. For consumer AI apps with unpredictable power users, it's an unusually clean risk reversal.
Verified 19m ago · liveness 68/100 · cite: rightaichoice.com/tools/echo
- Indie developers without capital to front provider API bills
- SaaS founders who want per-user AI billing without building the stack
- Open-source AI tool creators looking for a monetization path
- Next.js and React developers adding AI to an existing app
- Enterprises needing data residency, custom SLAs, or procurement contracts
- Products where users can't reasonably be asked to pay per use
- Apps requiring offline or on-premise model inference
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Echo if your users can't or won't pay for their own AI usage — internal tools, enterprise deployments, and products sold on unlimited free AI are all a bad fit for a user-pays meter.
Echo takes 2.5% of your profits, so your effective margin shrinks on every markup you set — free only until you start earning.
Echo's pricing is unusually light: the SDK is free and MIT-licensed, and the only vendor fee is 2.5% of profits. That undercuts usage-based gateway billing products, which typically charge on every call whether or not you make money. It fits indie developers and small SaaS teams best. Larger teams comparing against direct provider contracts should weigh the 2.5% cut against committed-spend discounts, and enterprises needing SLAs or data residency will find no tier here at all.
In short
Echo — Open-source user-pays LLM inference SDK — your users pay per token, you never front the AI bill. Best for Indie developers without capital to front provider API bills, SaaS founders who want per-user AI billing without building the stack, Open-source AI tool creators looking for a monetization path. Free to use.
What people actually say about Echo — is it worth it?
We scanned public community sources for Echo on Aug 30, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Our own analysis of that scan says the posts were off-subject. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
Viability Score
How well maintained and how widely used is Echo? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- User-pays LLM inference billed per token to your end users
- 5-line migration from the Vercel AI SDK to production
- Drop-in Echo Sign-In auth component with login, balance, and top-ups
- Unified gateway serving OpenAI, Anthropic, and Google Gemini
- Configurable markup that turns every consumed token into revenue
- No API keys, metering layer, or Stripe integration required
- Universal balance shared across all Echo-powered apps
- Next.js SDK with server-side auth and automatic token management
- React SDK using OAuth2 + PKCE for client-side LLM calls
- TypeScript SDK with API keys for backends and CLI tools
- echo-start CLI scaffolding for Next.js, React, Assistant UI, and CLI
- Templates for chat, image generation, video, and server-side API key apps
- Sponsor free tier for new users
- Dashboard tracking profit, token spend, and transactions
- Open-source and free under the merit-systems/echo GitHub repo
About Echo
Echo is an open-source SDK from Merit Systems that reverses who pays for AI features. Instead of absorbing the OpenAI, Anthropic, or Google Gemini bill yourself, your users fund their own token spend through a managed sign-in component with login, balance, and top-ups. Integration is deliberately small: the vendor describes changing five lines from the Vercel AI SDK and going to production, with no API keys, no metering layer, and no Stripe wiring to maintain. Requests route through Echo's unified gateway, which serves all frontier models behind a single account. Set a markup and every token a user consumes becomes revenue, tracked in a dashboard that reports profit, token spend, and transactions — the site's own demo numbers show $814.63 profit on 1.63M tokens and 1.69K transactions. Balances are shared across every Echo-powered app, so a user pays once and carries that balance everywhere. SDKs cover Next.js with server-side auth, React with OAuth2 + PKCE for client-side calls, and TypeScript with API keys for backends and CLI tools. The echo-start CLI scaffolds Next.js, React, Assistant UI, and chat, image, and video templates. You can also sponsor a free tier for new users so they try your app before spending. Echo suits indie developers and small SaaS teams who want per-user AI billing without building a billing stack. It's a different bet from gateway markup tools that still leave you holding the invoice — here the meter is visible to your end users, which is the point and the limitation.
Behind the Verdict
The interesting thing about Echo isn't the gateway — plenty of tools proxy models. It's that Merit Systems moved the paywall from you to your users, and built the auth, balance, top-up, and settlement plumbing so you don't have to. Pick this when your AI feature has power users whose token spend you can't forecast. That's the classic indie trap: a free tier that a handful of heavy users turn into a monthly bill you can't cover. Echo converts that liability into a configurable markup. Pass if your users can't be asked to pay — enterprise buyers, internal tools, or anything where a visible balance destroys the experience. Products needing offline or on-premise inference are out too. Compared with a plain model gateway that bills you, Echo's real difference is the balance layer and shared universal balance across apps. Compared with building usage-based billing yourself, the 5-line swap is the selling point, plus no API keys or metering to maintain. In practice, plan your UX around top-ups. Users hitting a zero balance mid-task is the failure mode, and the sponsor free tier is the mitigation the vendor hands you. One caveat worth flagging: our pricing page fetch failed, so we're reporting fees from the vendor's own site copy (2.5% on profits, no fees by default, free and OSS) rather than a retrieved tier table. Confirm current terms before you commit.
Researching Echo? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas Echo actually fits — and what changes day-one when you adopt it.
Runs npx echo-start@latest --template next to scaffold a project, swaps the AI SDK call for Echo, and drops in the Sign-In component.
Outcome: Users top up their own balance before chatting, so the developer ships AI features without putting a card on file with a model provider.
Sets a 50% markup in Echo and watches the dashboard's profit, token spend, and transaction figures as usage grows.
Outcome: Heavy users fund their own inference and the margin shows up as revenue instead of an escalating monthly bill.
Publishes the repo on GitHub and points contributors at Echo for inference, keeping the code MIT-licensed and self-hostable.
Outcome: The project earns on every token consumed through it without adding a paid tier or a donation ask.
Use Cases
- Ship a chatbot where each user funds their own messages instead of you covering API costs.
- Add image generation to an app and let users buy their own image credits.
- Run a coding assistant where users pay per token based on actual usage.
- Replace the Vercel AI SDK in an existing Next.js app to shift billing to end users.
- Offer a free tier you sponsor while heavy users pay their own way.
- Monetize an open-source AI tool by letting users pay directly for inference.
- Use the CLI template to build terminal AI chat with API keys and crypto wallets.
- Set a markup so every token consumed in your app produces profit.
Models Under the Hood
as of 2026-09-25
Limitations
- Echo is an SDK you integrate into an existing app rather than a standalone hosted product, and the documented SDKs cover Next.js, React, and TypeScript, with docs and templates focused on Next.js and React.
- Because end users fund their own inference usage, the model suits consumer-facing products where asking users to pay is acceptable.
- The site states no fees by default with a 2.5% fee on profits, and documents no enterprise SLA, data residency, or on-premise option.
- Agent runtime details beyond the core SDK are not documented in the provided evidence.
as of 2026-09-14
Verification history
We have re-verified Echo 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 7 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published Echo tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free & Open Source
$0/mo
Ideal for
Indie developers, SaaS founders, and open-source maintainers who want users to fund their own LLM inference instead of fronting provider bills.
What this tier adds
Free entry point: MIT-licensed SDK with managed auth, a 100+ model gateway, and 2.5% fees only on the profits you earn.
Where the pricing makes sense
The company stage and team size where Echo's pricing actually pencils out — and where peers do it cheaper.
Echo's pricing is unusually light: the SDK is free and MIT-licensed, and the only vendor fee is 2.5% of profits. That undercuts usage-based gateway billing products, which typically charge on every call whether or not you make money. It fits indie developers and small SaaS teams best. Larger teams comparing against direct provider contracts should weigh the 2.5% cut against committed-spend discounts, and enterprises needing SLAs or data residency will find no tier here at all.
Setup time & first value
How long it actually takes to get something useful out of Echo — broken out by persona, not the marketing-page minute.
For a new Next.js app, the echo-start CLI scaffolds a pre-configured project, so a working Echo integration is minutes of work. Adding Echo to an existing Next.js or React app means swapping roughly five lines from the Vercel AI SDK and adding the Sign-In component — an afternoon for a comfortable developer. Working outside those frameworks via the TypeScript SDK takes longer, since you build the
Switching to or from Echo
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From the Vercel AI SDK: change roughly five lines of code and add the Echo Sign-In component so requests route through Echo and users pay.
- →From rolling your own Stripe billing: drop the custom metering and Stripe integration entirely and let Echo handle auth, balance, and top-ups.
- →From a donated or free open-source project: attach Echo so users fund inference directly instead of relying on maintainer sponsorship.
- ↗To direct provider contracts: swap the Echo SDK back for the provider SDK, re-issue your own API keys, and rebuild per-user auth, metering, and billing.
- ↗To a self-hosted deployment: pull the MIT-licensed Echo codebase from GitHub and run it yourself rather than using the managed service.
Integrations
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “Echo”, and we withheld 6: 6 could not be judged, because “Echo” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Echo.
Official links
Tools that pair well with Echo
Common stack mates teams adopt alongside Echo, with the specific reason each pairing earns its keep.
OrcaRouter
One OpenAI-compatible endpoint in front of 200+ models, with per-prompt grading that routes each call — and no markup on tokens.
Crazyrouter
One OpenAI-compatible API key for 600+ AI models with cost-optimized routing and pay-as-you-go billing
Netlify AI Gateway
Netlify's built-in inference proxy: call OpenAI, Anthropic, Gemini, and OpenRouter models from Netlify code without managing API keys.
Featured Head-to-Head Comparisons
Echo vs Spider Cloud
Spider Cloud and Echo solve completely different problems. If you need to efficiently scrape web data for AI/LLM pipelines, Spider Cloud's Rust engine and low per-page cost ($0.03/1k pages) are hard to beat. If you're building an AI app and want to avoid upfront inference costs, Echo's user-pays model and drop-in SDK eliminate billing complexity. Choose based on your data source needs versus funding model.
Echo vs Voyage Ai
If your priority is retrieval accuracy for enterprise RAG on specialized data like finance or legal, Voyage AI’s domain-specific embeddings and rerankers are unmatched. But if you’re an indie developer or small SaaS wanting to offer AI features without upfront API costs, Echo’s user-pays model eliminates financial risk — though you’ll need to accept its open-ended, less-compliant nature. Choose the tool that fits your business model and data sensitivity.
Echo vs Temporal Ai
If you need rock-solid durability for AI agents or multi-step processes that survive any crash, Temporal is the clear choice – it’s trusted by OpenAI and Cursor for good reason. But if you’re an indie developer or SaaS founder looking to ship AI features without paying upfront for inference, Echo flips the cost model brilliantly, letting users pay directly. Pick Temporal for resilience; pick Echo for cost-free experimentation.
Alternatives to Echo
View all
OrcaRouter
One OpenAI-compatible endpoint in front of 200+ models, with per-prompt grading that routes each call — and no markup on tokens.
Crazyrouter
One OpenAI-compatible API key for 600+ AI models with cost-optimized routing and pay-as-you-go billing
Netlify AI Gateway
Netlify's built-in inference proxy: call OpenAI, Anthropic, Gemini, and OpenRouter models from Netlify code without managing API keys.
Frequently Asked Questions
Used Echo? Help shape our editorial sentiment research.