Getting started
The order in which a new organization sets up Mandatary.ai, and where each thing is done. Every page also has its own 'How to use this page' panel at the top.
Checking what is already done…
Step by step
- Sign inThe first administrator opens the invitation link Mandatary.ai sent and creates a passkey. From then on, one button. Then add a second device (your phone) in "My account & devices", so that losing one does not lock you out.
Which buttons, in which order
- Click the blue button "Sign in with a passkey" and follow your device: fingerprint, face or PIN. There is nothing to type.
- First time? Open the invitation link your administrator sent you: it creates your passkey and signs you in.
- For a system, a trial account or the platform owner: click "Use an API key instead", paste the key and click "Sign in with the key".
- No data yet? On "Getting started", card "Demo data", click "Load demo data": a complete fictitious client (assets, principals, agents, mandates, a month of operations, alerts) appears in seconds.
- Members & rolesInvite each colleague by name and e-mail and give them a role: compliance officer, agent operator, auditor or administrator. The "i" next to "Role" says what each role can and cannot do.
Which buttons, in which order
- Tab "Members", card "Invite a member": write the "Full name" and the "Work e-mail", and choose the "Role". Point at the small "i" next to "Role" (or read the box below the list) to see what that role can and cannot do. For an auditor, set "Access expires on". Click "Create invitation link".
- Copy the link from the green box now ("Copy link"): it is shown only once. Send it to the person over a channel you trust. They open it, create their passkey and are in.
- Card "Members" (below): each person with role, status and devices. "Edit" changes name, e-mail or role (the new role applies at once). "Suspend" stops them immediately; "Reactivate" brings them back. "New link" is for somebody who lost every device. "Remove" erases their name, e-mail and devices and keeps their history. "Activity" shows what they changed.
- Tab "API keys": card "Create a key" issues a key for a system (or a read-only, scoped, expiring key for an auditor's tool); copy it from the green box, it is displayed only once. "Revoke" disables a key immediately.
- System API keyCreate the key your trading platform's backend uses to ask Mandatary.ai before each operation. Keys are for systems; people sign in with a passkey.
Which buttons, in which order
- Open "Members & API keys" and click the tab "API keys".
- Card "Create a key": in "Type" choose the role the system needs (Administrator for a backend that calls /verify and manages mandates; Auditor for a read-only tool, with scope and expiry). In "Who is it for" write the name of the system, never a personal name. Click "Create key".
- Copy the key from the green box now: it is displayed only once. Store it in your secrets manager and configure it in the SDK or in the "x-api-key" header.
- Card "Keys" (below): "Revoke" disables a key immediately; create a new one first if the system is in use.
- AssetsName the tokens your agents will trade (address → symbol and name).
Which buttons, in which order
- Card "Add an asset" (left): paste the token contract address in "Token address". The issuer publishes this address (for example Dinari or Ondo list their tokens per network).
- Click "Look up on-chain" (gray button under the field). The console reads what the contract calls itself and fills "Symbol" and "Name" if they are empty. A yellow box means what you typed does not match the contract: double-check the address with the issuer.
- Choose "Kind" (stock, bond, fund…), optionally "Issuer" and "Reference" (ISIN or CUSIP), then click the blue button "Save asset".
- Card "Catalog" (bottom): every saved asset. Click "Edit" on a row to change it; the address never changes.
- PrincipalsRegister who grants the mandates: company with LEI, or individual; record the identity verification.
Which buttons, in which order
- Card "Register a principal" (top left): paste the signing wallet in "Signing wallet". Wallets that already granted mandates but have no record appear as gray buttons under the field: click one to fill it.
- Choose "Type": Company or Individual. For an individual write only a label in "Label" (for example "Client 1042"); personal data stays in your KYC provider.
- For a company, type its LEI in "LEI (Legal Entity Identifier)" and click "Look up in GLEIF". A green box shows the official legal name and status; "Legal name" and "Jurisdiction" fill in. The LEI is saved only if GLEIF confirms it.
- Click the blue button "Save principal".
- Card "Registered principals" (bottom left): click a row. The card "Verification of …" appears on the right: choose "Result" and "Level" (Basic, Professional, Institutional), the provider and the case reference, then click "Record verification result". Professional and Institutional require a validated LEI for companies. A verification expires after twelve months.
- AgentsGive each agent an identity: operator, services, liveness, operator verification, credential, on-chain registration.
Which buttons, in which order
- Tab "Directory", card "Register an agent" (top left): paste the agent wallet in "Agent wallet address" (the same address that appears in its mandates), fill "Agent name", "Operator", "What it does" and, if the operator has one, "Operator LEI".
- Under "Services", type the endpoint the agent exposes (public https only) and click the blue button "Save agent". Its ERC-8004 registration file is published immediately at the address shown in the green box.
- Card "Registered agents" (bottom): click the agent name in blue to open its detail page. There you check its endpoints, record the operator verification, issue the credential and register it on-chain.
- Tab "Fleet": choose the operator and the window in the two selectors above the table. The four cards are the totals: agents (verified, alive), active mandates (on-chain, valid credentials), verifications in the window (denied, attestations consumed) and open alerts.
- In the fleet table, green badges are healthy. "Adherence" is the share of operations that stayed inside the mandate: green from 90 %, yellow from 70 %, red below. Column "Alerts": click "N open" to go to Alerts and acknowledge them.
- Grant a mandateThe principal signs a limited power for the agent (template, limits, jurisdiction, legal document). Before signing, try operations against it in the "Simulator": it tells which rule decides, without recording anything.
Which buttons, in which order
- Step "1. Who": click a template card (Basic, Professional, Institutional) to pre-fill sensible limits; choose the "Jurisdiction of the legal document"; enter the principal wallet, the agent wallet and the asset (pick it from "Pick a catalogued asset" if you registered it under Assets). "Use test values" fills a test agent and the demo token. Click "Continue" (bottom right).
- Step "2. What": tick the allowed actions (Buy, Sell, Transfer, Subscribe, Redeem). Click "Continue".
- Step "3. How much": per-operation cap, daily cap, total cap, optional human-approval threshold with its deadline, optional speed limit (operations per time window) and maximum risk score. Click "Continue".
- Step "4. When": validity in months and, optionally, the trading window (days and hours, UTC). Click "Continue".
- Step "5. Confirm": read the summary in plain words and the full "Legal document" below it. Then choose: "Sign with wallet and register on-chain" (MetaMask asks the principal for two signatures: the readable terms, then the technical message; no gas is charged to the principal); "Save as draft (sign later)" when the person preparing the mandate is not the one who signs it (it stays "Pending signature" and every operation is denied until the principal signs it from the mandate page); or "Register without signature" (active at once, no wallet, no chain; it cannot be signed later; for development).
- Connect your trading platformYour trading platform calls Mandatary.ai before each operation (SDK, with the system key from step 3) and receives signed events here. Optional: your own limits on top of every mandate, in "Platform rules".
Which buttons, in which order
- Card "Register a webhook" (left): paste your https URL in "URL", tick the events you want (none ticked = all), optionally a description, and click "Register webhook".
- Copy the secret shown in the green box now: it is displayed only once. Your server uses it to verify the header x-mandatary-signature (the SDK has parseWebhook for this).
- Card "Webhooks" (bottom): click "Send test" on a row to deliver a test event, "Deliveries" to see attempts, responses and retries (1 min, 5 min, 30 min, 2 h, 12 h), "Deactivate" to stop it.
- OperateFrom then on the console is a control room: operations waiting for a person in "Approval inbox", what the engine flagged in "Alerts", every decision with its evidence fingerprint in "Operation verifications", and for auditors and principals, "Evidence dossiers" and the "Principal report".
Which buttons, in which order
- Table (left): one row per verification with date, outcome, operation (action, asset, quantity, price) and reason. Click a row. Filters above the table: date range, outcome and agent.
- Card "Decision detail" (right): the rule that decided in plain words and in code, the operation, agent, platform, execution status reported by the platform, the evidence fingerprint and the on-chain anchor when the batch was published.
- Rows are created only by real agent operations: before an agent executes, the system that runs the operation (the trading platform, the token contract or the agent wallet) asks the engine through the API or SDK, and each question is one row. The simulator never creates rows.
Think of it as opening an account. First you decide who can enter and as what: each colleague gets their own access with a role (the compliance officer approves and revokes, the agent operator manages agents, an auditor only reads), and the system of your trading platform, the one that will ask Mandatary.ai before each operation, gets an API key. Then you describe what is traded (assets), who you are (principals) and who acts for you (agents). The principal signs the power (the mandate), you test it in the simulator, and your trading platform starts asking Mandatary.ai before every operation. From then on the console is a control room: approvals waiting, alerts, evidence for auditors and the statement each principal receives.
Why people come first. Everything a person changes is recorded under their own name, and whoever asks for an approval cannot be the one who grants it. That only works if each person has their own access from day one, instead of a key passed from hand to hand.
The tags at the top of this page turn green as your organization completes each stage; the blue one is what to do next. The panel "How to use this page" on every screen reopens if you click it after closing it.