Purchasing Fikra API Credits: M-Pesa and Card Options
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 the public website states that M-Pesa and card payments are accepted.
Account and Top-Up Flow
- Access Dashboard: Log in to the Fikra dashboard to manage your account.
- Initiate Top-Up: Navigate to the billing or wallet section to purchase credits.
- Select Payment Method: Choose between M-Pesa or card payment via the Paystack integration.
- Confirm Transaction: Complete the payment process. Credits are added to your wallet upon successful transaction.
Monitoring Balance and Handling Errors
Developers should monitor their token-credit balance through the Fikra dashboard. If the balance is insufficient to process a request, the API may return an HTTP 402 (Payment Required) status code. Implement logic in your application to handle this response by prompting the user to top up their wallet or by gracefully degrading functionality.
Security Best Practices
- Environment Variables: Store your Fikra API key (
fk_live_...) in environment variables (e.g.,FIKRA_API_KEY) on your server. - No Client-Side Exposure: Never expose your API key in browser code, mobile apps, or any client-side environment. This prevents unauthorized access and potential abuse of your credits.
- Server-Side Proxies: If building a web application, route API requests through a secure backend server that holds the API key, rather than sending requests directly from the client.
Note on Payment Methods
While M-Pesa and card payments are publicly stated as accepted methods, specific details such as exact exchange rates, minimum deposit amounts, or regional availability should be confirmed directly with Fikra support or the dashboard billing interface before use.
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.