Your Trooth account and your company's workspace are now kept apart, as GitHub keeps a personal account apart from an organization: a workspace can have more than one owner, members can leave it, and an owner can reinstate a former member within three months. Every page also downloads less before it draws.
Every published company record now answers twelve buyer questions from its own fields and gives each fact an ID and a sentence that stands on its own. Trooth's Model Context Protocol (MCP) server, version 1.8.0, adds four read-only tools, two prompts and three resources, and records can now be asked about at /ask, downloaded in bulk and followed in feeds.
A person in a workspace can now give an artificial intelligence agent a bounded authority to pay or share data with one company, approve what it asks for above those limits, and revoke it. Trooth signs a receipt for each delegation and a ten-minute evidence reference for each authorized action.
A Trust Center document now carries a SHA-256, computed from the uploaded file or stated by the company; a certification can carry the digest of a private report and a link to the auditor's signed statement; a company can name the version of its record in its domain-signed declaration; each state registry entry in the public record names when it was read and the digest of the file or answer it came from.
The compare pages on trooth.co, the compare endpoint of the public application programming interface (API) and the Model Context Protocol (MCP) tool trooth_compare_companies are withdrawn. Each company's Trust Profile, the search, the shortlist and the public record are unchanged.
GET https://api.trooth.co/public/trust/{slug} is deprecated in favor of the canonical read, and the body-only webhook signature is legacy. Both stay in service until April 30, 2027.
A company can now sign and publish its own declaration at /.well-known/trooth.json on its domain, naming its keys, products, application programming interfaces (APIs) and code repositories, and trooth declare makes, signs and checks it. Each public record reading now names the proof behind each tie between a domain and a company, a key, a product or a repository.
The Trooth guard runs inside your agent and, before a consequential action, checks the counterparty's signed Trooth records and applies your written policy, answering allow, hold for a person, or deny. Each public record reading now names how each binding is proven, how fresh each class of evidence is, and what changed since the previous reading.
Trooth now fingerprints the tools Model Context Protocol (MCP) servers list and enters every change in its log, the public record adds federal contracting, patents, state registers, merger review and the domain's registration, and every checkpoint of the log is also signed by a key held in hardware.
Trooth's log now asks independent witnesses to cosign each checkpoint, every entry has a receipt in the COSE format, and each public record reading is signed and entered in the log. The public record is shown on Trust Profiles.
trooth public-record shows what a company filed with the US Securities and Exchange Commission (SEC) and what the Legal Entity Identifier (LEI) register holds about it, each fact with its source, and ties the company to a domain only where the evidence does.
Every witness statement Trooth publishes, and every correction it issues, now goes into one public log that can only grow. trooth verify checks each statement's place in it, and anyone can check that the log was never rewritten.
trooth verify can keep everything it checked in one file and check that file later with no network. It also checks statement v3, and the same checks now run as a library in JavaScript, Python and Go.
trooth verify checks a record's signed witness statement on your own machine: the signature, the key's status, the domain it was signed for, the counts, and the check mapping and evidence manifest digests.
The signed-in part of the public Model Context Protocol (MCP) server and the A2A agent is live: an agent with an OAuth access token from Trooth's sign-in provider can read your own workspace's company record and keep A2A tasks for 24 hours. No scope is required.
A company's own AI agent, working in an owner's or admin's browser, can now publish the company's declared fields without a person approving each change. It is on by default and can be turned off in Settings, Workspace.
The limit on free readings now matches what it promises, the public Model Context Protocol (MCP) endpoint and a new agent-to-agent (A2A) endpoint publish how to get an access token, traces connect the browser, the website and the application programming interface (API), and the signed-in workspace is fully in the message catalog.
Directory search now matches product names and domains on the live page, errors can be read as standard problem details, every response carries a request id, sign-in uses PKCE where the provider supports it, webhooks carry Standard Webhooks headers, and seven keyboard and focus defects are fixed.
Profiles say Not supplied and Temporarily unavailable in plain words, comparisons can show a stale, disputed or unreadable answer, a published product video needs a transcript, the public record read can be paged by section, and a status-page webhook proves it is yours before it is subscribed.
Accounts with two-factor authentication can make single-use recovery codes, profile alerts start only after the address confirms, the shared webhook key signs nothing from September 29, and a compromised signing key is treated as compromised whatever time a receipt carries.
Trooth now relies on the Article 27(2)(a) exemption instead of appointing an EU representative, with the events that would change that written down, and the Cloudflare connector names the two read permissions it needs.
The records Trooth kept indefinitely now have an end, the continuity document says what the Continuity Contact may do in the first hours of an incident, every control not yet in place carries a date, and a production deploy made outside the deploy workflow is now detected within the hour.
Corrections from an outside audit of the product, its public documents and its interfaces. A request for contract 1 now gets contract 1, the public interfaces have one catalog, the software bill of materials lists every package the website installs, the command line reads infrastructure files more exactly, and the published documents that had drifted from the service were brought back into line.
A sweep of the public site's 95 pages at thirteen screen widths, from a 320-pixel phone to a 3840-pixel monitor, in both themes. Links in legal documents are underlined again, code samples and wide tables can be reached from the keyboard, small text was raised to a readable size, and signed-out visits no longer log an error.
The continuity document now covers operator continuity, with a designated Continuity Contact, and sets out what Trooth commits to if the service is ever transferred or discontinued, including at least 90 days' notice.
The Trooth Standard and the Buyer Review Standard are rebuilt as references: each shows its version, who maintains it and its revision history, and every requirement or item says what it asks and what it does not establish. Requirement 08 is retitled to say what its checks cover. The About page pairs each commitment with its evidence.
Feedback is now a public board: search what others asked, vote, comment, and follow each request to the change that shipped it. Any two companies can be compared, up to four, on their published records.
The developer reference is rebuilt as a two-column reference with a quickstart, limits stated as numbers, and one entry per endpoint. The changelog can be searched, filtered, linked to and followed by feed.
The methodology page now carries a version, an effective date and a change log, defines all ten evidence labels, and has an invented example profile you can inspect without an account.
Every Cloudflare Worker behind api.trooth.co now has a public software bill of materials, and two claims on Trooth's own Trust Profile were corrected to match its policies.
Check counts on a Trust Profile, in the profile API and from the MCP server now come from the signed witness statement. Profile contract 1 is withdrawn on 2027-03-01.
Version 0.5.0 of the trooth command-line tool parses the files it lints, reports what it could not read, and exits with code 4 when a file cannot be parsed.
Disputes are visible only to the company concerned and to Trooth. Framework rollups are retired from the public mesh and comparisons, and badge 1.0.0 can be pinned.
Webhooks are signed per endpoint with a version 2 signature. The shared signing key was retired on 2026-09-28, and from 2026-09-29 endpoints that have not proven ownership receive nothing and no delivery carries the shared-key signature.
The Acceptable Use Policy, the API terms and the connector, privacy, retention, corrections and versioning documents were revised to match what the product does.
Personnel lifecycle, access review campaigns, typed-name policy acceptance, read-only auditor portals, and each vendor's live witnessed record in the vendor register.
Occasional notes when something on this page changes. You get one confirmation email when you subscribe, every email carries an unsubscribe link, and the address is never sold or shared.
Help decide what ships next.Requests are read by a person, and votes inform priorities.