Skip to content

Credits System

Understanding how Civra's credit system works.

Overview

Civra uses a credit-based system to manage usage fairly across all users. Credits ensure platform stability and allow us to provide high-quality AI and infrastructure services.

Credit Types

1. Message Credits

Used for AI-powered code generation and chat interactions.

Cost: 1 credit per action

What uses message credits:

  • 🤖 Initial project generation
  • 💬 Each chat message/modification
  • 🐛 Debugging requests
  • 📝 Code explanations
  • ♻️ Refactoring requests
  • 🔍 Code reviews

Example workflow:

Create NFT marketplace (1 credit)
→ Add wallet connection (1 credit)
→ Fix styling issue (1 credit)
→ Add dark mode (1 credit)
→ Optimize gas usage (1 credit)
= 5 message credits total

2. Integration Credits

Used for blockchain interactions, external APIs, and infrastructure operations.

Variable cost based on operation

What uses integration credits:

OperationCost
Blockchain RPC call1-5 credits
Smart contract deployment10 credits
Transaction simulation2 credits
NFT metadata fetch1 credit
IPFS file upload5 credits
Oracle price feed1 credit
Wallet balance check1 credit
Gas estimation1 credit
Contract verification5 credits
Subgraph query2 credits

Example DeFi deployment:

Deploy token contract (10 credits)
→ Verify on Etherscan (5 credits)
→ Add liquidity to DEX (5 credits)
→ Test swap functionality (3 credits)
= 23 integration credits total

Credit Allocation by Plan

PlanMessage CreditsIntegration CreditsMonthly Cost
Free10100$0
Starter1002,000$16
Builder25010,000$40
Pro50020,000$80
Elite1,20050,000$160

How Credits Work

1. Pre-Flight Checks

Before any operation, Civra checks if you have sufficient credits.

typescript
// Example: Before generating code
if (userMessageCredits < 1) {
  → Show "Insufficient credits" message
  → Suggest upgrading plan
  → Block operation
}

2. Atomic Deduction

Credits are deducted atomically to prevent double-charging.

typescript
// Guaranteed single deduction
BEGIN TRANSACTION
  → Check credits available
  → Deduct credits
  → Perform operation
  → Log transaction
COMMIT

3. Transaction Logging

Every credit usage is logged for transparency.

Transaction log includes:

  • Timestamp
  • Credit type (message/integration)
  • Amount deducted
  • Operation performed
  • Project ID
  • Success/failure status

4. Monthly Reset

Credits automatically reset on your billing date.

Billing date: 15th of each month
Current: Oct 15, 2024
Credits reset: Nov 15, 2024

Unused credits do NOT roll over.

Monitoring Your Usage

Real-Time Balance

Check your current balance anytime:

Dashboard → Usage Tab

Message Credits: 47/100 (47% remaining)
Integration Credits: 1,234/2,000 (62% remaining)

Usage Alerts

Get notified at key thresholds:

80% Used:

⚠️ You've used 80% of your message credits.
Consider upgrading to avoid interruptions.

90% Used:

🚨 Only 10% of your credits remaining!
Upgrade now to continue building.

100% Used:

❌ You've exhausted your credits.
Please upgrade to continue.
[View Plans]

Detailed History

View complete usage history:

  1. Go to SettingsUsageHistory
  2. Filter by:
    • Date range
    • Credit type
    • Project
    • Operation type
  3. Export as CSV for analysis

Example history:

Oct 20, 3:45 PM | Message | -1 | "Create staking UI" | Success
Oct 20, 3:47 PM | Integration | -10 | "Deploy contract" | Success
Oct 20, 3:50 PM | Integration | -5 | "Verify contract" | Success
Oct 20, 4:12 PM | Message | -1 | "Add dark mode" | Success

Optimizing Credit Usage

Message Credits

✅ Efficient:

Create a complete NFT marketplace with minting,
listing, and buying functionality
(1 credit for comprehensive request)

❌ Inefficient:

Create NFT contract (1 credit)
→ Add minting (1 credit)
→ Add listing (1 credit)
→ Add buying (1 credit)
(4 credits for same result)

Tips:

  • Combine requests when possible
  • Be specific in initial prompts
  • Use Prompt Library
  • Plan features before requesting

Integration Credits

✅ Efficient:

// Batch operations
estimateGasForMultiple([tx1, tx2, tx3])
(1 credit instead of 3)

❌ Inefficient:

// Individual calls
estimateGas(tx1) // 1 credit
estimateGas(tx2) // 1 credit
estimateGas(tx3) // 1 credit

Tips:

  • Use testnet for development (free)
  • Batch RPC calls when possible
  • Cache data locally
  • Use webhooks instead of polling

Credit Scenarios

Scenario 1: Building NFT Marketplace (Starter Plan)

