Tools
Exactly what the server advertised in the scan completed . Effects and capabilities are classified by Squatch from each tool's metadata. Squatch never runs tools. Compared with the previous scan: 4 new, 2 changed.
- Effect: Read 12
- Effect: Write 4
- Effect: Execute 3
- Effect: Unknown effect 1
Showing 20 of 20 tools
| Details | ||
|---|---|---|
| benchmarks Benchmarks as sets of statements, with how many members already carry public AI work: a contamination figure rather than a study. | Effect: Execute | |
| search_statements Search the register of mathematical statements. Returns summaries with formal status, prizes, and how much AI work is recorded against each. | Effect: Execute | |
| search_targets Search the targets: quantities with a direction and a record history, where AI work moved a bound or produced a better object rather than s… | Effect: Execute | |
| flag_recordNew Ask for a correction to a record: say what is wrong, with sources. Sent as a correction. Needs an API key, free from https://qed.bot/check … | Effect: Write | |
| list_systems Track record per AI system, computed from recorded claims. Not a benchmark: which statements attract attention has little to do with how ha… | Effect: Write | |
| submit_claimNew Add a claim of AI work to a record the register holds, with the systems and people behind it, when it was done, what it achieved and its so… | Effect: Write | |
| submit_leadNew Send qed.bot a link it should look at: a paper, a repository, a post or an announcement of AI work in mathematics, with an optional note, a… | Effect: Write | |
| check_proofChanged Have qed.bot rebuild a Lean file at its commit and read what every theorem in it depends on, under the admission rules every stranger's fil… | Effect: Read | |
| compare_registries Results recorded by more than one registry, and how the positions differ. A disagreement is a difference of judgement about who did the mat… | Effect: Read | |
| disclosure Announcements of results, graded for how much of what they claim can be inspected: whether each result is named, written up, and published … | Effect: Read | |
| get_checkChanged A paid check's status and verdict, by the id check_proof returned. Needs the same API key for a private check, or, for one paid over x402, … | Effect: Read | |
| get_formalisation One declaration in full: its sources, related formalisations, main results, the results held here it joins and on what key, Palomar's regis… | Effect: Read | |
| get_statement Everything the register holds about one statement: formalisations, cited proofs, recompilation results, graded claims, relations and aliase… | Effect: Read | |
| get_submissionNew Where a submission stands, by its id: stage received, in_review, accepted or declined, the review's note (the reason for a decline), whethe… | Effect: Read | |
| get_target Everything the register holds about one target: the record history with who held each value and when, the graded claims, and any check run … | Effect: Read | |
| list_collections The collections held, with counts of statements, formalisations and AI activity. | Effect: Read | |
| list_evaluators The object checkers available, what each establishes, what an artifact must look like, and which targets have been checked with it. Read th… | Effect: Read | |
| open_problems Statements not recorded as solved, most valuable prize first. Use formalised_only to restrict to those a prover could attempt directly. | Effect: Read | |
| search_formalisations Every formalization.yaml the register has read, with what each declares about its own axioms, unproved goals, assumed literature, automatio… | Effect: Read | |
| registry_positions Every registry's position on one result, this register included, with each one's own label preserved beside the bucket it was placed in. | Effect: Unknown effect |