Questions, answered.

A way to check claims from your own tools. You send text; it finds the claims, searches trusted sources, weighs the evidence, and returns a verdict with sources and a write-up. It is built by PIJAlance Magazine.

Newsrooms first, and any organisation that needs to check what it publishes or shares: NGOs, election monitors, universities, communications teams, platforms.

Sign in with your work email (we send a 6-digit code), open API keys in the dashboard, and click Create key. It is shown once, so copy it straight away.

A workspace belongs to an organisation, not to a personal inbox. It keeps your team's checks, style and review queue in one accountable place.

To call the API directly, yes. Without code you can use Google Sheets, a phone shortcut, or Zapier, Make or n8n. The docs show each, with pictures.

The first 100 checks every calendar month are free for the whole workspace. No card is needed.

While billing is off, requests return 402 until the next month. When pay as you go opens, you add a payment method and checks continue. The response tells you when you are past the free allowance.

A request that returns 200 or 202. Errors are not counted.

8,000 characters per request. Split longer articles by section.

Five active keys and fifty people per workspace.

A few seconds for a short sentence and up to a few minutes for long text, because it reads real sources. Always send async: true and collect the result later.

English, Hausa, Igbo, Yoruba and Nigerian Pidgin for answers. Evidence is searched in English.

Nine: verified true, mostly true, unverifiable, misleading, false, false context, speculative, AI generated, satire or parody.

One the system cannot settle with enough confidence. It has no verdict and goes to your own review queue. Never show it to readers as a finding.

Your text contained more than one claim. Each is checked separately.

We looked for evidence and found none that could confirm or refute it. That is a finding. Adding who, where and when to the claim often helps.

Your own editors, in your own queue in the dashboard. If you want PIJAlance editors to do it, that is a separate subscription.

Yes. Paste your style guide under House style. Answers for your workspace come back in that style. It never changes a verdict or a source, and it does not affect anyone else.

No. Facts always win over style.

Owners do everything and can hand over ownership. Admins manage people, keys and style. Editors review claims. Members run checks.

Owners and admins have an Activity tab with each person's last use and checks in the last 30 days, plus a log of changes.

Remove them on the Team tab and revoke any key they knew.

No. Anyone could read your key in the page code. Call it from your server.

Revoke it in the dashboard at once, then create a new one.

No. Read the sources, especially when confidence is medium or low. Always publish the AI disclosure with the write-up.

Checks are recorded so you can trace a published verdict. Do not send passwords, ID numbers or confidential source details.

Not through the API yet. Text only.

The key is wrong, has a space, is missing the word Bearer, or was revoked.

You have used the free checks this month.

Use async: true and poll the job.

The write-up step did not run. Send the check again, and never publish without the disclosure.

Check your spam folder, request a fresh code, and use your organisation email.

The troubleshooting page, then the community.