Sarpoy vs Generic LLM wrappers
Chat UI bolted to an API key
Most "AI chat" products are a Next.js app and a model API key. They have no settlement primitive at all — payments, if any, are handled by Stripe at the subscription layer, and every message is a free API call under the hood. Sarpoy meters at the message: each send_message is a priced, on-chain Anchor instruction with escrowed value behind it. The chat is a side effect of the metered program, not the other way around.
Choose Generic LLM wrappers
Pick a generic wrapper when you just want a chat surface and you have no economic relationship to model. The free-tier UX is excellent and the build cost is near zero.
Choose Sarpoy
Pick Sarpoy when money has to move per message, the pot needs to be visibly escrowed, and the verification step needs to gate a real on-chain payout.
Feature-by-feature
| Feature | Sarpoy | Generic LLM wrappers |
|---|---|---|
| Per-message accounting | Anchor instruction | None — it's just an API call |
| Escrowed prize pool | Treasury PDA | Not a concept |
| Wallet auth | Nonce + signature + JWT | Usually email/password |
| Settlement primitive | submit_solution Anchor instruction | None |
| Audit trail | Solana transaction signatures | Application database |
Technical notes
Generic LLM wrappers are great products. They are not platforms — they are chat clients.
If you find yourself adding payment hooks, refund logic, and an audit trail to your LLM wrapper, you are reinventing what Sarpoy already ships.
The Anchor program is the difference between a chat surface and a settled game.