Direct answer
Teams in Morocco run WhatsApp support, email triage, coding second-eyes and back-office document summaries behind one Fikra key and one wallet. Every call debits predictably, every key can be capped, and /stats publishes platform telemetry you can sanity-check.
Live numbers as of 2026-11-14
These figures come from the public stats snapshot generated on 2026-11-14 from backend ledgers. They show volume and reliability only; they do not prove any single route wins your workload. Run your own 50 prompts before you move budget.
| Metric | Value | What it tells you |
|---|---|---|
| All-time requests | 126,617 | 109 days since launch |
| All-time tokens processed | 5,460,329,009 | 2,299,586,240 served from cache |
| Requests, last 30 days | 116,189 | 5,437,162,745 tokens across 82 active routes |
| Registered developers (all time) | 424 | Self-serve accounts, prepaid |
| Live model routes | 31 | Catalogue at /models; machine list at /v1/models |
| DeepSeek V4.1 Flash 1017, last 30 days | 63,202 | cache-hit rate 12.94% |
| DeepSeek V4.1 Flash Economy (free), last 30 days | 8,741 | cache-hit rate 97.36%; free window, not an SLA |
| 30-day uptime | 98.95% | 88,390 health checks; status currently reports attention, re-check /status before production |
What the routes cost right now
Prices are USD per 1M tokens, taken from the live registry snapshot dated 2026-11-14. The KES columns use the checkout rate of KES 133 = $1; your bank or card issuer may add its own conversion margin on top.
The catalogue is authoritative at /v1/models (the OpenAI-compatible listing) and at /models (the public card with context windows and rate limits). Check both before a production commitment; prices move with provider terms.
See the live list from your terminal: curl -s https://api.fikraapi.co.ke/v1/models -H "Authorization: Bearer YOUR_FIKRA_KEY"
| Model ID | Input / 1M | Cached input / 1M | Output / 1M | Input KES / 1M | Output KES / 1M |
|---|---|---|---|---|---|
| deepseek-v4.1-flash-1017 | $0.05 | $0.0075 | $0.15 | KES 6.65 | KES 19.95 |
| deepseek-v4.1-flash | $0.05 | $0.0075 | $0.15 | KES 6.65 | KES 19.95 |
| qwen3.8-27b | $0.045 | $0.045 | $0.35 | KES 5.98 | KES 46.55 |
| glm-5.3-flash | $0.1875 | $0.0375 | $0.625 | KES 24.94 | KES 83.12 |
| glm-5.3 | $1.225 | $0.225 | $3.85 | KES 162.93 | KES 512.05 |
| kimi-k3 | $2.4375 | $0.24375 | $12.1875 | KES 324.19 | KES 1,620.94 |
What production looks like in Morocco
A typical deployment in Morocco is small and concrete: one support queue, one budget cap and one route that survived a 50-prompt test. WhatsApp itself is not billed by Fikra; your WhatsApp integration passes the conversation text to the API, and Fikra bills the tokens.
The pattern that keeps side projects alive is boring: default route for routine work, escalation route for the hard 10%, wallet alerts before renewal day, and a rollback to the previous route ID pinned in /v1/models.
- Support agent: deepseek-v4.1-flash-1017 for routine replies; escalate billing disputes to a stronger route.
- Email triage: classify and draft with qwen3.8-27b at temperature 0 for deterministic labels.
- Coding assistant: glm-5.3-flash for completion-heavy work; qwen3.8-27b for structured refactors.
- Back-office: fikra-embed for retrieval, then one chat route for summaries; keep the corpus off shared free tiers.
Deployment sequence
- Install the OpenAI client; set base_url to https://api.fikraapi.co.ke/v1 and model to a live route from /v1/models.
- Set a conservative max_tokens and a per-request timeout before the first real user touches it.
- Cap the key in the dashboard; fund only what the pilot needs, from $5 upwards.
- Watch /stats and the dashboard for a week; expand budget only after cost per accepted task stabilises.
- Rotate keys per environment; use separate keys for staging and production, and revoke on offboarding.
Budget guardrails that fit a MAD team
Fund in dollars, plan in MAD. At the KES 133 = $1 checkout rate for Kenya, or your issuer's rate elsewhere, write the 30-day budget in local currency and convert it into a daily window. Lite allows $0.50 per day by default, Pro $1.50, Max $5.00; overages are not possible on a prepaid wallet because the balance is the hard cap.
How to start in Morocco in ten minutes
- Create the account at /account/signup and verify the email address.
- Copy the fk_live_ key from the dashboard and store it somewhere safe; it is shown once.
- Open /dashboard and pay by USD card. The minimum top-up is $5. Conversion from Moroccan dirham happens at your card issuer's rate and fees, not at a Fikra-set rate. Kenya also shows M-Pesa and Airtel Money; Morocco does not.
- Point your OpenAI client at https://api.fikraapi.co.ke/v1 and set the model to deepseek-v4.1-flash-1017.
- Run 50 prompts from your own workload, then open /stats and the dashboard to check token spend and cache hits before you scale.
- Cap the key with a budget in the dashboard, keep the route that wins your prompt set, and drop the rest.
curl https://api.fikraapi.co.ke/v1/chat/completions \
-H "Authorization: Bearer YOUR_FIKRA_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"deepseek-v4.1-flash-1017","messages":[{"role":"user","content":"Summarise this ticket in two lines."}]}'
Questions buyers ask
Can I pay from Morocco without a foreign credit card?
Not at this checkout. Morocco buyers pay by USD card; the Kenya checkout additionally shows M-Pesa and Airtel Money. Mobile money is not available outside Kenya on this checkout, so plan your funding path before onboarding a team.
How much do I need to start?
The minimum top-up is $5. Self-serve plans are prepaid per 30 days: Lite $10, Pro $25, Max $60. Every tier allows 3,000 requests per minute and 250,000 per day. There is no free production tier; free windows are trials.
Which model ID should I use first?
Use deepseek-v4.1-flash-1017 for text, code and summarisation at $0.05 input and $0.15 output per 1M tokens. Confirm it is listed at /v1/models before production, then compare against qwen3.8-27b and glm-5.3-flash on your own prompts.
Does Fikra sign an SLA?
No. Self-serve is prepaid and has no SLA. Platform 30-day uptime is published at /status (98.95% over 88,390 checks as of 2026-11-14, with status reported as attention). If you need a contractual commitment, contact support before you sign anything.
Where do I see my spend?
The dashboard shows balance and per-key usage; /stats publishes platform-wide telemetry from the same ledgers. Keep request IDs from production calls if you need to reconcile a charge.