What makes MagicPay notable?

3.4K downloads. Trust evidence available

How should MagicPay be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

MagicPay

Use for MagicPay payments, funding, Memory, agent email, account readiness, optional choices and human input, or payment recovery through remote MCP. Skill: MagicPay Owner: xor777 Summary: Use for MagicPay payments, funding, Memory, agent email, account readiness, optional choices and human input, or payment recovery through remote MCP. Tags: http-api:0.1.0, latest:0.4.85, magicpay:0.1.0, payments:0.1.0, secrets:0.1.0 Version history: v0.4.85 | 2026-10-07T08:22:10.979Z | user Release magicpay-v0.4.85 v0.4.84 | 2026-10-07T06:41:44.296Z | user Release magicpay-v0.4.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

3.4k

Updated

Oct 9, 2026

Version

0.4.85

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 3.4K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 3.4K downloadsadoption · observed Oct 9, 2026
Latest release: 0.4.85release · observed Oct 7, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s170j1f52qsha0313xn4j1rjsn84bn5f:magicpay

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-xor777-magicpay/snapshot"

Documentation

CLAWHUB

151,114 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: magicpay
description: Use for MagicPay payments, funding, Memory, agent email, account
readiness, optional choices and human input, or payment recovery through
remote MCP.
homepage: https://github.com/nuanu-ai/skills/tree/main/skills/magicpay
---

# MagicPay

MagicPay is the remote payment, approval, optional-choice, Memory, and reconciliation layer. The host agent remains the orchestrator.
MagicCard is MagicPay's omnipayment tool, with one unified balance across supported payment methods.
Use the exact names **MagicPay** and **MagicCard** in replies, confirmation labels, and top-up guidance; never shorten or respell them.
Approval, reservation, form fill, final action, provider submission, and
merchant confirmation are not settlement. Only a durable completed payment
operation proves settlement.

Keep the latest task and corrections through compaction/reconnect: outcome, people, dates, route, options, spending limits and “do not buy”. Old invoices are background unless requested now.
After compaction, finish the current task. Recover exact existing operation IDs; never restart a payment to reconstruct context.

Read this complete entry file once when MagicPay is first used, then load only
the focused reference needed for the current task. When the task changes, use
its matching reference. Host skills provide browser capabilities; MagicPay's
references provide its payment workflow.

## Start with the user's intent

- Balance: call `get_payment_balance` directly; no setup or reference detour is needed for an already connected account.
- Spending: `list_recent_transactions` is paginated agent-scoped workflow activity; follow `nextPage` with the same `limit`. Amounts/update times are not settled debits/dates.
Separate posted purchases, helper compute, reserves, confirmed fees and refunds; specify period, timezone and scope. Incomplete reads yield only a visible subtotal with its missing scope.
Never infer an exact remaining test allowance from incomplete activity. Wallet available balance is a different number.
- Connect or recover authentication: call `get_magicpay_capabilities`, then
`get_magicpay_status`; follow [setup](references/setup.md) and this host's
[install/connect guidance](references/runtime-setup.md) only when needed. Reuse a valid connection; never restore a CLI or local server.
- Account readiness: use `account_status`; use `show_account_status` only when
explicitly requested. [Commands and direct views](references/commands.md) covers presentation policy.
- Funding, crypto transfers, x402 purchases and retained results: follow
[payment operations](references/payment-operations.md). Generic "top up" uses `show_topup` and its returned view or link; direct addresses may accompany it.
Crypto transfers use `run_crypto_transfer` once resolved; for a named recipient, check Memory first rather than immediately asking for an address.
Price-only requests use `quote_x402_payment`: show fee-inclusive debit or maximu

_meta.json

{
  "ownerId": "kn76jq44xm9vvwz0h4grasjvax84b83f",
  "slug": "magicpay",
  "version": "0.4.85",
  "publishedAt": 1791361330979
}

references/choices.md

# Normalized Choices

Use a MagicPay choice when the agent has two to eight concrete, closed-world
options and the user's preference materially changes the next step. It is an
optional human-in-the-loop aid, not a required checkpoint. Do not create one
for a single obvious result, a factual lookup, an open-ended question, or to
replace payment, Memory, login, or other protected approval.

## Normalize messy sources

Fetch or observe the current source first. Turn comparable results into the
small stable `request_choice` shape:

- `prompt`: a short question plus only the shared context needed to choose.
- `notes`: optional shared decision-relevant caveats, rendered after the options.
  Put local-time conventions, price freshness and material limitations common
  to every option here instead of making the question a long paragraph.
- `id`: opaque and unique within this request; never derive authority from it.
- `type`: a lower-case semantic hint such as `flight`, `hotel`, `product`,
  `plan`, or `service`; unknown content uses a useful generic key.
- `title`: short, unique human label.
- `subtitle` and `description`: product/seller context and the tradeoff that matters.
- `attributes`: ordered `{key,label,value}` facts that compare across options.
  Keep zero and false values. Include units and qualification in the value.
- `price`: display text with currency, billing interval, per-unit/total, and tax
  qualification where the source supplies them.
- `images`: objects with `url`, explicit `kind: image` or `kind: logo`, and
  optional `alt`. Preserve source order; a text-only option may omit images.
- `url`: the exact source/detail page. Opening it never selects the option.

