Skip to main content

​
Payment Options

There are three public payment modes you can reason about safely.

​
1. Dashboard-managed wallet

Best when you want the easiest operational flow.
  • create or import an agent wallet in the dashboard
  • generate a connect string or gateway-safe credential bundle
  • let the wallet pay for gateway calls within the configured limits
Use this when the operator wants a smoother repeated-call workflow. If you are using the local Apiosk MCP package, import that connect string through apiosk_get_started so the package can save it locally and verify the setup with a first call.

​
2. Raw x402 proof flow

Best when you want direct control of the payer.
  • call the gateway without proof
  • receive HTTP 402
  • sign the payment challenge with your own payer
  • retry with x-payment
Use this when you already have your own payment orchestration or want the most explicit proof path.

​
3. Unpaid routes

Some routes can be configured as free. In those cases the gateway does not require payment before forwarding the request.

​
Recommendation

  • use managed wallet mode for operator dashboards and repeated agent workflows
  • use raw x402 mode for protocol-level integrations and explicit payment control
  • use unpaid mode only when the listing or endpoint is intentionally public
  • for local MCP installs, start with apiosk_get_started and let it tell you whether you are ready or still need funding