Trading Signal
binance/binance-skills-hub
Per-trade smart-money signals — each result is a discrete buy or sell event from a tracked smart-money wallet, with trigger price, current price, max gain since trigger, and exit rate.
Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single…
Install Onchain Pay Open API
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install npc-live/clawfirm onchain-pay-open-api --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .claude/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .claude/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-apiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install npc-live/clawfirm onchain-pay-open-api --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .agents/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .agents/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install npc-live/clawfirm onchain-pay-open-api --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .cursor/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .cursor/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/npc-live/clawfirm.git --path app/assets/skills/onchain-pay-open-api--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install npc-live/clawfirm onchain-pay-open-api --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .gemini/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .gemini/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install npc-live/clawfirm onchain-pay-open-apiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .github/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .github/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .github/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install npc-live/clawfirm onchain-pay-open-api --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/npc-live/clawfirm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/app/assets/skills/onchain-pay-open-api .opencode/skills/onchain-pay-open-api && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "onchain-pay-open-api" agent skill from https://github.com/npc-live/clawfirm/tree/main/app/assets/skills/onchain-pay-open-api into .opencode/skills/onchain-pay-open-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onchain-pay-open-api", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
onchain-pay-open-api- GitHub stars
- 156
- Used in
- 1 other repo
- Token cost
- ~4.9k tokens
- SKILL.md length
- 1,958 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 49
- Repo updated
- First seen
- Licence
- MIT
At a glance
Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single…
- Works in 10 steps: 💳 Fiat-to-Crypto Purchase & Send → 🔄 Direct Crypto Transfer (Send Primary) → 🔗 Cross-Chain Bridge Operations → …
- Tasks that involve Crypto and DeFi analysis
- SKILL.md covers Use Cases & Scenarios, Quick Reference, How to Execute a Request and Authentication, plus 5 more sections
- Runs Shell scripts from its folder; calls bash; reaches api.commonservice.io; needs API_KEY
What it does
Onchain Pay Open API is an agent skill from npc-live/clawfirm. Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single flow—no manual withdrawal needed. Enables partners to integrate crypto buying services: - payment-method-list: Get available payment methods (Card, P2P, Google Pay, Apple Pay, etc.) with limits for a fiat/crypto pair - trading-pairs: List all supported fiat currencies and cryptocurrencies - estimated-quote: Get real-time…
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `CHANGELOG.md`, `LICENSE.md` and `references/authentication.md`).
It sits in Business, Finance & HR, covering Crypto and DeFi analysis, Smart contracts and Trading and backtesting. It works with Binance. The licence is MIT.
When your agent uses it
- Tasks that involve Crypto and DeFi analysis
- Tasks that involve Smart contracts
- Tasks that involve Trading and backtesting
Example prompts
- “/onchain-pay-open-api”
Requirements
- A Bash shell
- A credential in API_KEY
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit db435ed. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.commonservice.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Onchain Pay Open API loads about 4.9k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 225 tokens; SKILL.md has 1,958 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from npc-live/clawfirm at commit db435ed, republished under its MIT licence (© npc-live). 1,958 words, ~4,911 tokens.
Download SKILL.mdSave it as
.claude/skills/onchain-pay-open-api/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- onchain-pay-open-api
- description
- Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single flow—no manual withdrawal needed. Enables partners to integrate crypto buying services: - payment-method-list: Get available payment methods (Card, P2P, Google Pay, Apple Pay, etc.) with limits for a fiat/crypto pair - trading-pairs: List all supported fiat currencies and cryptocurrencies - estimated-quote: Get real-time price quote including exchange rate, fees, and estimated crypto amount - pre-order: Create a buy order and get redirect URL to Binance payment flow - order: Query order status and details (processing, completed, failed, etc.) - crypto-network: Get supported blockchain networks with withdraw fees and limits - p2p/trading-pairs: List P2P-specific trading pairs
- metadata.version
- 0.1.1
- metadata.author
- onchain-pay-team
- license
- MIT
Binance Onchain-Pay Open API Skill
Call Binance Onchain-Pay Open API endpoints with automatic RSA SHA256 request signing.
Use Cases & Scenarios
This skill is designed for the following scenarios:
1. 💳 Fiat-to-Crypto Purchase & Send
When to use: User wants to buy crypto with fiat currency and send directly to an external on-chain wallet address
- Buy USDT with USD/EUR/TWD using credit card → Send to MetaMask address on BSC
- Purchase BTC with Google Pay → Transfer to hardware wallet
- Buy USDC with P2P → Send to DeFi protocol contract address
Key APIs: trading-pairs → payment-method-list → estimated-quote → pre-order
2. 🔄 Direct Crypto Transfer (Send Primary)
When to use: User has crypto in Binance account and wants to send to external address
- Send existing USDT from Binance Spot to friend's wallet address
- Transfer ETH to Uniswap contract for trading
- Move crypto from Binance to self-custodial wallet (Trust Wallet, Ledger, etc.)
Key APIs: pre-order with SEND_PRIMARY customization
3. 🔗 Cross-Chain Bridge Operations
When to use: User needs to buy crypto on one chain and transfer to another network
- Buy USDC on Ethereum → Bridge to Polygon for lower fees
- Purchase tokens on BSC → Transfer to Base network
- Fiat to crypto on Solana → Send to Arbitrum for DeFi
Key APIs: crypto-network → pre-order with network selection
4. 🏪 Merchant Payment Integration
When to use: Integrate crypto payment gateway for e-commerce or services
- Accept fiat payments and auto-convert to crypto
- Enable "Pay with Crypto" checkout flow
- Process subscription payments with crypto
Key APIs: pre-order with externalOrderId tracking
5. 🤖 Smart Contract Interaction (Onchain-Pay Easy)
When to use: Buy crypto and execute smart contract in one transaction
- Buy USDT and deposit to lending protocol
- Purchase tokens and stake in DeFi pool
- Fiat on-ramp directly to GameFi or NFT marketplace
Key APIs: pre-order with ON_CHAIN_PROXY_MODE customization
6. 📊 Query & Monitoring
When to use: Check order status, available networks, or payment methods
- Monitor order processing status (pending, completed, failed)
- List supported fiat currencies and cryptocurrencies
- Check available payment methods for specific country/amount
- Verify network fees and limits
Key APIs: order, crypto-network, trading-pairs, payment-method-list
Quick Reference
| Endpoint | API Path | Required Params | Optional Params |
|---|---|---|---|
| Payment Method List (v1) | papi/v1/ramp/connect/buy/payment-method-list | fiatCurrency, cryptoCurrency, totalAmount, amountType | network, contractAddress |
| Payment Method List (v2) | papi/v2/ramp/connect/buy/payment-method-list | (none) | lang |
| Trading Pairs | papi/v1/ramp/connect/buy/trading-pairs | (none) | (none) |
| Estimated Quote | papi/v1/ramp/connect/buy/estimated-quote | fiatCurrency, requestedAmount, payMethodCode, amountType | cryptoCurrency, contractAddress, address, network |
| Pre-order | papi/v1/ramp/connect/gray/buy/pre-order | externalOrderId, merchantCode, merchantName, ts | fiatCurrency, fiatAmount, cryptoCurrency, requestedAmount, amountType, address, network, payMethodCode, payMethodSubCode, redirectUrl, failRedirectUrl, redirectDeepLink, failRedirectDeepLink, customization, destContractAddress, destContractABI, destContractParams, affiliateCode, gtrTemplateCode, contractAddress |
| Get Order | papi/v1/ramp/connect/order | externalOrderId | (none) |
| Crypto Network | papi/v1/ramp/connect/crypto-network | (none) | (none) |
| P2P Trading Pairs | papi/v1/ramp/connect/buy/p2p/trading-pairs | (none) | fiatCurrency |
How to Execute a Request
Step 1: Gather credentials
Use the default account (prod) unless the user specifies otherwise. You need:
- BASE_URL: API base URL
- CLIENT_ID: Client identifier
- API_KEY: The sign access token
- PEM_PATH: Absolute path to the RSA private key PEM file
Use the account marked (default) in .local.md.
Step 2: Build the JSON body
Build a compact JSON body from user-specified parameters. Remove any parameters the user did not provide.
IMPORTANT: Address and Network Validation
address(destination wallet address) andnetwork(blockchain network) are REQUIRED for all pre-order requests- If the user has configured
Default AddressandDefault Networkin.local.md, use them automatically - If not configured or not provided by user, ASK the user to provide both values before proceeding
Step 3: Sign and call using the bundled script
bash <skill_path>/scripts/sign_and_call.sh \
"<BASE_URL>" \
"<API_PATH>" \
"<CLIENT_ID>" \
"<API_KEY>" \
"<PEM_PATH>" \
'<JSON_BODY>'Step 4: Return results
Display the JSON response to the user in a readable format.
Authentication
See references/authentication.md for full signing details.
Summary:
- Payload =
JSON_BODY+TIMESTAMP(milliseconds) - Sign payload with RSA SHA256 using PEM private key
- Base64 encode the signature (single line)
- Send as POST with headers:
X-Tesla-ClientId,X-Tesla-SignAccessToken,X-Tesla-Signature,X-Tesla-Timestamp,Content-Type: application/json
Parameters Reference
Payment Method List v1 (buy/payment-method-list)
| Parameter | Type | Required | Description |
|---|---|---|---|
| fiatCurrency | string | Yes | Fiat currency code (e.g., USD, EUR, BRL, UGX) |
| cryptoCurrency | string | Yes | Crypto currency code (e.g., BTC, USDT, USDC, SEI) |
| totalAmount | number | Yes | Amount value |
| amountType | number | Yes | 1 = fiat amount, 2 = crypto amount |
| network | string | No | Blockchain network (e.g., BSC, ETH, SOL, BASE, SEI) |
| contractAddress | string | No | Token contract address (required for non-native tokens) |
Payment Method List v2 (v2/buy/payment-method-list)
Get all available payment methods without specifying fiat/crypto parameters. Simplified version of v1.
| Parameter | Type | Required | Description |
|---|---|---|---|
| lang | string | No | Language code for localized payment method names (e.g., en, cn, es) |
Differences from v1:
- Simpler: No need to specify fiatCurrency, cryptoCurrency, or amount
- Comprehensive: Returns all available payment methods for the merchant
- Use case: Useful for displaying all options before user input
Response Format: Same as v1, returns list of payment methods with their limits and properties.
Estimated Quote (buy/estimated-quote)
| Parameter | Type | Required | Description |
|---|---|---|---|
| fiatCurrency | string | Yes | Fiat currency code |
| cryptoCurrency | string | No | Crypto currency code (optional if contractAddress provided) |
| requestedAmount | number | Yes | Amount value |
| payMethodCode | string | Yes | Payment method (e.g., BUY_CARD, BUY_GOOGLE_PAY, BUY_P2P, BUY_WALLET) |
| amountType | number | Yes | 1 = fiat amount, 2 = crypto amount |
| network | string | Yes* | Blockchain network (can use default from .local.md) |
| contractAddress | string | No | Token contract address |
| address | string | Yes* | Destination wallet address for receiving crypto |
* Recommended: These parameters should be provided. If not specified by user, check .local.md for defaults. If no defaults exist, ask user before proceeding.
Pre-order (buy/pre-order)
Create a buy pre-order and return the redirect link for payment.
| Parameter | Type | Required | Description |
|---|---|---|---|
| externalOrderId | string | Yes | Partner's unique order ID (must be unique) |
| merchantCode | string | Yes | Merchant code (e.g., connect-gray) |
| merchantName | string | Yes | Merchant display name (e.g., GrayTest) |
| ts | number | Yes | Current timestamp in milliseconds |
| fiatCurrency | string | No* | Fiat currency code (e.g., TWD, USD, EUR) |
| fiatAmount | number | No* | Fiat amount to spend |
| cryptoCurrency | string | No* | Crypto currency to buy (e.g., USDT, BTC, ETH) |
| requestedAmount | number | No* | Amount value (fiat or crypto based on amountType) |
| amountType | number | No* | 1 = fiat amount, 2 = crypto amount |
| address | string | No | Destination wallet address for receiving crypto |
| network | string | No | Blockchain network (e.g., BSC, ETH, SOL) |
| payMethodCode | string | No | Payment method code (e.g., BUY_CARD, BUY_P2P, BUY_GOOGLE_PAY, BUY_APPLE_PAY, BUY_PAYPAL, BUY_WALLET, BUY_REVOLUT) |
| payMethodSubCode | string | No | Payment method sub-code (e.g., card, GOOGLE_PAY, WECHAT) |
| redirectUrl | string | No | Success redirect URL |
| failRedirectUrl | string | No | Failure redirect URL |
| redirectDeepLink | string | No | Deep link for success (mobile apps) |
| failRedirectDeepLink | string | No | Deep link for failure (mobile apps) |
| customization | object | No | Custom configuration object (see Customization section below) |
| destContractAddress | string | No | Destination contract address (for Onchain-Pay Easy mode) |
| destContractABI | string | No | Contract ABI name (for Onchain-Pay Easy mode) |
| destContractParams | object | No | Contract parameters (for Onchain-Pay Easy mode) |
| affiliateCode | string | No | Affiliate code for commission tracking |
| gtrTemplateCode | string | No | GTR template code (e.g., OTHERS) |
| contractAddress | string | No | Token contract address (for non-native tokens) |
* Either fiatAmount or (requestedAmount + amountType) should be provided. If fiatCurrency is not provided, the system will auto-select available fiat currencies.
Response Example:
{
"code": "000000",
"message": "success",
"data": {
"link": "https://app.binance.com/uni-qr/ccnt?...",
"linkExpireTime": 1772852565045
},
"success": true
}Get Order (order)
| Parameter | Type | Required | Description |
|---|---|---|---|
| externalOrderId | string | Yes | The external order ID to query |
Customization Options
The customization field in pre-order API accepts various flags to customize the buy flow behavior. Each merchant must have the corresponding permission configured in db.merchant_info table.
Show full SKILL.md (809 more words)Show less
Available Customization Flags
| Flag | Code | Type | Availability | Description | Use Case |
|---|---|---|---|---|---|
LOCK_ORDER_ATTRIBUTES | 1 | array | Open API ✓ | Lock specific order attributes so users cannot modify them. Values: 1=fiat currency, 2=crypto currency, 3=amount, 4=payment method, 5=network, 6=address, 7=fiat amount, 8=crypto amount | Fixed-parameter orders |
SKIP_CASHIER | 2 | boolean | Open API ✓ | Skip the cashier page and proceed directly to payment. Reduces user friction in the checkout flow. | Streamlined payment experience |
AUTO_REDIRECTION | 3 | boolean | Open API ✓ | Automatically redirect to redirectUrl after order completion without showing success page. | Seamless user experience |
HIDE_SEND | 6 | boolean | Open API ✓ | Hide the "Send" tab in the UI. Useful when only buy flow is needed. | Buy-only integration |
SEND_PRIMARY | 7 | boolean | Open API ✓ | Enable Send Crypto feature. If user's Binance balance is insufficient, auto-trigger buy flow first. | Send crypto to external address |
MERCHANT_DISPLAY_NAME | 8 | string | Open API ✓ | Override the display name shown to users in the UI. | Custom branding |
NET_RECEIVE | 9 | boolean | Open API ✓ | User receives net amount after deducting all fees. Total cost is more transparent. | Better UX for showing final received amount |
P2P_EXPRESS | 10 | boolean | Open API ✓ | Enable P2P Express mode for faster P2P order matching. | Quick P2P transactions |
OPEN_NETWORK | 11 | boolean | Web3 only | Allow users to select different networks. Default is locked to pre-selected network. Note: Currently only available for Web3 entrance, not available for Open API. | Multi-network support (Web3 only) |
ON_CHAIN_PROXY_MODE | 12 | boolean | Open API ✓ | Enable Onchain-Pay Easy mode. After buying crypto, Onchain-Pay will execute smart contract interaction instead of direct withdrawal to user wallet. Requires destContractAddress, destContractABI, and destContractParams. | Fiat to Smart Contract integration |
SEND_PRIMARY_FLEXIBLE | 13 | boolean | Open API ✓ | Flexible Send Primary mode with more options. | Advanced send crypto scenarios |
Customization Examples
Example 1: Basic Card Payment
{
"customization": {}
}Example 2: Onchain-Pay Easy (On-Chain Proxy)
{
"customization": {
"ON_CHAIN_PROXY_MODE": true,
"NET_RECEIVE": true,
"SEND_PRIMARY": true
},
"destContractAddress": "0x128...974",
"destContractABI": "depositFor",
"destContractParams": {
"accountType": 2
}
}Example 3: Send Crypto
{
"customization": {
"SEND_PRIMARY_FLEXIBLE": true,
"SEND_PRIMARY": true
}
}Example 4: P2P with Auto Redirection
{
"customization": {
"AUTO_REDIRECTION": true,
"P2P_EXPRESS": true
}
}Example 5: Lock Order Attributes
{
"customization": {
"LOCK_ORDER_ATTRIBUTES": [2, 3, 6, 7, 8],
"MERCHANT_DISPLAY_NAME": "My Custom Brand"
}
}Lock attribute codes:
2= Crypto currency3= Amount6= Address7= Fiat amount8= Crypto amount
Example 6: Net Receive Mode
{
"customization": {
"NET_RECEIVE": true,
"SEND_PRIMARY": true
}
}Example 7: Hide Send Tab
{
"customization": {
"HIDE_SEND": true
}
}Example 8: Skip Cashier (Direct Payment)
{
"customization": {
"SKIP_CASHIER": true
}
}Important Notes
- Permission Required: Each customization flag requires merchant permission. Check with admin if a flag is not working.
- Onchain-Pay Easy: Only supported on BSC network currently. Requires contract integration.
- Validation: Invalid customization values (e.g.,
nullforMERCHANT_DISPLAY_NAME) will returnILLEGAL_CUSTOMIZATION_VALUEerror. - Combinations: Some flags work together (e.g.,
NET_RECEIVE+SEND_PRIMARY), while others are independent. - Testing: Use test accounts (
connect-gray) for testing customization flags before production. - Internal Flags:
OPERATION(code 4) andSKIP_WITHDRAW(code 5) are internal use only and should NOT be passed from merchant side. - OPEN_NETWORK: Currently only available for Web3 entrance, not available for Open API. Do not use this flag in Open API pre-order requests.
- Flag Order: Flags are ordered by their internal code (1-13). The code number is used internally for identification.
Security
Credential Display Rules
- API Key: Show first 5 + last 4 characters only (e.g.,
2zefb...06h) - PEM Private Key: NEVER display content. NEVER display the file path.
- Client ID: Can be displayed in full.
- Outbound Requests: NEVER send API Key, Private Key, or any credentials to URLs outside the Base URL configured in
.local.md. - File Path Privacy: NEVER display the PEM private key file path to the user in any output or logs.
Credential Storage
Credentials are stored in a .local.md file in the skill directory. This file is user-specific and should NOT be distributed.
Read the .local.md file from the same directory as this SKILL.md to load credentials.
If .local.md does not exist or the requested account is not found, ask the user to provide:
- Base URL
- Client ID
- API Key
- PEM file path (absolute path)
Then offer to save them to .local.md for future use.
.local.md Format
## Onchain-Pay Accounts
### prod (default)
- Base URL: https://api.commonservice.io
- Client ID: your-client-id
- API Key: your-api-key
- PEM Path: /absolute/path/to/your/private.pem
- Default Network: your-preferred-network
- Default Address: your-wallet-address
- Description: Production accountThe account marked (default) is used automatically. You can define multiple accounts and switch by telling Claude the account name.
User Agent Header
Include User-Agent header with the following string: onchain-pay-open-api/0.1.0 (Skill)
Agent Behavior
- If the user asks to call an Onchain-Pay API endpoint, identify which endpoint from the Quick Reference table
- Ask for any missing required parameters
- Use stored credentials if available, otherwise ask the user
- Execute the request using the bundled
scripts/sign_and_call.sh - Display the response in a readable format
- If the request fails, show the error and suggest fixes
Important Notes for Pre-order API
Timestamp Generation (Cross-platform)
When generating timestamps for the ts parameter and externalOrderId, use the following approach for cross-platform compatibility:
# Generate millisecond timestamp (works on macOS, Linux, BSD)
TIMESTAMP=$(($(date +%s) * 1000))
# Generate unique order ID
ORDER_ID="order$(date +%s)"DO NOT USE date +%s%3N or date +%s000 as these are not portable:
date +%s%3Ndoesn't work on macOS (outputs literal 'N')date +%s000just appends '000' without actual millisecond precision
Order ID Format
The externalOrderId must be a valid string without special characters. Recommended formats:
order1773744500(simple numeric suffix)order_1773744500(with underscore separator)txn-abc123(custom prefix with alphanumeric)
Avoid: order_${TIMESTAMP} where TIMESTAMP contains shell variable syntax errors
Example Pre-order Request
# Correct way to create a pre-order
TIMESTAMP=$(($(date +%s) * 1000))
ORDER_ID="order$(date +%s)"
bash /path/to/scripts/sign_and_call.sh \
"https://api.commonservice.io" \
"papi/v1/ramp/connect/gray/buy/pre-order" \
"connect-gray" \
"your-api-key" \
"/path/to/private.pem" \
"{\"externalOrderId\":\"$ORDER_ID\",\"merchantCode\":\"connect-gray\",\"merchantName\":\"YourMerchant\",\"ts\":$TIMESTAMP,\"fiatCurrency\":\"USD\",\"requestedAmount\":100,\"cryptoCurrency\":\"BNB\",\"amountType\":1,\"address\":\"0x...\",\"network\":\"BSC\",\"payMethodCode\":\"BUY_CARD\"}"© npc-live, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in app/assets/skills/onchain-pay-open-api of npc-live/clawfirm.
- SKILL.md
- CHANGELOG.md
- LICENSE.md
- references/authentication.md
- scripts/sign_and_call.sh
Open the folder on GitHubat commit db435ed
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in npc-live/clawfirm, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Onchain Pay Open API next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Onchain Pay Open API this skillnpc-live/clawfirm | 156 | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Trading Signalbinance/binance-skills-hub | 1.1k | — | ~682 | Automated safety check: Pass | None | |
| Binance Leaderboardbinance/binance-skills-hub | 1.1k | — | ~2.5k | Automated safety check: Pass | None | |
| Binance Onchain Copy Traderbinance/binance-skills-hub | 1.1k | — | ~13k | Automated safety check: Pass | None | |
| Binance Trading SignalTermiX-official/cryptoclaw | 100 | — | ~817 | Automated safety check: Pass | MIT | |
| P2pbinance/binance-skills-hub | 1.1k | — | ~9.9k | Automated safety check: Notes | MIT |
Similar skills
Binance Leaderboard
binance/binance-skills-hub
On-chain wallet leaderboard and Gem Hunter analysis on Binance Web3.
Binance Onchain Copy Trader
binance/binance-skills-hub
Scaffold for assembling on-chain copy-trading strategies on Binance Agentic Wallet.
Binance Trading Signal
TermiX-official/cryptoclaw
Binance Web3 official skill — Smart Money on-chain trading signals tracking professional investor buy/sell activity on BSC and Solana.
P2p
binance/binance-skills-hub
Binance P2P trading assistant for natural-language queries about P2P/C2C market ads, the user's own P2P order history, order detail & appeal tracking, and advertisement publish & management.
Academy Skill
binance/binance-skills-hub
Retrieve Binance Academy's official educational content (Glossary, Courses, Learn & Earn, Articles) for AI chat.
More from npc-live/clawfirm
All 49 skills in this repoSolana Skill
npc-live/clawfirm
Interact with Solana blockchain via Helius APIs. An agent skill from npc-live/clawfirm.
Solana Sniper Bot
npc-live/clawfirm
Autonomous Solana token sniper and trading bot. An agent skill from npc-live/clawfirm.
Fiat
npc-live/clawfirm
Query Binance fiat payment capabilities — supported countries, currencies, payment methods, limits, and crypto prices — via public APIs, plus authenticated order/payment history lookup.
Solana Easy Swap
npc-live/clawfirm
Swap any Solana token from chat. An agent skill from npc-live/clawfirm.
Solana Payments Wallets Trading
npc-live/clawfirm
Pay people in SOL or USDC, buy and sell tokens, check prices, discover trending and new tokens, create and manage Solana wallets, stake SOL, earn yield through lending and managed vaults, borrow…
Agent Browser
npc-live/clawfirm
Browser automation skill using the agent-browser CLI for EXTERNAL WEBSITES via Chrome/CDP.
Related
Works with
Categories
Questions about Onchain Pay Open API
What does Onchain Pay Open API do?
Binance Onchain Pay enables users to buy cryptocurrency with fiat (e.g., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single…. Onchain Pay Open API is an agent skill from npc-live/clawfirm., EUR, USD) or send existing crypto from their Binance account directly to any external on-chain wallet address in a single flow—no manual withdrawal needed.
When should I use Onchain Pay Open API?
Onchain Pay Open API fits situations like: tasks that involve Crypto and DeFi analysis; tasks that involve Smart contracts; tasks that involve Trading and backtesting.
How do I install Onchain Pay Open API in Claude Code?
Run `npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a claude-code`. Or copy the skill folder (app/assets/skills/onchain-pay-open-api in npc-live/clawfirm) into .claude/skills/onchain-pay-open-api in your project. Claude Code loads it when a task matches its description.
How do I install Onchain Pay Open API in Codex?
Run `npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a codex`. Or copy the skill folder (app/assets/skills/onchain-pay-open-api in npc-live/clawfirm) into .agents/skills/onchain-pay-open-api in your project. Codex loads it when a task matches its description.
Can I use Onchain Pay Open API in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add npc-live/clawfirm --skill onchain-pay-open-api -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/onchain-pay-open-api, .gemini/skills/onchain-pay-open-api, .github/skills/onchain-pay-open-api and .opencode/skills/onchain-pay-open-api in your project.
What does Onchain Pay Open API need to run?
Going by SKILL.md and its folder, Onchain Pay Open API needs a shell for the scripts in its folder, the command-line tools its instructions call (bash) and credentials named API_KEY. Our summary lists: A Bash shell; A credential in API_KEY.
Does Onchain Pay Open API access the network?
SKILL.md names 1 domain. In commands or code: api.commonservice.io; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Onchain Pay Open API safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Onchain Pay Open API use?
Onchain Pay Open API is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Onchain Pay Open API use?
About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 702 tokens, read only when the agent opens those files.
What are the alternatives to Onchain Pay Open API?
Skills that share tags, products or a category with Onchain Pay Open API: Trading Signal (binance/binance-skills-hub, 1.1k stars), Binance Leaderboard (binance/binance-skills-hub, 1.1k stars), Binance Onchain Copy Trader (binance/binance-skills-hub, 1.1k stars) and Binance Trading Signal (TermiX-official/cryptoclaw, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Onchain Pay Open API?
npc-live (a GitHub organization) maintains it in npc-live/clawfirm, which has 156 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on June 17, 2026.
Source: npc-live/clawfirm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.