Free halal stock screening API (Akinda free tier)

Most developer APIs that offer halal stock screening either require a contract or hide their free tier behind a sales process. Akinda is the exception — the Basic tier is free, self-serve, and lets a developer integrate halal compliance into a side project without any commercial commitment.

What's in the free tier

• 10 calls a day against the /compliance/<ticker> endpoint.
• 100 MB of data transfer per month.
• US ticker coverage — currently around 5,000 tickers in the catalogue.
• No credit card required — sign up with email or Google.
• Same methodology as paid tiers — the screen doesn't change based on what you pay for.

What it's good for

The free tier is targeted at developers who want to try the API before paying for it. 10 calls a day is enough to check a handful of tickers by hand, confirm the response shape, and wire the call into your code. It is not enough to keep anything running: the moment a watchlist, a bot or a dashboard refreshes on a schedule, you are on a paid plan.

When you outgrow it

• You need the financial ratios (debt, liquidity, non-compliant revenue) — those live on /basic-report and require the Personal Standard tier.
• You need the full AAOIFI screening grid + AI- extracted SEC dollar fields — that's on /full-report, Personal Ultimate or higher.
• You're hitting the rate limit — paid tiers move to a per-minute limit: 300 a minute on Personal Standard, 1,000 on Personal Ultimate, and more on the Business plans.

How to start

1. Create an account at /signup using email or Google.
2. Copy the auto-provisioned API key from /api-keys.
3. Fire your first request: GET https://b2b-api.akinda.io/api/v1/compliance/AAPL?apikey=<key>.

You'll get back a compact JSON verdict — here is the real response for AAPL:

{"company_name":"Apple Inc.","halal_status":"HALAL","ticker":"AAPL"}

The halal_status field comes back as HALAL, NOT HALAL or DOUBTFUL — plus an ERROR_DATA / INCOMPLETE_DATA state when a company's filings aren't available. Authenticate with the apikey query parameter or the X-API-Key header; there is no Authorization: Bearer flow. The verdict itself uses the same AAOIFI-based methodology on every tier — paid plans add the evidence behind it (the three ratios on /basic-report, the full screen on /full-report) and higher limits, not a different screen.