Introducing Enchant for Agents (Beta)
Beta: Enchant for Agents is currently in beta.
An agent should not need a custom integration and billing relationship for every paid capability it may use.
Enchant for Agents gives coding agents and other tool-using runtimes one connection to a catalog of research, media, browser, data, communication, travel, storage, and other specialist services.
Connect once. Let the agent discover what is available. Keep pricing and payment control attached to every run.
One endpoint for many services
Enchant exposes a hosted MCP endpoint at https://askenchant.com/mcp. OAuth-capable clients can connect directly. Scripts, CI environments, and clients without OAuth can use an API key.
Install guides are available for Codex, Claude Code, Cursor, VS Code, GitHub Copilot CLI, and ChatGPT. The connection gives each client the same Enchant account, balance, and default payment setting.
Enchant also publishes an installable skill for coding agents. The skill teaches an agent how to check account state, discover services, inspect a service schema, plan a request, run it, poll asynchronous work, and retrieve receipts.
Discover before choosing
The catalog is designed for runtime discovery. An agent can search for services that fit a task, inspect the request requirements, and compare the returned candidates before it commits to a route.
A reliable paid workflow looks like this:
- Check the account and funding state.
- Discover services relevant to the task.
- Inspect the selected service and its schema.
- Plan the request and review the price.
- Run with Enchant credits or prepare supported direct-wallet execution.
- Poll asynchronous jobs until the result is final.
- Retrieve the receipt when the payment trail matters.
Planning comes before execution. An agent does not need to invent endpoint paths, guess a provider schema, or start a paid run before it understands the request.
Two ways to fund a run
The simplest path is Enchant-funded execution. Add credits to the account, let the agent prepare the request, and approve the run against the shared balance. Credits can be added through hosted card checkout or supported wallet top-ups.
For supported routes, an agent can instead prepare a direct Base x402 or Tempo MPP payment for local wallet execution. The signing key stays on the agent host. Enchant prepares the provider call and payment context without taking custody of the local key.
Not every route supports every execution mode. The agent workflow reports the available choices and can fall back to Enchant-funded execution when direct settlement is unavailable.
Controls travel with the account
Access to a broad service catalog needs a clear payment boundary.
Enchant uses Conto to evaluate limits and approval rules before a paid provider call. An account can define how much an agent may spend, when a request needs approval, which providers are allowed, and whether a fallback route may be tried.
The result and the spend record stay connected. That gives an operator a consistent trail from the original task to the selected service, approved price, completed run, and receipt.
This is the same strategic idea behind the Enchant consumer workspace. Software can choose paid services dynamically, while Conto keeps policy and payment evidence in the path.
Connect a client
New accounts receive a small credit for a connection test. The setup console checks the account, funding choice, and execution path before you connect a client.
Use hosted MCP when the client supports OAuth. Use manual API access for scripts or environments that need a bearer token. Start with planning-only access when the agent should inspect and quote services without permission to execute paid work.