Identity and business verification (KYC/KYB)

Both Thinker models unlock through KYC and an Enterprise contract.

Updated 2026-10-27 · MainAI Compute docs

KYC confirms the person; KYB confirms that the organization is a real legal entity and that the submitter can act for it. Both are reviewed as one identity case. Approval starts contract review; the recorded contract unlocks both the portal and inference.

What access needsLink to this section

Stage	Check	Unlocks
Public marketing	None	Catalogue, model pages, pricing and docs.
Portal shell	Verified email	Onboarding, KYC case submission and status.
Portal and inference	Approved KYC + active Enterprise contract	Dashboard, keys, wallet, ledger and both models.

Public marketing

Check: None
Unlocks: Catalogue, model pages, pricing and docs.

Portal shell

Check: Verified email
Unlocks: Onboarding, KYC case submission and status.

Portal and inference

Check: Approved KYC + active Enterprise contract
Unlocks: Dashboard, keys, wallet, ledger and both models.

There is no trial, free model or preview bypass. New organizations start on free; staff approve KYC and then record an Enterprise contract reference. The plan only changes through the staff commercial panel.

Collect before you startLink to this section

Field	Notes
`legalName`	Exactly as registered, including suffix.
`registrationNo`	National company number. Include the country prefix if that is the local format.
`country`	Two-letter ISO code of incorporation.
`documents`	Evidence references: registration extract, beneficial-owner summary or authorization letter.

legalName

Notes: Exactly as registered, including suffix.

registrationNo

Notes: National company number. Include the country prefix if that is the local format.

country

Notes: Two-letter ISO code of incorporation.

documents

Notes: Evidence references: registration extract, beneficial-owner summary or authorization letter.

The submitting user must hold owner, admin or billing. The endpoint is session-authenticated:

POST /api/portal/verify

bash

curl -s https://cloud.mainai.dk/api/portal/verify \
  -H "Content-Type: application/json" \
  -H "Origin: https://cloud.mainai.dk" \
  -H "Cookie: $PORTAL_COOKIE" \
  -d '{
    "legalName": "Northwind Systems ApS",
    "registrationNo": "DK-41827391",
    "country": "DK"
  }'

A successful submission moves the organization to pending. It does not change the plan. The page at /kyc remains the only accessible authenticated screen until approval and contract.

StatesLink to this section

State	Meaning	What to do
`unverified`	No case submitted.	Submit the legal identity.
`pending`	Queued for staff review.	Wait; answer any request for more information.
`approved`, no contract	Identity confirmed.	Staff record the Enterprise contract next.
`rejected`	Evidence insufficient or mismatched.	Read the reason, fix it, resubmit.

unverified

Meaning: No case submitted.
What to do: Submit the legal identity.

pending

Meaning: Queued for staff review.
What to do: Wait; answer any request for more information.

approved, no contract

Meaning: Identity confirmed.
What to do: Staff record the Enterprise contract next.

rejected

Meaning: Evidence insufficient or mismatched.
What to do: Read the reason, fix it, resubmit.

Review and contract orderLink to this section

01Staff open the case in Verifications and inspect the legal fields and evidence.
02Approval sets verification to approved and activates the organization, but leaves the plan uncontracted.
03Staff open the customer commercial panel and enter a signed contract reference.
04The plan becomes enterprise, a start date is stamped and the contract mail is queued.
05The dashboard, wallet, keys and inference become available.

Review criteriaLink to this section

Legal name matches the registry extract.
Registration number resolves in the stated country.
The submitter is authorized by the organization.
Billing email uses a domain consistent with the entity, or the difference is explained.
Beneficial ownership is clear enough for the agreed credit limit.