Kobaru
  1. Guides
Kobaru
  • Kobaru.io Gateway API
    • Introduction
      • What is Kobaru?
      • Quick start
      • How x402 works
    • Integration
      • Standard x402 SDK
      • Advanced SDK
      • Transparent proxy integration
      • Direct API integration
    • Core Concepts
      • Available Chains and Assets
      • Payment schemes
      • Security
      • Usage models
    • Guides
      • Pricing your API
      • Going to Production
      • Testing with devnet
      • Bazaar discovery
    • API Reference
      • Error Handling
      • Get Supported Payment Kinds
      • Verify Payment Authorization
      • Settle Payment
    • Discovery
      • List Discovery Resources
    • Schemas
      • SupportedResponse
      • ErrorResponse
      • UnauthorizedResponse
      • RateLimitResponse
      • VerifySuccessResponse
      • VerifyErrorResponse
      • SettleSuccessResponse
      • SettleErrorResponse
      • DiscoveryResourceItem
      • ListDiscoveryResourcesResponse
  1. Guides

Pricing your API

Pricing your API#

This guide helps you set effective prices for your API. Good pricing balances value for your customers with sustainable revenue for your business.

Understanding atomic units#

USDC has 6 decimal places. Prices in Kobaru are specified in atomic units:
Price (USD)Atomic unitsAmount string
$0.0000011"1"
$0.0011,000"1000"
$0.0110,000"10000"
$0.10100,000"100000"
$1.001,000,000"1000000"
Example: To charge one-tenth of a cent ($0.001) per request, use amount: "1000".

Pricing strategies#

Per-request pricing#

Charge for each API call. This works best when:
Requests have consistent value
Usage varies widely between customers
You want simple, predictable pricing

Bundle pricing#

Sell packs of requests at a discount. This works best when:
You want to encourage larger purchases
Customers prefer predictable costs
You want to reduce transaction overhead

Time-based pricing#

Charge for a period of unlimited access. This works best when:
Customers need high-frequency access
Usage is predictable
You want to simplify billing

Pricing examples by API type#

Data APIs#

Endpoint typeSuggested priceRationale
Simple lookup0.0001−0.001Low compute, high volume
Search query0.001−0.01Moderate compute
Analytics report0.01−0.10High compute, lower volume
Real-time feed0.10−1.00/hourContinuous access

AI/ML APIs#

Endpoint typeSuggested priceRationale
Classification0.001−0.01Fast inference
Text generation0.01−0.10Variable compute
Image generation0.10−1.00High compute
Training job1.00−10.00Intensive compute

Compute APIs#

Endpoint typeSuggested priceRationale
Validation0.0001−0.001Minimal compute
Transformation0.001−0.01Moderate compute
Rendering0.01−0.10Heavy compute

Volume discounts#

Reward high-volume customers with tiered pricing:

Option 1: Larger bundles#

BundlePricePer-request cost
10 requests$0.01$0.001
100 requests$0.08$0.0008 (20% discount)
1000 requests$0.60$0.0006 (40% discount)

Option 2: Time-based tiers#

DurationPriceEffective hourly rate
1 hour$0.10$0.10/hr
24 hours$2.00$0.083/hr (17% discount)
7 days$10.00$0.059/hr (40% discount)

Competitive analysis#

Before setting prices, research comparable APIs:
1.
Find competitors - Search for APIs offering similar functionality
2.
Note their pricing - Per-request, subscription, freemium?
3.
Calculate equivalent cost - Normalize to per-request for comparison
4.
Consider your differentiators - Speed, accuracy, features, support

Example comparison#

APIPricing modelEquivalent per-request
Competitor A$50/month for 100K requests$0.0005
Competitor B$0.002 per request$0.002
Your APIPay-as-you-go micropayments$0.001
Position yourself based on value, not just price:
Lower price = Volume play, aggressive growth
Matching price = Compete on features
Higher price = Premium positioning, better service

Testing your pricing#

A/B testing approaches#

1.
Different endpoints - Price similar endpoints differently
2.
Time-based tests - Change prices and measure impact
3.
Customer segments - Offer different prices to different users

Metrics to track#

MetricWhat it tells you
Conversion rateAre prices too high?
Revenue per userAre prices too low?
Churn rateAre customers leaving?
Request volumeIs usage growing?

Common mistakes#

1. Pricing too high#

Symptom: Low conversion, abandoned transactions
Solution: Start lower and increase based on demand

2. Pricing too low#

Symptom: High volume but unprofitable
Solution: Calculate your costs and ensure margin

3. Complex pricing#

Symptom: Customer confusion, support tickets
Solution: Keep pricing simple and transparent

4. No free tier#

Symptom: Developers don't try your API
Solution: Offer devnet testing or limited free access

Quick reference#

Price conversion formula#

atomic_units = price_in_usd * 1,000,000

Common prices#

USDAtomic units
$0.0011000
$0.0055000
$0.0110000
$0.0550000
$0.10100000

Related documentation#

Usage models - Pay-per-request vs pay-per-time
Quick start - Setting up your first paid endpoint
Testing guide - Test pricing on devnet
Modified at 2026-01-04 13:56:55
Previous
Usage models
Next
Going to Production
Built with