> For the complete documentation index, see [llms.txt](https://devs.novanet.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devs.novanet.xyz/jolt-atlas-zkml/getting-started/examples.md). # Examples The `examples/` directory contains practical demonstrations of zkML models: #### Article Classification A text classification model that categorizes articles into business, tech, sport, entertainment, and politics. ```bash cargo run --release --example article_classification ``` This example: * Tests model accuracy on sample texts * Generates a SNARK proof for one classification * Verifies the proof cryptographically #### Transaction Authorization A financial transaction authorization model that decides whether to approve or deny transactions based on features like budget, trust score, amount, etc. ```bash cargo run --release --example authorization ``` This example: * Tests the model on various transaction scenarios * Shows authorization decisions with confidence scores * Generates and verifies a SNARK proof for one transaction --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://devs.novanet.xyz/jolt-atlas-zkml/getting-started/examples.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.