Trooth

Runs the whole guide, proving the domain, reading the site, reviewing and signing the facts, putting the signed copy on the site and checking it, and answers the one next call to make: next_action names the tool and its arguments. Each answer reflects the steps already done. A step only a person may take answers its trooth.co page.

For one hub (business_profile or merchant_center): previews what the signed facts change there, then, with approve true, sends those items, then checks the hub against the signed copy. Each call does the next of preview, send and check and answers next_action. Sending waits for a person's approval where the key needs one.

Adds one toolset to what tools/list shows for this sign-in or key: developer (Developer), team (Team and governance), commerce (Commerce), reports (Reports), evidence (Evidence and monitoring), semanto_more (Semanto, every tool). Answers the group's tools. Every tool already answers by name; this only changes the list.

Searches every tool on this server, shown or not, by name, title and description, and answers the best matches with their toolset and input schema. Each match answers by name.

Runs one tool by its name with its arguments, exactly as calling it directly does: the same sign-in, scopes and approvals. Use it for a tool search_tools or enable_toolset named that your client does not list.

Read what one company on the Trooth Network has declared about AI and customer data (whether it trains models on customer data, whether AI is in the product, which approaches), named by its domain or its Trooth slug, matched exactly. Each row is the company's own declaration and is labeled so, with whether Trooth observed a supporting policy clause: not observed means Trooth has not read one, never that the company does not train on customer data. Read only.

Answer a question about Trooth itself (what the Trooth Network is, what one company record carries, pricing, how witnessing works) from Trooth's fixed, curated knowledge base; takes one question of at most 500 characters. Makes no outside request. A question the knowledge base does not cover returns out_of_scope; for a company's record use trooth_public_trust_profile.

List how one company's published record changed: give its domain or slug and, optionally, since (an ISO 8601 date or time). Returns record versions oldest first, each with the fact keys changed, added or removed, per-fact edits (old value, new value, time, role) when the record carries them, with next_cursor for more, and the recalls the company stored or changed in Semanto, oldest first, with recall_cursor to poll for newer ones. Read only.