Message Credits Used:

  • Initial generation: 1
  • Add wallet connection: 1
  • Create listing page: 1
  • Add bidding system: 1
  • Style improvements: 1
  • Bug fixes: 2
  • Total: 7 credits

Integration Credits Used:

  • Deploy NFT contract: 10
  • Deploy marketplace: 10
  • Verify contracts: 10
  • Test minting: 5
  • Test listings: 5
  • IPFS uploads (3 images): 15
  • Total: 55 credits

Result: Well within Starter plan limits (100/2000)

Scenario 2: DeFi Protocol (Builder Plan)

Message Credits Used:

  • Token contract: 1
  • Staking contract: 1
  • Liquidity pool: 1
  • Frontend interface: 1
  • Dashboard: 1
  • 15 modifications/fixes: 15
  • Total: 20 credits

Integration Credits Used:

  • Deploy 3 contracts: 30
  • Verify contracts: 15
  • Add liquidity: 10
  • 50 test transactions: 100
  • Oracle integration: 20
  • Subgraph queries: 30
  • Total: 205 credits

Result: Comfortable in Builder plan (250/10,000)

Scenario 3: DAO Platform (Pro Plan)

Message Credits Used:

  • Governance token: 1
  • Voting contract: 1
  • Treasury: 1
  • Timelock: 1
  • Frontend: 1
  • 50+ modifications: 50
  • Documentation: 5
  • Total: 60 credits

Integration Credits Used:

  • Deploy 5 contracts: 50
  • Verify all: 25
  • 200 governance tests: 400
  • Snapshot integration: 50
  • Multiple chain deployments: 100
  • Total: 625 credits

Result: Fits in Pro plan (500/20,000)

What Happens When Credits Run Out

1. Immediate Notification

🚨 Credits Exhausted

You've used all your message credits for this month.

Options:
→ Upgrade Plan (instant credits)
→ Wait for reset (Nov 15, 2024)
→ Contact sales for add-ons

2. Graceful Degradation

  • ✅ View existing projects
  • ✅ Browse code
  • ✅ Export projects
  • ✅ Access documentation
  • ❌ Generate new code
  • ❌ Modify existing code
  • ❌ Deploy contracts

3. Upgrade Options

Click "Upgrade" for immediate access:

  • Instant credit top-up
  • Pro-rated billing
  • No feature interruption

Credit Sharing (Team Plans)

Pro and Elite plans support team credit sharing:

How It Works

Pro Plan: 500 message credits shared among 5 members

Member A uses: 150 credits
Member B uses: 100 credits
Member C uses: 50 credits
Members D & E: 200 credits total

Remaining: 0 credits (exhausted)

Team Alerts

Admins get notified when:

  • Team uses 80% of credits
  • Individual member uses >30% alone
  • Credits exhausted

Credit Allocation (Elite)

Elite plans can allocate credits per member:

Total: 1,200 message credits

Member A (Lead Dev): 400 credits
Member B (Frontend): 300 credits
Member C (Backend): 300 credits
Team Pool: 200 credits

Credit Add-ons (Coming Soon)

Purchase extra credits without upgrading:

One-Time Packs

Message Credits:

  • 50 credits - $10
  • 100 credits - $18 (10% off)
  • 250 credits - $40 (20% off)

Integration Credits:

  • 1,000 credits - $5
  • 5,000 credits - $20 (20% off)
  • 10,000 credits - $35 (30% off)

How Add-ons Work

  • Purchased separately from plan
  • Never expire (until used)
  • Stack with monthly credits
  • Used after monthly credits

Enterprise Credit Management

Elite plans include advanced features:

Custom Limits

  • Negotiated credit pools
  • Rollover options available
  • Volume discounts

Advanced Analytics

  • Per-project breakdowns
  • Team member usage
  • Cost forecasting
  • Budget alerts

Priority Support

  • Dedicated credit manager
  • Usage optimization consulting
  • Custom credit rules

FAQs

Do unused credits roll over?

No, credits reset monthly and don't roll over. This keeps pricing fair for all users.

Can I purchase credits separately?

Credit add-ons are coming soon. For now, upgrade your plan for more credits.

What if I need more than Elite plan?

Contact enterprise@civra.dev for custom pricing.

How are credits refunded?

Unused credits from canceled plans aren't refunded, but you keep them until period end.

Can I gift credits?

Not currently, but team plans allow credit sharing.

Are testnet operations free?

Testnet blockchain interactions use integration credits, but at reduced rates (50% off).

Best Practices

  1. Plan ahead - Outline features before building
  2. Be specific - Detailed prompts save credits
  3. Test on testnet - Cheaper than mainnet
  4. Batch operations - Combine when possible
  5. Monitor usage - Check dashboard regularly
  6. Set alerts - Get warned before running out
  7. Upgrade proactively - Don't wait until exhausted

Next Steps

Built with Civra - Web3 Development Platform