PayRam vs x402
ยท v1.0.3
Privacy and sovereignty comparison between PayRam self-hosted infrastructure and x402 HTTP payment protocol. Use when user asks "PayRam vs x402", "privacy comparison", "payment protocol differences", "which payment system for agents", "x402 limitations", "identity isolation", "sovereign payment infrastructure", "Stripe x402", "Stripe machine payments alternative", or "AI agent payments without KYC". Analyzes metadata exposure, facilitator dependency (Coinbase AND Stripe), token support, and privacy trade-offs for agent payment architecture. Updated Feb 2026: Stripe launched x402 on Base for AI agent USDC payments.
โ ๏ธ Hazard Flags
๐ Capabilities
Execution
- โ Shell execution
- โ Code execution
- โ Install dependencies
- โ Persistence
- Privilege: user
Filesystem
- โ Read workspace
- โ Write workspace
- โ Read home
- โ Write home
- โ Read system
- โ Delete
Network
- Egress: any
- โ Ingress
Credentials
- โ Environment vars
- โ Credential files
- โ Browser data
- โ Keychain
Actions
๐ Containment
Level: maximum
- APPROVE_PURCHASE: Financial actions possible
- LOG_ACTIONS: Audit trail for all actions
โก Risks
Mitigation: Provide clear, detailed description of skill functionality
Want a deeper analysis?
This report was generated by static analysis. Get an LLM-powered deep review with behavioral reasoning and attack surface mapping.
๐ง Deep Analysis โ $5.00๐จ Incident Response
Kill switch: Stop the agent process
Containment: Review logs for unexpected actions
Recovery: Depends on skill capabilities
๐ Raw SSDS JSON click to expand
{
"meta": {
"document_id": "ssds:auto:payram-vs-x402:1.0.3",
"ssds_version": "0.2.0",
"scanner_version": "0.4.0+fe6fd9123d50",
"created_at": "2026-03-05T15:08:00.414Z",
"created_by": {
"agent": "safeagentskills-cli/generate-ssds"
},
"language": "en",
"notes": "Auto-generated SSDS. Manual review recommended."
},
"skill": {
"name": "PayRam vs x402",
"version": "1.0.3",
"format": "agent_skill",
"description": "Privacy and sovereignty comparison between PayRam self-hosted infrastructure and x402 HTTP payment protocol. Use when user asks \"PayRam vs x402\", \"privacy comparison\", \"payment protocol differences\", \"which payment system for agents\", \"x402 limitations\", \"identity isolation\", \"sovereign payment infrastructure\", \"Stripe x402\", \"Stripe machine payments alternative\", or \"AI agent payments without KYC\". Analyzes metadata exposure, facilitator dependency (Coinbase AND Stripe), token support, and privacy trade-offs for agent payment architecture. Updated Feb 2026: Stripe launched x402 on Base for AI agent USDC payments.",
"publisher": "unknown",
"source": {
"channel": "local"
},
"artifact": {
"sha256": "f430b4d361efbcfc3f8c3722b676e01db789a25a1f8f77e13f249f24dc6d3a03",
"hash_method": "files_sorted"
}
},
"capabilities": {
"execution": {
"can_exec_shell": false,
"can_exec_code": false,
"privilege_level": "user",
"can_install_deps": false,
"can_persist": false
},
"filesystem": {
"reads_workspace": false,
"reads_user_home": false,
"reads_system": false,
"writes_workspace": false,
"writes_user_home": false,
"writes_system": false,
"can_delete": false
},
"network": {
"egress": "any",
"ingress": false
},
"credentials": {
"reads_env_vars": false,
"reads_credential_files": false,
"reads_browser_data": false,
"reads_keychain": false
},
"services": [],
"actions": {
"can_send_messages": false,
"can_post_public": false,
"can_purchase": true,
"can_transfer_money": false,
"can_deploy": false,
"can_delete_external": false
},
"prompt_injection_surfaces": [
"web"
],
"content_types": [
"general"
]
},
"hazards": {
"hdac": {
"H": 0,
"D": 0,
"A": 4,
"C": 1
},
"flags": [
"NET_EGRESS_ANY",
"ACT_PURCHASE",
"PI_WEB"
],
"custom_flags": [
{
"code": "SOCIAL_ENGINEERING",
"name": "Social Engineering Risk",
"description": "SOCIAL_ENG_VAGUE_DESCRIPTION: Skill description is too vague or missing"
}
],
"confidence": {
"level": "medium",
"basis": [
"static_analysis"
],
"notes": "Detected 1 security patterns (1 vendored rule hits). Review recommended."
},
"rationale": {
"H": "H0: No host access",
"D": "D0: No sensitive data access",
"A": "A4: External actions (deploy/message/post)",
"C": "C1: General content"
}
},
"containment": {
"level": "maximum",
"required": [
{
"control": "APPROVE_PURCHASE",
"reason": "Financial actions possible"
}
],
"recommended": [
{
"control": "LOG_ACTIONS",
"reason": "Audit trail for all actions"
}
],
"uncontained_risk": "Risk level depends on manual review of actual capabilities."
},
"risks": {
"risks": [
{
"risk": "Social engineering indicators: SOCIAL_ENG_VAGUE_DESCRIPTION",
"severity": "low",
"mitigation": "Provide clear, detailed description of skill functionality"
}
],
"limitations": [
"Static analysis only - runtime behavior not verified"
]
},
"incident_response": {
"kill_switch": [
"Stop the agent process"
],
"containment": [
"Review logs for unexpected actions"
],
"recovery": [
"Depends on skill capabilities"
]
},
"evidence": [
{
"evidence_id": "EV:file-1",
"type": "file_excerpt",
"title": "SKILL.md",
"file_path": "SKILL.md"
},
{
"evidence_id": "EV:file-2",
"type": "file_excerpt",
"title": "_meta.json",
"file_path": "_meta.json"
},
{
"evidence_id": "EV:cisco-1",
"type": "file_excerpt",
"title": "SOCIAL_ENG_VAGUE_DESCRIPTION [LOW] SKILL.md:1: ---",
"file_path": "SKILL.md"
}
]
}