Aller au contenu

Tools Reference

Ce contenu n’est pas encore disponible dans votre langue.

Thirty-one tools. Most take an action naming the operation, so one tool covers a whole area rather than a dozen near-identical entries. You do not call these yourself — the assistant does, from what you ask it in plain language. The list is here so you know what you have handed it.

Codes can be generated in English, German, Spanish, French, Italian or Dutch; every tool that produces or checks words takes a language parameter.

my_code — your own three words. Takes a Unix timestamp to compute the code for a moment other than now, which is how an assistant answers “what is my code for the two o’clock?”.

code_for — the current code for one connection, found by name. Partial names match.

all_codes — every connection with its current code.

verify — three words in, match or no match out, checked against your connections on this device. Because it only knows the connections whose secrets this device holds, it can honestly answer that it cannot tell.

rotation — when the codes change next.

status — signed-in state, sync state, how many connections are cached.

login — opens a browser. With action: "switch" it signs out first and lets you sign in as somebody else.

recover — sets up a new device from the three recovery words in the mobile app. Only called when login answers recovery_required.

stamp — puts your identity on a piece of text and returns a verification link. A file_path may be given: the file is hashed locally, never uploaded, and the hash is bound to the verification code, so a recipient can drop the file on the verification page and see that it matches. require_approval sends the request to your phone for biometric approval first. send_to_email mails the link to somebody. action: "export_proof" exports the proof document for a stamp you made earlier.

sync — pulls connection data from the server.

connect — joins somebody’s shared link, given its path.

mint_provider_stamp — for providers: mints a one-time, three-word verification code signed by this device’s key, to place inline in an invoice or a quote. The customer reads the words at the verify site and sees whether the document really came from you. Local only, and only after the device has been provisioned as a provider.

invitations — the default way to add people. send creates a connection and invites one address or many in a single step, with an optional description, tags, personal message, and a duration_hours after which the connection expires by itself. Also lists, approves, declines and withdraws.

connections — everything about connections that already exist: list with tags, rename, change the code language or code mode, add and remove members, avatars, favourites, transfer ownership, delete.

open_links — shareable links, for a website or an event, that let people connect without an individual invitation. Create, pause, resume, rename the slug, delete, and approve or decline the requests that arrive when the link is set to manual approval.

guest_codes — verification for people who do not have Trusted Codes. You create a code, they use it to confirm who you are. Create, list, search, revoke, send by email or SMS, and produce a QR code.

external_members — records a contact who is not on Trusted Codes, so you can keep and revoke the entry. It issues no code and no page. If somebody needs to verify you, this is the wrong tool; guest codes are the right one.

lookup_user — checks whether an email address belongs to a Trusted Codes user, so an assistant setting up a meeting knows who to invite and who needs a guest code.

tags — labels for connections. Create, rename, delete, assign, unassign.

presets — saved templates for connections: default name, description, language, code mode, auto-expiry, tags. Useful when the same kind of connection keeps recurring.

profile — read or update your display name and preferred language, and read your plan.

emails — the addresses on the account. One is primary, one is what connections see. Adding an address is two steps: send mails a code to it, verify confirms it. You have to read the code out of your inbox in between.

devices — what else is signed in as you: enrolled devices and open sessions, and the ability to remove either. Both are reversible; the person simply signs in again.

exports — the data export. Asynchronous: request returns an id, list says whether it is ready, download gives a signed link that expires.

notifications and preferences — the notifications themselves (list, mark read, delete) and the settings that decide which ones arrive by email, push or in-app.

api_tokens — user-scoped tokens for the Trusted Codes platform API, for a CI pipeline or an integration. These are not the local companion’s own tokens.

trust — the people you follow, your own trust score, the log of verifications, and verify_public, which asks the server rather than this device. verify and verify_public are different questions: this device knows only your connections, the server can answer for anybody, including beacons and provider stamps you have no connection to. Following somebody requires a ticket, and only verify_public issues one — so you cannot follow a person you have not just verified.

org — member management, groups and their entitlements, usage alerts, activity logs, dashboards and trends. Every action requires the admin or owner role; anybody else gets a permission error.

Two tools answer from server-held encrypted secrets rather than from this device, for when your own devices are offline and a connection has been opted in for it. Both are hidden unless the caller’s token carries the named scope for them.

verify_codeword_remote — returns one bit, match or no match, for a connection. It does not reveal the code. After fifty consecutive no-match results in twenty-four hours, remote verification switches itself off for that connection until you turn it back on by hand.

current_codeword_remote — returns the current code for a connection. Prefer the verify tool when you are checking words somebody has already given you.