Connect over MCP or API. Every paid run is quoted first, checked against your limits, and saved with a receipt.
Paste this into Codex, Claude Code, Cursor, or another agent client.
set up https://askenchant.com/agents/SKILL.mdSet a budget once. Review only the runs that need you.
Get a quote before the provider is called.
Pause paid or sensitive work for review.
Set a maximum for each run and the workspace.
See the provider, route, charge, and result.
Match the job to a provider.
Review the route, inputs, and price.
Continue, change it, or stop.
See what ran and what it cost.
Choose one. Nothing runs until you approve the quote.
Check the entry-level plans from Notion, Linear, and Slack in one table.
Use workflowSummarize the week's news on agent payments, with sources, risks, and next steps.
Use workflowFind 15 US fintech companies and the most relevant growth or partnerships role.
Use workflowTurn the current top 20 Hacker News stories into a clean CSV.
Use workflowSign in, add a balance, and test the connection. Most clients work with the hosted MCP endpoint below.
Checking the current browser session.
Use your email. We will send a six-digit code.
Add the balance your agent can spend. Pay by card or transfer from a supported wallet.
For CI, scripts, and clients without OAuth.
Includes execution, funding, receipts, and hosted MCP access.
Sign in first to create an API key.
Run one live request to check planning, payment, and execution.
Sign in first to run the setup test.
Choose how paid providers are settled. This is separate from how you add money to the Enchant balance: card or stablecoin top-ups create credits, while direct wallet mode pays the provider from the agent host.
ENCHANT_EVM_PRIVATE_KEY locally. Enchant prepares the request but never receives the signing key.Add credits once and let Enchant pay providers from its shared treasury. Card checkout is available here; agent clients can also start Base or Tempo wallet top-ups.
Skip the Enchant balance for a supported route. The agent host needs stablecoin and native gas, and the user approves the local signing policy.
Use this URL for OAuth-capable clients. Use API keys only when a client requires manual bearer authentication.
Use these details only for REST clients, bearer-token installs, or direct-wallet settlement.
Connection metadata, routes, scopes, and readiness checks.
REST contracts for clients that generate typed request code.
OAuth-capable remote MCP endpoint for modern agent clients.
Small client helper with polling, receipts, and direct-wallet hooks.
Use this for REST clients and bearer-token MCP installs.
ENCHANT_BASE_URL=https://askenchant.com
ENCHANT_API_KEY=<ENCHANT_API_KEY>Keep this only on the agent host that signs Base or Tempo requests.
ENCHANT_EVM_PRIVATE_KEY=<LOCAL_EVM_PRIVATE_KEY>Replace the placeholder with a full-access key for manual REST testing.
curl -sS https://askenchant.com/api/agent/v1/run \
-H "Authorization: Bearer <ENCHANT_API_KEY>" \
-H "Content-Type: application/json" \
-d '{"prompt":"Search Reddit for recent posts about AI agents and summarize the main themes"}'