aicertificates.study

Last change

None yetUnchanged since first read.

Declared read-only

4 of 5

llms.txt

Present

1. check_answerCan change things

   Grades the user's choice and returns an explanation for EVERY option, including the ones they did not pick. On this exam two options are frequently defensible and only one is credited, so the reasons the wrong options lose are the part worth teaching.

   First seen 11 Oct 2026. Unchanged since.

2. get_practice_questionReads only

   Returns one original practice question with its options and no answer key. Present it to the user and let them choose before calling check_answer. Pass every id already served in exclude_ids — this server is stateless and remembers nothing.

   First seen 11 Oct 2026. Unchanged since.

3. list_examsReads only

   The Claude certifications covered here, with exam codes, item counts, fees and the full domain list with published weights. Call this first to get valid exam slugs.

   First seen 11 Oct 2026. Unchanged since.

4. my_progressReads only

   Their recorded history for one exam, broken down by blueprint domain with the weakest first, plus how their misses compare with everyone else's on the same free-form questions. Call this at the start of a study session to decide what to drill, and after a run of questions to show what moved. It names the domain to pass to get_practice_question, and when their misses follow the crowd's favorite wro

   First seen 11 Oct 2026. Unchanged since.

5. open_studyReads only

   Open or resume the study page for an exam, optionally focused on a domain or a sub-objective. Use this when someone asks to study rather than to be quizzed in chat: the page gives them a visible question they answer themselves, and once it is open a richer set of tools appears for reading and steering that screen. Returns the URL; a browser agent should navigate there.

   First seen 11 Oct 2026. Unchanged since.

Run this site? This page shows what your site told our crawler, ToolChronicleBot. To be left out, disallow it in robots.txt or write to hello@toolchronicle.com.