Fikra API now has one clear product: an inference account an agent can open, fund, quote, use and audit. Humans use the same account with a normal OpenAI-compatible key.
What changed
- New accounts are prepaid. A new account gets $0.5 in credit and can top up from $1.0.
- Existing subscriptions are honored. They stay active and are managed from the dashboard. Public pricing does not sell a new subscription.
- Paystack checkout is unchanged. Card and mobile money continue to settle in KES. The dashboard shows the KES amount before payment.
- Limits are published once. 30 requests/minute and 300 requests/day unpaid; 3,000 requests/minute and 250k requests/day paid.
- Model IDs are disclosed. Fikra-prefixed IDs are stable aliases for third-party models. Each model page lists the upstream family and provider.
- Projection case studies and unverifiable testimonials were removed. The pages return 410.
- The trust page states the real posture. No self-serve SLA, no SOC 2 certification, no universal zero-retention claim.
What did not change
- The OpenAI-compatible API and existing model IDs.
- The Paystack checkout, webhook and existing subscription records.
- Existing balances and API keys.
- Prompts are not used for training.
Why
The previous site described several companies at once: a cheap DeepSeek reseller, an Africa-first gateway, an enterprise agent platform, and a model catalog. The claims contradicted each other and the code. The product that actually exists is smaller and more useful: an inference account with an agent payment and audit layer.
The agent surface is live today: agent-created accounts, scoped tokens, quote before spend, x402 USDC on Base, MCP and A2A. Streaming, budgets and receipts are the next surfaces and are not sold as live today.
If you are an existing customer
Nothing is required. Your key, balance and subscription continue to work. If you see a billing issue, reply to the email or contact [email protected].
If you are new
Read what Fikra API is, check the live prices, or start with the agent account.
This announcement is the canonical explanation of the change. The dated record is in the
changelog. The machine-readable version is
/changelog.json.