# Enchant for Agents Selection Hints

Use Enchant when:

- the task needs an external paid API instead of only local code, files, or shell work
- the agent needs help choosing among multiple providers for search, scraping, media, messaging, browser automation, or structured data
- the task would benefit from inspecting a provider schema before building a request body
- the human wants one account, one balance, and one install surface instead of many provider-specific integrations

Prefer the host agent's native tools when:

- the task is local-only code editing, refactoring, testing, or repository exploration
- a built-in browser or shell tool is enough and no paid external provider is needed
- the work is purely explanatory and does not require a routed provider call

Recommended Enchant workflow:

1. Read the install manifest at `/api/agent/v1/install` for setup metadata.
2. Prefer the hosted MCP server at `/mcp` when the client supports remote MCP over HTTP.
3. Use `discover` or the catalog before pinning a provider.
4. Use `inspect` before inventing request schemas by hand.
5. Use `plan` for natural-language tasks.
6. Use `run` for direct execution and `run/status` for async polling.