Read one answer from one company's published record: give the company's domain or slug and a buyer question ID (q_ai_training and eleven more, in trooth://buyer-questions) or a fact ID such as security.mfa_methods. Returns the sentence, value, provenance word, date, freshness window and anchor address, or the negative that applies: no, not_published or not_read. A fact ID the record does not hold answers unknown_fact_id with the IDs it holds. Read only.

List the companies published on the Trooth Network by what they published: industry, data region, witnessed or not, and claimed (the company published its own profile) or unclaimed. Returns 20 entries per page in alphabetical order of record identifier with next_cursor (limit takes 1 to 200), from the first 100 matches the directory returns, so at most 100 come back; nothing is weighed or put in an order of merit. Read only.

Needs an OAuth access token for this server, for a person who has signed in to trooth.co (no scope is required; the public tools here need no token, and an agent key is not accepted), and takes no arguments: the workspace comes from the token's subject and never from an argument. Reads the company record of the Trooth workspace the signed-in person belongs to and returns its name, its slug and the address of its public page. Read only.

Takes no parameters.

Fetch https://<domain>/ and /.well-known/security.txt once, when called, from Trooth's server and report whether HTTPS answered, which of five response headers (HSTS, CSP, nosniff, frame protection, referrer policy) are present, and whether security.txt is published, absent or unread. IP literals and names resolving to private, loopback or link-local addresses are refused; redirects are reported, not followed; each request stops after 4 seconds. Observations, not witnessed evidence, not a grade.

Uses your trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when you belong to several. Lists the steps left before the workspace's Trust Profile can be published, each with state done, todo or unknown and how to do it. A step that is the owner's own choice carries action_url, the trooth.co page where the owner takes it. Read only.

Uses your trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when you belong to several. Lists, field by field, where the saved Trust Profile draft and what the public page says now differ: each such field, by JSON Pointer, with change added, removed or changed and both values. A profile never published shows every field as added. Read only.

Checks DNS now for the TXT record trooth_profile_domain_start gave. Uses your sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when you belong to several. Returns confirmed true, or confirmed false with found (the TXT values at the record's name), expected (the value it must carry), host and dns_host (where the domain's DNS is managed), and the fix; DNS can take minutes, so check again. Once confirmed, trooth_profile_publish can put the page live.

Starts the proof that the workspace controls its company's domain. Uses your sign-in as owner or admin (or an agent key with profile:publish). Takes domain, and workspace when you belong to several; it states you act for someone authorized to represent the company. Returns the DNS TXT record (host, value) to add with the DNS host's own API. trooth_profile_domain_check confirms it. Refusals carry code and fix.

Uses your trooth.co sign-in (or, for an agent that runs on its own, the workspace's agent key with profile:read). Takes fields, and workspace when you belong to several. Returns the workspace's own Trust Profile DRAFT as saved now, its revision (send it as if_match to trooth_profile_update), whether it is published, and its public address. fields narrows the draft to the keys or JSON Pointers asked for. With no sign-in: status unauthenticated and the fix. Read only.

Uses your trooth.co sign-in (or an agent key with profile:write). Reads one https page of the company's own website (robots.txt first) and returns the candidates, saving nothing; accept all or candidate ids saves them to the DRAFT with the page named. pages (up to ten of one site) reads each in turn and fills blank draft fields only, the website from the home page, each value with its page. Nothing is published. It states you may draft from those pages.

Puts the workspace's saved Trust Profile draft on its public page, which anyone can read. Uses your trooth.co sign-in if your role may publish the page (or an agent key with profile:publish). Takes only workspace, when you belong to several. Success: status published with public_url. A first publish needs the domain proved: code domain_proof_required until trooth_profile_domain_start and trooth_profile_domain_check are done. Other refusals carry their code and fix.

Uses your trooth.co sign-in (or an agent key with profile:read). Takes only workspace, when you belong to several. Turns each open checklist item into a step: the problem, the fix, the change or call that closes it, and the source its value needs. It proposes and never applies: every proposed value is null until you read it from that source and send it with trooth_profile_update. Read only.

Changes fields of the workspace's own Trust Profile DRAFT; the public page changes only on trooth_profile_publish. Uses your trooth.co sign-in if your role may edit the page (or an agent key with profile:write). Each change names one field by JSON Pointer (/tagline, /founders/-) with a value and its source { url, quote } from the company's own page, or state not_published with a reason. Returns each change as applied or rejected (with code and fix) and the new revision.

Uses your trooth.co sign-in (or an agent key with profile:read). Takes changes (optional, as trooth_profile_update takes them), expected_revision and workspace. Runs the checks of trooth_profile_update with dry_run and of a publish (name, domain proof, transcripts, agent publishing permission, instructions to a model) and saves nothing. Returns each check with its code and fix, and would_publish. Read only.

Read one company's published record on the Trooth Network, given its domain or Trooth slug, matched exactly, never by a similar name; a name several companies share returns their candidates, not a pick. Returns a status and a provenance label with the complete Trust Profile (detail full, the default) or a short answer (detail summary, the better first call). A record is keyed by its domain and does not by itself say which legal entity, subsidiary or product the domain belongs to. Read only.

Find the published Trooth Network record for a company given a domain, web address, Trooth slug or name; a company-register identifier, Crunchbase address or Wikidata ID is accepted and answered not_found, because Trooth keeps no lookup by them. Returns the record ID, its canonical https address and why it matched, or every candidate with why each matched (status ambiguous, none chosen), or not_found. Read only.

Search the companies published on the Trooth Network by name, domain, tagline or category, optionally within one industry. Returns up to 10 entries per page (limit takes 1 to 200) in slug order with next_cursor; only the first 100 matches are read, so at most 100 come back, each with its name and tagline in the company's own words, whether Trooth witnessed it, and the identifier that reads its record with trooth_public_trust_profile. Read only.

Check the two signatures on a Trust Ledger Token (tlt2. or tlt. form, or its JTI) against Trooth's own token ledger. A Trust Ledger Token is a signed token a company issues through Trooth about its own declared claims: the company signs the claims and Trooth signs the event of issuing it. Returns valid, invalid (a signature does not check out), expired or revoked, or unclaimed when no token matches; Trooth's signature covers the signing event, not the claim bytes and not the truth of the claims.

Setup status and next step. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

What Semanto is and the order an agent runs it in, with which steps need the person. Read it once before running setup for someone. No key needed.

Takes no parameters.

Read the website again. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

Choose Basic or the full signed copy. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

The facts to review. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

Confirm the reviewed version. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

Sign and publish. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

Pages changed since the read. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

How to put it on the site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

Check my site. Sign in to Trooth, or send an agent key, to see what it takes and to use it.

Takes no parameters.

One page of a company's signed copy as markdown, by its path on the company's site. No key needed.

The company's signed facts as JSON-LD. No key needed.

Checks a page against the current signed version. With no hash, Trooth fetches the page as an agent does (Accept: text/markdown) and hashes what it is served, which is what semanto_install_check checks too; compared says which. When the live HTML changed after the last signature, the site serves the last signed bytes under a behind notice; the notice is stripped before hashing and served_state says behind. status: matches, differs (hash is what was found, signed_hash what was signed), not_served (the page did not answer with markdown), unknown_url or not_signed. No key needed.