Check and normalize a TeX formula in Wikimedia
A documented Wikimedia operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Check and normalize a TeX formula.
- POSTChanges data · Math
wikimedia.org/media/math/check/{type}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Wikimedia operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Wikimedia operations
- Machine-translate contentPOST · changes data
- Machine-translate contentPOST · changes data
- Lists the language pairs supported by the back-endGET · reads data
- Gets availability of featured feed contentGET · reads data
- Lists the tools and language pairs availableGET · reads data
- Lists the tools available for a language pairGET · reads data
- Lists the tools and language pairs availableGET · reads data
- Get a previously-stored formulaGET · reads data
Questions
- Can HumDay check and normalize a tex formula in Wikimedia?
- Yes. This operation is published in Wikimedia's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Wikimedia data?
- Yes — this is a POST operation, so it changes something in Wikimedia. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Wikimedia account.
Where this came from
Read from a published API description for Wikimedia at wikimedia.org/api/rest_v1/?spec. The description above is the provider’s own wording, not ours. Last published 2019-01-03.