For evaluators

Don't take our word for it. Check it.

Five checks you can run from your own desk in about fifteen minutes, with no account and no call. Each one uses your own browser tools or a public record, and each one says what it does not prove.

1Your inputs stay on your machine

About 4 minutes. Needs a desktop browser with developer tools (Chrome, Edge or Firefox).
  1. Open the Patent Term and Maintenance-Fee Calculator.
  2. Press F12 to open developer tools and choose the Network tab.
  3. Run the calculator once with its preset inputs. This first run loads the tool's code, so you will see files arrive from gdbs.getvaultsync.com.
  4. Clear the network list (the circle-with-a-line icon), enter your own grant date, and run it again.
  5. Wait a few seconds, then look at what was sent. For a stronger test, set the Network tab's throttling menu to Offline, change the date again and run once more.
What you should see. One request, to /api/log/batch on gdbs.getvaultsync.com. Click it and open Payload: it records the tool's name, the word "run" and whether you used the preset or your own inputs. Your dates are not in it, and nothing goes to any other host. With the browser offline, the calculator still computes; only that usage event fails to send.
What this does not prove. It covers the calculation tools. Tools that search public sources (Federal Register, eCFR, court opinions) must send your search terms to fetch results, and the Gate client portal stores the documents you choose to share. The security page lists where each kind of data lives.

2Every answer traces to the rule it applied

About 4 minutes.
  1. On the same calculator, enter a utility patent's grant date: one of your own, or any issued patent.
  2. Read the three maintenance-fee dates in the result and the authority cited beside them.
  3. Open the cited statute, 35 U.S.C. 41(b), and the fee schedule at 37 CFR 1.20, and count the dates out by hand.
What you should see. Fees due at 3.5, 7.5 and 11.5 years from the grant date, each tied to the provision that sets it, so you are checking the reasoning rather than trusting an output.
What this does not prove. That every one of the tools is right. It shows the standard each one is built to: a result you can check against its source. These are calculators, not counsel.

3It tells you when a result can't be trusted

About 2 minutes.
  1. Open GeoNum Drift Under Cancellation and run it with its preset sweep.
  2. It computes (1 - cos x) / x² as x shrinks from 0.1 toward 0.00000001. The true limit is exactly 1/2, and the textbook way of computing it in ordinary floating point falls apart as x gets small.
  3. Watch the trust badge as the sweep moves toward small x.
What you should see. The computed value drifts away from 1/2, the tracked drift rises in step with the real error, and the badge drops to UNRELIABLE. A tool that only ever showed a green light would be telling you nothing.
What this does not prove. The trust verdict measures whether the arithmetic kept its precision. It does not judge whether the inputs or the method were the right ones for your question.

4Same input, same answer, on any machine

About 2 minutes, plus a colleague's computer.
  1. Paste any paragraph into the GTI Analyzer and note the score and the content hash it shows (a short fingerprint of the text).
  2. Have a colleague paste the same paragraph on a different computer and browser.
  3. Change one word and run it again.
What you should see. The same score and the same fingerprint on both machines, and a different fingerprint after the one-word edit. The calculator from check 1 behaves the same way: the same dates on any machine.
What this does not prove. The fingerprint catches edits; it is not a cryptographic signature and is not built to resist someone forging a match. The GTI score measures how a text is written, not whether it is true.

5VaultSync is a real, registered company

About 3 minutes. All public records, none of them ours.
  1. State registration. Search "VaultSync Solutions" in the Wyoming Secretary of State business search.
  2. Federal registration. Search "VaultSync Solutions" in the SAM.gov entity search for the active registration, UEI and CAGE code.
  3. Independent mention. The PenFed Foundation's press release names VaultSync in its Veteran Entrepreneur Accelerator, July 2026 cohort.
  4. A public build history. The open GDBS Free repository on GitHub shows the engine's public commit history since March 2026.
What this does not prove. VaultSync holds no SOC 2 or equivalent third-party attestation, and GDBS is not certified under HIPAA, ISO 27001, FedRAMP or CMMC. If your procurement needs one, the security page says so plainly and tells you who to write to.

These checks show how GDBS behaves. Whether it fits your team's work is a different question, and the answer is a pilot: thirty days, no cost and no card, with a written evaluation plan agreed up front and a one-page report at the end.

Request a team pilot Write to Joe Garrett, Founder and CEO

Evaluating the science engines? Each result on Validated results names the published reference it was checked against, so the same approach as check 2 applies.