Nano WizPay Agent API
Agent Connect has been replaced by Nano WizPay Agent API. The old Agent Connect model is retired and deprecated. Email OTP onboarding, scoped session tokens, wallet profiles, the old faucet flow, payment intents, approve-intent, and execute-transfer flows are no longer the production agent API. The production Nano WizPay Agent API is:nano-wizpay repo remains:
Execution Model
Nano WizPay Agent API is non-custodial. It never stores private keys, never signs user transactions, never executes user funds, and never custodies user funds. The API prepares routes and execution instructions. The agent, user wallet, frontend, SDK, raw calldata executor, or Circle CLI executes the returned calldata or commands. Free read-only endpoints:GET /servicesGET /contracts/statusPOST /swap/quotePOST /payroll/plan
POST /swap/preparePOST /payroll/prepare
- Call the prepare endpoint without payment.
- The API returns
PAYMENT_REQUIREDwith the required fee details. - Pay the
0.003 USDCservice fee to the service fee collector. - Retry the same prepare request with:
Production Endpoints
Contracts
Service fee:
Curl Examples
List Services
Check Contract Status
Request Swap Quote
/swap/quote is read-only. It does not create a transaction, collect a fee, sign anything, or move funds.
Plan Payroll
/payroll/plan is read-only. It returns a payroll plan for review before any paid prepare call.
Prepare Swap Without Payment
Prepare Payroll Without Payment
Payroll Execution Note
Payroll prepare responses include batch calldata for SDK, frontend, and raw calldata executors. For Circle CLI demos, prefer therouteAndPay fallback commands from circleCliFallback.commands. Circle CLI may fail with overloaded array-based batchRouteAndPay functions, so demos should use the fallback command set when available.
Safety Requirements for Agents
Agents integrating with Nano WizPay Agent API should:- Treat read-only responses as planning data, not completed execution.
- Show the user the payment, route, token, recipient, and fee details before asking them to execute anything.
- Require the user’s wallet or Circle CLI environment to sign and submit transactions.
- Never ask WizPay API to store, receive, or sign with private keys.
- Never treat an unpaid prepare response as executable.
- Never replace a missing official route with synthetic pricing or a legacy fallback.
Production Proof
Latest verified Arc testnet transactions:Deprecated Agent Connect References
Agent Connect formerly usedhttps://agent.wizpay.xyz and an onboarding/session model built around email OTP, scoped tokens, wallet profiles, faucet calls, payment intents, approvals, and execute-transfer calls.
That model is retired. New integrations should use https://api.wizpay.xyz and the Nano WizPay Agent API endpoints documented above.