Yieldagentx402
Wire policy-gated x402 agent payments into MCP with TEE-backed receipts when you build autonomous workflows that must pay for APIs without holding user funds.
Overview
YieldAgentX402 MCP is a MCP server for the Build phase that provides 18 policy-gated x402 tools with TEE receipts for non-custodial agent payment workflows.
What is this MCP server?
- Exposes 18 MCP tools for YieldAgentX402 agent payment and policy workflows
- Policy-gated x402 design with TEE receipts and explicit no-custody positioning
- npm package agentx402-mcp-server (v1.0.4) with stdio transport
- Requires YAX_API_KEY and YAX_AGENT_ID from yieldagentx402.app dashboard
- Optional YAX_MCP_ENDPOINT override defaulting to https://api.yieldagentx402.app/mcp
- 18 MCP tools documented in catalog description
- Package version 1.0.4 (agentx402-mcp-server)
- Default remote MCP API base https://api.yieldagentx402.app/mcp
What problem does it solve?
You want agents to pay for services under hard policies and auditable receipts, but bolting x402 and custody rules into custom code is slow and error-prone.
Who is it for?
Indie builders shipping agent products that need metered API access, x402 rails, and policy-bound spend without building a payment MCP from scratch.
Skip if: Simple SaaS with Stripe Checkout only and no autonomous agent spend—or teams that cannot manage API keys and agent IDs.
What do I get? / Deliverables
Your agent calls gated x402 tools with dashboard-managed identity and receives TEE receipts while funds stay out of MCP custody.
- Agent-invokable x402 payment and policy operations across 18 tools
- TEE-backed receipt artifacts for auditable agent spend
- Integrated agent identity wired to YieldAgentX402 backend
Recommended MCP Servers
Journey fit
Build / agent-tooling is the canonical shelf because the server extends how agents act in production-like payment flows during product construction, not later marketing or error triage. Agent-tooling captures x402, dashboard agent IDs, and the 18-tool surface meant for autonomous commerce and gated spend policies.
How it compares
Policy-gated x402 payment MCP with 18 tools, not a generic Stripe skill or manual finance spreadsheet workflow.
Common Questions / FAQ
Who is YieldAgentX402 MCP for?
Builders creating agent-native products that must authorize and record x402 payments under policy, with TEE receipts and no MCP custody of balances.
When should I use YieldAgentX402 MCP?
Use it while building agent-tooling when workflows need to discover, request, or settle x402 payments through MCP instead of one-off HTTP scripts.
How do I add YieldAgentX402 MCP to my agent?
Install agentx402-mcp-server from npm, set YAX_API_KEY and YAX_AGENT_ID, optionally YAX_MCP_ENDPOINT, add the stdio server to your MCP client, and restart.