Credyt
Real-time billing infrastructure for AI: pre-usage authorization, multi-asset wallets, and event-level profitability.
Real-timeWalletsEntitlementsBilling PortalCost Observability
Last verified: April 2026
Good fit if...
- →AI products with per-request inference costs where pre-authorization prevents runaway spend before costs are incurred
- →Solo builders and early-stage teams who need credits, auto top-up, and a billing portal without frontend engineering
- →Prepaid credit and token-economy products where customers buy balance upfront and deplete it per usage event
- →Teams implementing hybrid pricing combining subscription entitlements with usage-based overages or top-up credit pools
- →Products that need hard budget ceilings and agent spend governance to prevent unbounded AI inference bills
Pricing
- Model
- Per Monthly Active Wallet (MAW) + per-event above 1M/month
- Free tier
- Yes
- Starting price
- $0 (first 10 active wallets/month free forever, full feature access)
- Revenue %
- None
- Per customer
- $1 per Monthly Active Wallet (MAW) per month
- Per event
- $0 for first 1M events/month; $2 per million events above that
- Seat fees
- None
- Transparency
- Full
Canonical scenario — 100 customers, $2K MRR, 100K events, 5 seats
| Line item | Cost |
|---|---|
| Platform fee | $0 |
| Per customer | $90 (100 customers × $0.90 effective rate; pricing is $1/MAW with first 10 MAWs free — 90 paid wallets × $1) |
| Seat fees | $0 (no seat fees) |
| Event fees | $0 (100K events within the 1M/month free allowance) |
| Revenue % | $0 (no revenue percentage) |
| Payment processing | Pass-through |
| Total / month | $90 + pass-through PSP fees |
Credyt charges $1 per Monthly Active Wallet with the first 10 active wallets free each month. At 100 customers the effective cost is $90 (90 paid wallets × $1). Payment processing fees from Stripe (or external PSP) are passed through without markup and are not included in Credyt's charge. Event total of 100K is well within the 1M free monthly allowance. Do not express as $0.90 per wallet — the pricing is $1/MAW with 10 free.
Technical profile
| Dimension | Value |
|---|---|
| Billing model | Hybrid Hybrid: real-time wallet debit for usage events combined with subscription entitlements. Authorization happens before the work starts; the wallet is debited atomically at the moment of usage. |
| Usage authorization | Pre-usage |
| Usage tracking | Real-time metering + immediate debit |
| Wallet architecture | First-class primitive |
| Multi-asset support | Native |
| Payment processing | Built-in Built-in via Stripe with no markup on Stripe's standard fees. External PSPs are supported through the Adjustments API — the platform reflects balance changes in Credyt without a direct Credyt integration to the PSP. |
| PSP agnostic | Partial Stripe is the built-in default; external PSPs are supported via the Adjustments API rather than a direct native integration. Not fully PSP-agnostic. |
| Customer portal | Drop-in |
| Auto top-up | Customer-controlled |
| Integration model | Extends existing stack |
| Profitability analytics | Event-level |
| Open source | No |
| License | Proprietary |
| Deployment | Cloud only |
| Enterprise contracts | Not supported Volume pricing is negotiable for large wallet counts (contact info@credyt.ai); no formal contract tooling, commit management, or enterprise contract machinery is built into the platform. |
| Pricing models | Per-unit, Tiered, Volume, Subscription, Hybrid (subscription + usage), Prepaid credits / wallet, Outcome-based, Dimensional |
Strengths
- +Pre-usage wallet authorization prevents margin loss before AI inference costs are incurred
- +Multi-asset wallets hold USD, tokens, GPU hours, credits, and custom units in one customer wallet
- +Drop-in branded billing portal with live balances, usage history, and self-service top-up; no frontend engineering required
- +Event-level cost attribution tracks profitability per customer, per feature, and per workload
- +MCP server connects to Cursor, Windsurf, Claude Code, Codex, Lovable, Bolt, Replit, and V0 for one-prompt billing setup
- +Flat per-wallet pricing with no revenue percentage, no PSP markup, and no seat fees
Limitations
- −Cloud-hosted only — no self-hosted or on-premises deployment option
- −Proprietary platform; not open source unlike Lago or Flexprice
- −No enterprise contract tooling; large volumes can negotiate custom pricing but there is no formal contract management layer
- −PSP-agnostic only in partial sense; non-Stripe PSPs require manual Adjustments API integration rather than a native connector
- −Not a drop-in replacement for invoice-based subscription billing systems such as Stripe Billing or Zuora
- −Does not process payments directly — depends on Stripe or an external PSP for payment collection
Not ideal for
- ×Traditional SaaS with monthly invoice cycles and no real-time infrastructure cost to authorize or control
- ×Enterprise teams that require formal contract management, quarterly commits, and complex invoicing workflows
- ×Teams requiring self-hosted or on-premises deployment for compliance or data residency reasons
- ×Companies that need a single platform to fully replace their payment processor and finance stack
- ×High-volume invoice-based usage billing at enterprise scale where platforms like Orb or Metronome are purpose-built
Similar providers
Company
- Founded
- 2025
- Headquarters
- San Francisco, CA, USA
- Funding
- $4.55M seed