Account
Dey check your sign-in status…
Sign in to manage identity verification, research access, organizations, billing and connection tokens here.
Google / GitHub na just to identify the account. To sign in, na passkey or wallet dem dey use — never password.
Approve a device
What does approving do?
Approving issues ONE personal API token to that device. Your passkey or wallet never travels to it. The code expires in ten minutes and can be exchanged once.
Deny anything you do not recognise. Check that the code on this screen is the same one the device is showing.
Account
Wetin be principal?
Principal na di stable identifier wey mithril.fund dey use know you. E no go change if you change passkey or wallet.
Linked accounts
Wetin be linked account?
If you link Google or GitHub account, "Continue with Google" go fit offer dis account passkey next time. Linked account na just name for the account; e no be way to sign in.
If you unlink am, e no go affect how you dey sign in wit passkey or wallet.
Notification channels
Wetin be notification channel?
Email address na only place wey notification go go, dem dey register am for dat reason. E no fit sign you in, e no fit take di place of passkey or wallet, e no fit reset password or recover account.
You confirm am by enter the code wey the mail carry into dis signed-in page. The code no be link, e go expire after 15 minutes.
Notification wey dem dey send to dis address today: notice when connection token don issue.
Identity verification
How verification dey work
Card verification: register credit or debit card make e complete (checkout.stripe.com). Prepaid and virtual card no dey accepted.
You fit add document verification (Stripe Identity, verify.stripe.com). Card details and documents dey go to Stripe only; mithril.fund dey keep the status, the expiry date, and one evidence reference. Verification go expire after 365 days.
Research access
Scopes wey dem approve
Wetin be scope?
Every scope get im own approval basis for research. Scope wey don expire or dem suspend no fit run inference.
Organization
Organizations and teams
Dem dey issue organization as did:webvh DID; membership dey manage with verifiable credentials (VC). Di person wey create am go get owner role.
Members wey dem invite go share API tokens, scopes and billing. Roles na owner / admin / member / billing.
Organization SSO (Team / Enterprise)
Wetin be organization SSO?
Na organization identity provider (OpenID Connect: Google Workspace, Microsoft Entra ID, Okta and others) dey manage members. If dem remove member from IdP, e go lose organization access for the next re-authentication interval.
IdP no be way to sign in. Members go first sign in with passkey or wallet, den authenticate with di organization IdP to get membership. Roles na admin / member / billing; IdP no fit ever grant owner role.
Na for organizations wey dey on Team / Enterprise plan dis dey available. SAML no dey supported yet.
Team
Member invitation go open once organization dey exist.
Security controls
Guardrail, firewall and compliance rules plus their versions dey show under Security controls.
Billing and credits
About charges
Dem no dey charge di free research plan wey you don verify. Paid capacity, dem go buy am without automatic top-up.
Use from CLI / IDE
Issue connection token for local CLI / IDE agent. E go show one time only.
For OpenAI-compatible clients: KOTOBA_API_BASE=https://api.mithril.fund/v1 and KOTOBA_API_TOKEN=kc_pat_… (dem go show the token one time after dem issue am).