Purchasing Fikra API Credits with KES
Fikra API operates on a token-credit wallet system. Developers purchase credits to fund API requests, which are then deducted based on token usage. The platform integrates with Paystack for billing, and public documentation states that M-Pesa and card payments are accepted.
Note on Payment Methods: While M-Pesa and cards are listed as accepted methods, specific payment flows, exchange rates, or minimum deposit amounts are not detailed in the public technical documentation. If you are attempting to use a specific payment method not explicitly listed (such as a direct 'OpenAI credits' purchase flow), confirm availability with Fikra support before proceeding.
Token-Credit Wallet
A token-credit wallet is a prepaid balance associated with your Fikra account. When you make an API call, the system calculates the cost based on the input and output tokens and deducts the corresponding amount from your wallet. If the balance is insufficient, the request will fail.
Account and Top-Up Flow
- Access Dashboard: Log in to the Fikra dashboard at https://fikraapi.co.ke.
- Navigate to Billing: Locate the billing or wallet section.
- Initiate Top-Up: Select the amount of credits to purchase.
- Complete Payment: Choose an available payment method (e.g., M-Pesa or Card) via the Paystack integration.
- Confirmation: Once the payment is processed, the credits are added to your wallet balance.
Monitoring Balance and Handling HTTP 402
Developers should monitor their wallet balance to avoid service interruptions. If an API request is made when the wallet balance is insufficient, the Fikra API will return an HTTP 402 (Payment Required) status code.
Best Practices: - Pre-check Balance: Query the dashboard or relevant API endpoint (if available) to check the current balance before making high-volume requests. - Handle 402 Errors: Implement error handling in your application to catch HTTP 402 responses. When this occurs, pause API calls and prompt the user or administrator to top up the wallet. - Alerting: Set up alerts for low balance thresholds to ensure timely recharging.
Security Advice
- Never Expose API Keys in Browser Code: Fikra API keys (e.g.,
fk_live_...) must be stored securely on the server side. Do not include them in client-side JavaScript, HTML, or any publicly accessible code. Exposing keys in browser code allows anyone to use your credits and access your data. - Use Environment Variables: Store API keys in environment variables (e.g.,
FIKRA_API_KEY) on your server to keep them secure. - Rotate Keys: If a key is compromised, rotate it immediately via the Fikra dashboard.
For the most current payment options and billing details, always refer to the Fikra dashboard or contact Fikra support directly.
James Miano
CTO & ML Engineer at Lacesse Ventures. James specializes in low-overhead LLM quantization processes, custom ternary weights architectures, and localized server optimization.
Stop paying for overpriced round-trip latency
Why route queries over Western servers when you can use low-overhead hardware located in Nairobi? Save 87% on your monthly inference spend. No minimum credit limits. M-Pesa ready.