Use actual current source facts. Do not convert payment-network alternatives
for one endpoint into duplicate products, claim travel availability without
dates/occupancy, or invent a missing price, baggage allowance, stock state, or
commercial term. Narrow a larger result set by relevance before asking.
Keep option-specific terms in that option's description or attributes, not in
shared notes. For flights, include observed date, route and departure/arrival
times on each option so its selected receipt is self-contained. Preserve the
currency, total/per-person basis and supplied fare qualifications in `price`.
Send these fields as plain text; the host owns bold titles/prices and note
formatting. Never add HTML or Markdown decorations to the stored choice fields.

Keep retrieval-provider attribution (such as "from Google Flights"), API/tool
names and "official"/"unofficial" implementation labels out of customer-facing
choice text. State the actual decision-relevant limitation instead: baggage
allowance is not confirmed, the price must be rechecked before booking, or
selecting an option does not book or pay. Preserve observed airline, seller and
service identities and all material product terms; never turn an unknown fact
into a reassuring claim. If the user explicitly asks about the

references/commands.md

# MCP Routing Map

MCP discovery is authoritative for exact arguments and results. This reference
only distinguishes starting routes, continuations, and explicit presentation.
Use opaque IDs exactly as returned.

## Starting routes

| User intent | Start here |
| --- | --- |
| Connect or recover | `get_magicpay_capabilities`, then `get_magicpay_status` |
| Account readiness | `account_status` |
| Identity-verification help | `help_identity_verification` |
| Recent user activity | `list_recent_transactions` |
| Recent charges on a checkout's card | `list_card_transactions` with its checkout session ID |
| Balance | `get_payment_balance` |
| Generic top-up | `show_topup` |
| Funding methods, link, or addresses | Use the exact funding action requested |
| New crypto transfer | `run_crypto_transfer` |
| x402 price before payment | `quote_x402_payment`; show the complete price and stop |
| Authorized purchase of a known raw x402 resource | `run_x402_payment` with the exact `httpRequest` envelope and accepted quote reference when previewed |
| Known checkout destination | `create_checkout_session` |
| Unknown product or provider method | `search_provider_methods` |
| Inspect a returned MCP provider | `list_provider_mcp_tools` |
| Use an advertised provider tool | `call_provider_mcp_tool` |
| Optional seller comparison | `check_merchant` with up to ten documented seller requests |
| Optional choice without an existing session | `begin_request_session`, then `request_choice` |
| Existing payment status | `get_payment_operation` |
| Invoice or original-document status | `get_payment_operation` for the exact operation; see [invoices.md](invoices.md) |
| Attach a PDF original or supported HTML receipt link | `attach_payment_invoice` with the exact operation and supported host file input; see [invoices.md](invoices.md) |
| Read agent correspondence | `list_agent_email_threads`, `read_agent_email_thread` for the exact owned agent |
| Prepare and send agent email | `prepare_agent_email`, normal `wait_request` / supported decision flow, then `send_agent_email` when directed; see [email.md](email.md) |
| Recover an uncertain email send | `get_agent_email_send` with the same send and agent IDs |
| Save or update supplied Memory values | `save_memory_item`, including protected values; exact item/revision for updates |
| Manage Memory metadata | Use the value-free CRUD action matching the intent |
| Use Memory in an active session | `get_memory_footprint`, then exact `materialize_memory_items` or v3 `resolve_browser_form_values` |
| Existing request, session, or operation | For payment execution, use only its returned `nextAction`; authorized read-only diagnosis remains available |

A request that already names a merchant, recipient, or site does not require
provider discovery: find its official destination in the host browser, then
create the checkout session.

## Silent work and presentation

Operational reads, mutations, approval, waits, status checks, and recon

references/compare-before-buy.md

# Compare Before Buy

Use this when a user has selected a retail product and might benefit from the
same item at a lower delivered price. The host agent researches current seller
pages with its normal search and browser tools; MagicPay handles the chosen
checkout. This is an optional suggestion, not a required stop before buying.

Offer a quick check once when the seller is flexible. If the user asks for a
cheaper source, compare directly. Keep the purchase direct when the user chose
a particular seller, speed matters, or payment is already in progress. Do not
silently change a chosen merchant.

Match the actual item: model, variant (such as size, color, or capacity),
condition, quantity, and bundle. Use product identifiers when available, but
do not invent them. A near match is an alternative, not the same item; suggest
alternatives only if the user wants them. For subscriptions or services, terms
and fulfillment rights also have to match.

Check a few credible current offers as useful. Compare the delivered total,
including shipping, tax, and fees when shown, along with stock, delivery time,
region, returns, and warranty. State what is unknown; a lower listing price
alone does not establish savings. Verify the chosen offer and final total on
the merchant's checkout page.

Present the original and any better offer with source links, comparable totals
or unknowns, and the trade-off that matters. Recommend when one choice is
clear. Use [choices](choices.md) only when a material user preference remains;
research or a choice is not payment approval.

Choose the item and merchant before starting [browser checkout](host-browser-payments.md).
An existing MagicPay session or approval cannot be transferred to another
seller. If payment is pending or uncertain, follow [statuses and recovery](statuses.md)
for the exact operation rather than starting a replacement. A later purchase
from another merchant needs its own checkout and approval after the original
is safely closed and the user authorizes it.

Github ReposUpdated 4h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.