For AI agents: A machine-readable capability summary is available at /skill.md.
For detailed guidance on writing effective goals, see the Goal Prompting Guide.
Choosing the Right Endpoint
| Use Case | Endpoint | Why |
|---|---|---|
| Quick tasks (<30s) | POST /v1/automation/run | Simpler code, immediate results |
| Long-running tasks | POST /v1/automation/run-async | Non-blocking, poll for results |
| Large batches | POST /v1/automation/run-async | Submit all at once, monitor progress |
| Real-time feedback | POST /v1/automation/run-sse | Stream progress events to users |
| Fire and forget | POST /v1/automation/run-async | No need to wait for completion |
Quick Decision Guide
1
Need real-time progress updates?
Yes → Use
/run-sse (SSE streaming)2
Task takes longer than 30 seconds?
Yes → Use
/run-async + polling3
Submitting multiple tasks at once?
Yes → Use
/run-async (parallel submission)4
Simple, quick task?
Use
/run (synchronous)Writing Effective Goals
Thegoal field is a natural language instruction that tells Mino what to accomplish. Your job is to remove ambiguity—the more explicit your goal, the higher your success rate.
Goal Prompting Guide
Learn how to write goals that succeed on the first try, with task-specific templates and examples.
Quick Reference: Goal Style by Task Type
| Task Type | Recommended Style | Key Principle |
|---|---|---|
| Price/product extraction | Specific, constrained | List exact fields, exclude extras |
| Form filling | Natural language | Describe the person/entity |
| Multi-step workflows | Numbered steps | Enable cross-step memory |
| Batch execution | Minimal, strict schema | Only essential fields |
Interpreting Responses
Understanding Run Status
| Status | Meaning | Next Action |
|---|---|---|
PENDING | Queued, not started | Wait and poll |
RUNNING | Currently executing | Wait and poll |
COMPLETED | Finished (check result) | Parse result field |
FAILED | Infrastructure error | Check error.message |
CANCELLED | Manually stopped | N/A |
Response Handling Pattern
Streaming Response Handling (SSE)
For/run-sse, handle events progressively:
Common Integration Patterns
Pattern 1: Simple Extraction
Pattern 2: Batch Processing
Pattern 3: Retry with Stealth Mode
For AI Agents
If you are an AI agent integrating Mino as a tool, follow these patterns for reliable results.Specify Output Schema Explicitly
Don’t just say “return as JSON.” Provide the exact structure:Include Termination Conditions
Tell the agent when to stop:Handle Edge Cases Explicitly
Request Structured Error Reporting
Rate Limiting
- Concurrency limit varies by plan (check your dashboard)
- Implement exponential backoff for 429 errors
- Space requests 1-2 seconds apart for bulk operations