Fidera documentation
Create an account
Sign up, verify your identity, and get a tenant API key — without talking to anyone.
Everything in these docs needs a tenant secret key. Here is how to get one.
1. Sign up
Go to fideralabs.com/signup with a company name, your name, a work email, and a password of at least 12 characters. We email you a confirmation link; it works once and expires in 24 hours.
Clicking it signs you into the operator console.
2. Verify your identity
Your account starts in pending_verification. In that state you can browse
the whole console, but your API keys are inert — every request with one
returns 403.
To activate, complete a single identity check: a government ID and a short face check, on your phone, taking about two minutes. Start it from Settings → Verify your identity, which gives you a link to open on a mobile device.
It is the same hosted journey your own applicants will complete. That is deliberate — it is worth seeing the thing you are about to integrate from the other side.
We do this for one practical reason as well: checks call live providers and cost real money, so verifying that each account belongs to a distinct person is what keeps a free allowance affordable. One person, one account. If you genuinely need a second — an agency, a separate legal entity — email sales@fideralabs.com.
3. Take your key
Once the check passes, your account activates within a few seconds and the
console swaps the verification card for Settings → API key. Press
Rotate API key to mint your first tnk_ key.
It is shown exactly once. We store only an HMAC fingerprint, so a lost key cannot be recovered — only replaced.
export FIDERA_API_KEY="tnk_..."Keep it on a server. It carries full access to your tenant. If you need a credential for browser or mobile code, use the publishable key instead — see Authentication.
What's included
A new account comes with 250 checks. They run against the same providers production uses — real sanctions data, real document extraction — because a sandbox that returns fixtures cannot tell you whether the thing works.
When the allowance runs out, requests return 402 with
code: "allowance_exhausted". Nothing is throttled or degraded before that
point, and no check is ever partially graded to save budget. To raise the
limit, email sales@fideralabs.com.
Current usage is on Settings → Included checks, broken down by check type so you can see where the allowance went.
Next
Quickstart — your first Check, in about five minutes.