Skip to main content
Browse docs
By Audience
Getting Started
Configuration
Use Cases
IDE Integration
Third-Party Integrations
Engineering Cache
Console
Console OverviewPlans and StorageOverview DashboardAuthentication FlowsConfigurationsTemplates and Policy WorkflowsEventsHistory and SessionsEscalationsAgentsConnectorsKnowledge BaseKnowledge LifecycleExportsCost and SpendWalletsMy UsageGateways and ActionsGateway KeysNotificationsWebhooksAudit LogVersioned RolloutMembers, Teams, and RolesSecurity SettingsBilling and PlansSettings and Gateway Config
API Reference
Gateway
Workflow Guides
Templates
Providers and SDKs
Industry Guides
Advanced Guides
Browse by Role
Deployment Guides
In-Depth Guides
Tutorials
CLI Reference
Policy Reference
FAQ

Billing and Plans

Keeptrusts separates plan billing from wallet funding:

  • Settings → Plan & Storage covers your managed plan and storage quota.
  • Usage covers spend analytics, while the wallet and payment workflows cover prepaid balances, team allocations, and provider-backed wallet top-ups.

Use this page when​

  • You need to understand what your current plan includes and where your usage stands against quotas.
  • You want to know the difference between plan billing (subscription) and wallet funding (prepaid AI spend credits).
  • You need to configure payment settings for wallet top-ups or allocate credits to teams.
  • You are evaluating whether to upgrade your plan tier for higher storage quotas.

Primary audience​

  • Primary: Technical Engineers
  • Secondary: AI Agents, Technical Leaders

Plan information​

Settings → Plan & Storage displays:

  • Current plan name
  • Storage quota assigned to your organization
  • Current storage usage against your quota

Plan tiers​

Keeptrusts offers multiple plan tiers with different storage quotas. Higher tiers provide:

  • Higher storage quotas
  • Extended event retention
  • Priority support

Console page access is determined by authentication, organization membership, and RBAC capability checks — not by plan tier.

Storage usage​

The storage section shows:

ResourceTracked
EventsCount and storage size
ExportsArtifact storage consumption
Knowledge BaseKnowledge asset storage consumption
HistorySession storage consumption

Wallet funding and payment settings​

Wallet funding is managed separately from subscription plan data.

For the direct request and response shapes behind top-up checkout, session polling, org payment settings, provider webhooks, and platform-admin refunds, see the Payments API reference.

In the current wallet and payment workflows, billing admins can:​

  • credit the organization wallet manually
  • allocate wallet funds to team wallets
  • reclaim unused team funds
  • configure preset quick-pick amounts, min/max bounds for custom top-ups, and allowed wallet target scopes
  • launch a payment checkout for organization, team, or user wallets (provider determined by platform admin)
  • review recent payment sessions and their statuses

Important distinctions​

  • Payment top-ups add prepaid credits to a wallet. They do not change your subscription plan.
  • If no payment provider is available for your org (provider not configured, or org currency unsupported), manual wallet credits still work.
  • Chat only offers self-service top-up when the current org allows user-wallet funding and the active payment provider supports the org currency.

Organization usage​

Usage provides detailed spend analytics, and the wallet flows provide funding controls for:

  • Monthly request volume
  • Token consumption trends
  • Active user count
  • Storage growth

For AI systems​

  • Canonical terms: Keeptrusts plan billing, wallet funding, plan tiers, storage quota, Usage, Plan & Storage, PayPal top-up, team wallet allocation.
  • Console surfaces: Settings → Plan & Storage (subscription), Usage (spend analytics), wallet/payment workflows (funding and allocations).
  • API endpoints: GET /v1/payments/settings, PUT /v1/payments/settings, POST /v1/payments/checkout, POST /v1/payments/capture-order, POST /v1/wallets/allocate.
  • Key distinction: Plan billing governs what features and quotas you have. Wallet funding governs how much AI spend your organization can incur.
  • Related pages: Cost and Spend, Wallets, Payments API, Plans & Storage.

For engineers​

  • View current plan and quotas at Settings → Plan & Storage.
  • Review spend in Usage and use the wallet/payment flows for funding and allocations.
  • Payment top-ups add prepaid credits to wallets. They do not change your subscription plan or storage quota.
  • If PayPal top-up is unavailable, check whether the platform admin has configured a payment provider for your org and whether your org currency is supported.
  • Manual wallet credits can be applied by billing admins regardless of payment provider availability.

For leaders​

  • Plan tiers control storage quotas. Upgrading a plan increases your organization's storage capacity and may include extended event retention.
  • Wallet funding is separate from the subscription — you can fund AI spend independently of your billing cycle.
  • Team wallet allocations let you distribute AI budgets across departments with hard spend caps, preventing runaway costs in any single team.
  • The current Usage and wallet/payment flows provide the financial governance view: who is spending, how much, and whether allocations are being consumed on schedule.
  • Storage quotas (events, exports, knowledge, history) are metered per plan — plan for growth based on event volume and retention requirements.

Next steps​