> ## Documentation Index
> Fetch the complete documentation index at: https://docs.x402layer.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# Singularity Skill

> Portable full-platform skill for skills.sh-compatible agents

# Singularity Skill

The **singularity** skill is the portable full-platform package for skills.sh-compatible agents.
It packages the same high-value platform capabilities already proven in the OpenClaw-native `x402-layer` skill:

* payments integration
* endpoint creation and management
* World AgentKit endpoint benefits
* XMTP-backed support thread flows
* marketplace flows
* webhook + receipt verification
* ERC-8004 / Solana-8004 identity and reputation
* optional PAT-backed Singularity MCP guidance
* direct owner-linked dashboard API-key management guidance

> Current release: **v1.12.0**

This release adds API schema support for endpoint route documentation, enabling agents to self-discover routes from 402 challenges, powering interactive API testers on pay pages, and displaying route docs on marketplace listings.

## Install

```bash theme={null}
npx skills add https://github.com/ivaavimusic/singularity-skill --skill singularity
```

If you specifically need the OpenClaw-native distribution, use the `x402-layer` skill instead.

## What It Covers

* **Payments integration** — direct endpoint paywalls, credits, products, hosted pages, and custom UI
* **Endpoint ops** — create, manage, top up, and list endpoints
* **AgentKit benefits** — discover and use seller-defined benefits for verified human-backed agent wallets
* **Support + XMTP** — open support threads, authenticate wallets, and message through the platform support flow
* **Webhook fulfillment** — set webhook targets and verify payment signatures/receipts
* **Webhook hardening** — separate Studio HMAC verification from any app-internal settlement secret handoff
* **Marketplace flows** — browse public services and listings
* **Agent identity** — register, update, and rate ERC-8004 / Solana-8004 agents
* **Optional OWS mode** — use OpenWallet / OWS as an optional local wallet backend for pay, discover, and sign-message flows
* **Optional MCP mode** — use Singularity MCP with a dashboard PAT for owner-scoped control-plane actions
* **Direct API-key mode** — use an owner-linked `X-API-Key` for the direct worker management API, including fundraiser campaigns

## Example Prompts

```text theme={null}
Integrate crypto payments into my app with x402
Create a paid endpoint and connect it to my API
Set up webhook fulfillment and verify receipts
Pay for an endpoint with AgentKit enabled
Open a support thread and send an XMTP support message
Use my dashboard PAT to manage my endpoints through MCP
Use my owner-linked X-API-Key to create or update fundraiser campaigns
Use OpenWallet / OWS to pay for an endpoint without exporting a raw key
Buy credits for an endpoint and consume them
Register my agent on ERC-8004 and bind my endpoint
```

> Studio seller webhooks use `X-X402-Signature`, `X-X402-Timestamp`, `X-X402-Event`, and `X-X402-Event-Id`. Verify `HMAC-SHA256(timestamp + "." + rawBody)` with the webhook `signing_secret`. Keep legacy raw-secret headers only as fallback for older receivers.

## Relationship to Other Surfaces

* **singularity** = portable skills.sh package
* **x402-layer** = OpenClaw channel
* **MCP** = optional PAT-backed control plane for owner-scoped management
* **Direct worker API** = owner-linked `X-API-Key` access for endpoint, webhook, and fundraiser campaign management routes

## What It Does Not Do Yet

* It does not replace MCP for every owner-scoped action; PAT-backed control-plane work should still prefer MCP when available, while existing owner-linked API keys remain valid for the direct worker routes.
* It does not auto-generate your product UI; hosted pages and custom UI are both supported, but the agent still needs to wire the chosen route.
* It does not bypass human steps required by World App or wallet ownership. Payment, support, and registry signing still happen from the agent's configured wallet context.
* OWS is optional-first in this release; the deepest wallet-first registration and custom transaction paths still default to direct key-based signing.