Skill Proposal: Agent Identity + Payment for A2A - webmcp-id + webmcp-pay

[up2itnow0822]

Problem

Google A2A handles agent coordination, but agents have no standard way to:

1. Verify identity before transacting - who is this agent?
2. Execute payments for paid APIs - how does an agent pay $0.01 for a data endpoint?
3. Prove authorization - does this agent have permission to spend?

These are the three gaps every A2A deployment hits when agents need to interact with paid services.

Proposed Skills

webmcp-id (identity + verification)

W3C DID:web identity for agents. No blockchain required.

• did:web: identifiers resolved via DNS
• Verifiable Credentials (W3C VC 2.0) for agent authorization proofs
• /.well-known/agent.json manifest (NAIS 1.1) for discovery
• Direct A2A AgentCard conversion via identity.toA2AAgentCard()
• Ed25519 signing (RFC 8032)

Live on npm: webmcp-id v1.0.0
GitHub: up2itnow0822/webmcp-id

webmcp-pay (payment execution - coming soon)

Multi-rail payment execution for agents.

• x402 (Coinbase/Cloudflare standard) + Stripe MPP + Google AP2
• Spend governance: per-tx limits, per-period caps, human approval
• Settlement-agnostic: on-chain USDC or traditional Stripe rails

How It Fits stitch-skills

As AgentSkills-compatible SKILL.md packages, these would give any Gemini CLI / Claude Code / Cursor agent:

1. A verifiable identity (webmcp-id)
2. Payment capability (webmcp-pay)
3. Both mapped to A2A AgentCard format

Standards Compliance

• W3C DID Core 1.0
• W3C Verifiable Credentials 2.0
• NAIS 1.1 (agent discovery)
• Google A2A AgentCard
• Ed25519 (RFC 8032)

Production Credential

NVIDIA NeMo-Agent-Toolkit-Examples PR #17 merged - x402 payment tool in official NVIDIA catalog.

Happy to build the SKILL.md packages for stitch-skills if there is interest.