Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

6.2.1. Using Analyzers and the Foundry Playground

💡 First Principle: An analyzer is the configured extractor — it defines which fields to pull from a given kind of content. Prebuilt analyzers handle common scenarios out of the box; custom analyzers let you define fields for your own content. The Foundry portal's analyzers playground lets you test either without writing code.

The workflow mirrors the model and agent flows: explore in the playground (does this analyzer pull the right fields from my sample?), then move to code once it works. Prebuilt analyzers get you started immediately for things like common document types; custom analyzers are the path when your content or required fields are specific to your business.

⚠️ Exam Trap: Prefer a prebuilt analyzer when one fits your content type — building a custom analyzer when a prebuilt one would do is wasted effort. Reach for custom only when your fields or document types aren't covered by a prebuilt option. (Echoes the Phase 3 "don't over-build" judgment.)

Reflection Question: When does it make sense to build a custom analyzer instead of using a prebuilt one? What question about your content settles it?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned