sap-payments-x402

sap-payments-x402 is a skill for Claude Code, Codex from OOBE-PROTOCOL/sap-mcp. It costs 0 tokens per session (3,022 once invoked), scanned A, original, MIT.

A set of tools for handling SAP x402 payments, balances, subscriptions, paid API requests, and monetized hosted MCP tools. x402 is a payment flow used to authorize access to paid web services.

In plain words
What is it for?
Use it to inspect payment profiles, check balances, make paid tool calls, manage subscriptions, register agents, and verify payment receipts.
Why use it?
It helps an agent check payment details and available funds before making paid requests, then prepare, process, and verify those transactions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inspect payment profiles, check balances, make paid tool calls, manage subscriptions, register agents, and verify payment receipts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oobe-protocol/sap-mcp/sap-payments-x402
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add OOBE-PROTOCOL/sap-mcp --skill sap-payments-x402
Clone the repo
git clone --depth 1 https://github.com/OOBE-PROTOCOL/sap-mcp

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sap-payments-x402

README.md
[![agentmods](https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-payments-x402/github.svg)](https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-payments-x402)
Your own site
<a href="https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-payments-x402"><img src="https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-payments-x402/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sap-payments-x402

Your own site · 80×15
<a href="https://agentmods.dev/skills/oobe-protocol/sap-mcp/sap-payments-x402"><img src="https://agentmods.dev/badge/skills/oobe-protocol/sap-mcp/sap-payments-x402.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,022 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03022
Opus 5 $0.00000 $0.01511
Sonnet 5 $0.00000 $0.00604
Haiku 4.5 $0.00000 $0.00302

Measured 12d ago against content hash 87a68c3fee28, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sap-payments-x402 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sap-payments-x402/SKILL.md · 251 lines

How it starts

The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SAP Payments X402

Use this skill for SAP x402 payment context, balances, subscriptions, paid API workflows, and hosted SAP MCP x402/pay.sh monetization.

Tools

  • sap_x402_prepare_payment
  • sap_x402_get_balance
  • sap_payments_profile_current
  • sap_payments_wallet_guard
  • sap_payments_process_status
  • sap_payments_call_paid_tool
  • sap_payments_call_external_x402
  • sap_payments_register_agent
  • sap_payments_update_agent
  • sap_payments_finalize_transaction
  • sap_payments_prepare_challenge
  • sap_payments_sign_challenge
  • sap_payments_verify_receipt
  • sap_prepare_action
  • sap_x402_paid_call
  • sap_create_subscription
  • sap_fund_subscription
  • sap_cancel_subscription
  • sap_fetch_subscription

Flow

  1. Inspect agent profile and pricing with sap_get_agent_profile.
  2. Use sap_x402_prepare_payment before building a paid request.
  3. Use sap_x402_get_balance before assuming a depositor can pay.
  4. Use subscription tools only after explaining amount, cadence, and cancellation path.

Hosted MCP Monetization

Canonical hosted endpoint: https://mcp.sap.oobeprotocol.ai/mcp.

Remote /mcp deployments can require x402 v2 payment for paid tools/call requests. Local stdio usage remains free and should not attempt x402 payment. Do not treat hosted 402 Payment Required as a failure; it is the expected payment handshake. Do not silently bypass hosted paid tools by switching to a local free stdio MCP server unless the user explicitly asks for local execution. If sap_profile_current says the hosted server has no signer, treat that as the non-custodial model: OOBE does not hold user keys. Paid and value-moving hosted calls still proceed through x402/pay.sh plus the user's local SAP profile or external signer.

  • Free: MCP handshake, tools/list, prompts/list, resources/list, sap_profile_current, sap_agent_start, sap_agent_runtime_status, sap_agent_next_action, sap_estimate_tool_cost, sap_pricing_catalog, repair/status tools, local payment bridge control, transaction preview/finalization helpers, SOL/SPL/x402 balance readiness, single-asset price snapshots, and memory/audit helpers.
  • Micro read: exact SAP agent/profile reads, compact sap_list_agents pages with limit <= 20, sap_get_network_overview, SNS availability, escrow state, and lightweight trader/perps context.
  • Read premium: sap_discover_agents, sap_list_all_agents, full/enriched or large sap_list_agents pages, enriched holdings, indexed discovery, network stats, protocol/capability indexes, DAS, token lists, quotes/routes, and OHLCV/history.
  • Builder: batch SNS/domain checks, analytics, transaction builders.
  • Value action: fixed fee plus configured basis-points fee when public USD notional fields are present.

Read the full file on GitHub · 251 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 251 lines · 0 tokens per session scan A 87a68c3fee28

Subscribe to this mod's changes

sap-payments-x402 is a skill published in the GitHub repository OOBE-PROTOCOL/sap-mcp (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,022 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.