submit_payment — PrivateDAO Agent Exchange MCP Tool
submit_payment
(submit payment) is one of 20 tools on the
PrivateDAO Agent Exchange
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call submit_payment from your client
- Claude Code PrivateDAO Agent Exchange submit_payment run in your project directory
- Claude Desktop PrivateDAO Agent Exchange submit_payment ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PrivateDAO Agent Exchange submit_payment ~/.cursor/mcp.json
- VS Code PrivateDAO Agent Exchange submit_payment .vscode/mcp.json
- Zed PrivateDAO Agent Exchange submit_payment ~/.config/zed/settings.json
- Windsurf PrivateDAO Agent Exchange submit_payment ~/.codeium/windsurf/mcp_config.json
- Cline PrivateDAO Agent Exchange submit_payment ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PrivateDAO Agent Exchange submit_payment ~/.gemini/settings.json
- Grok PrivateDAO Agent Exchange submit_payment .mcp.json (in your project root)
- ChatGPT PrivateDAO Agent Exchange submit_payment Settings → Connectors → Advanced → Developer mode
- Claude.ai PrivateDAO Agent Exchange submit_payment Settings → Connectors → Add custom connector
- LangChain PrivateDAO Agent Exchange submit_payment pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http pdao-agent-exchange https://agents.privatedao.org/mcpOther tools on this server
- exchange_overview
- pdao_services
- service_recommendation
- provider_integrations
- payment_guide
- execution_guide
- verify_basic
- create_paid_job
- job_status
- get_receipt
- search_agents
- register_agent
- agent_match
- logistics_request
- network_stats
- external_services
- seller_update_services
- seller_replace_endpoint
- seller_retire
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.