“Best practices for microflow error handling AND logging”
“SDK patterns for creating entities with associations”
Ask for Code
“Show me code for creating a microflow with SDK”
“Give me a working example of entity creation”
Request Specifics
“What SDK version supports [feature]?”
“Show me the exact API for [method]”
Follow Up
“Tell me more about that”
“Show me an example”
“What are the common mistakes?”
Quick Reference - API Endpoints
If you’re building integrations:
Endpoint
Method
Use For
/health
GET
Health check
/status
GET
Full status with capabilities
/search
POST
Hybrid search (body: {"query": "..."})
/query
POST
Knowledge query (body: {"topic": "..."})
/best-practice
POST
Best practices (body: {"scenario": "..."})
/beast-mode
GET
Research protocol
/analytics
GET
Usage statistics
/harvest-status
GET
Harvest schedule
/dashboard
GET
Visual analytics (HTML)
Example Conversations
Example 1: SDK Development
You: How do I create a microflow with the Mendix Model SDK?
GPT: [Returns detailed SDK patterns with code examples]
You: Show me error handling for that
GPT: [Returns try/catch patterns and common pitfalls]
You: What are the common mistakes?
GPT: [Returns troubleshooting knowledge]
Example 2: Best Practices
You: Best practice for large data handling in Mendix
GPT: [Returns pagination, batching, XPath optimization tips]
You: How do I implement pagination?
GPT: [Returns specific implementation patterns]
Example 3: Research Mode
You: Use beast mode to research custom widget state management
GPT: [Returns exhaustive research protocol with 5 tiers of sources]
Troubleshooting
“I don’t have information about that”
Try rephrasing or use beast mode:
“Use beast mode to research [your topic]”
Generic responses
Be more specific:
Instead of “widgets” → “pluggable widget development in Mendix 10”