P2p
Operate Binance P2P orders, appeals, and merchant advertisements through agent-guided API flows with confirmation on writes.
Overview
p2p is an agent skill for the Operate phase that guides Binance P2P order lookup, appeals, and merchant ad lifecycle actions with guarded write confirmations.
Install
npx skills add https://github.com/binance/binance-skills-hub --skill p2pWhat is this skill?
- Scene 1: order detail, filtered lists, history with counterparty context, and complaint/appeal queries
- Order status branches: completed timeline, in-progress countdown, appealing auto-surface appeal state
- Scene 2 merchant flows: reference pricing, market search, publish/update ads with diff display—writes require confirmati
- Batch ad status updates (online/offline/close) and payment-method discovery for listing setup
- Supporting currency lists and merchant profile plus ad detail lookups
- 2 documented scenes (order/appeal vs merchant ad management)
- Changelog 1.1.0 dated 2026-04-20
Adoption & trust: 2.6k installs on skills.sh; 881 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You juggle Binance P2P orders, appeals, and live ads manually and need structured agent calls instead of ad-hoc API exploration.
Who is it for?
Verified P2P merchants and solo treasury operators who already trade on Binance and want agent-assisted ops dashboards.
Skip if: Builders seeking investment advice, spot/futures trading unrelated to P2P, or anyone without Binance API credentials and merchant eligibility.
When should I use this skill?
User needs Binance P2P order queries, appeal/complaint status, or merchant ad publish/update/status operations via the hub skill.
What do I get? / Deliverables
You pull filtered order and complaint state, adjust merchant ads with diff-aware updates, and apply batch status changes only after explicit confirmation on writes.
- Filtered order or complaint reports
- Ad publish/update payloads with confirmation
- Batch ad status change results
Recommended Skills
Journey fit
P2P order handling, appeals, and live ad management are ongoing production operations for merchants—not one-off scaffolding—so Operate/iterate is the canonical shelf. Iterate covers tuning ads, resolving disputes, and rerunning filtered order queries as market conditions change.
How it compares
Binance P2P API playbook skill, not a generic crypto wallet MCP or tax reporting template.
Common Questions / FAQ
Who is p2p for?
Binance P2P merchants and operators who need order, appeal, and advertisement management through an agent with clear read vs write boundaries.
When should I use p2p?
Use it in Operate when reconciling orders, responding to appeals, or rotating ad pricing and status; merchant Scene 2 flows require P2P merchant permissions.
Is p2p safe to install?
Read the Security Audits panel on this Prism page and treat API keys as secrets; write operations can change live ads and order-related state on Binance.
SKILL.md
READMESKILL.md - P2p
# Changelog ## 1.1.0 - 2026-04-20 ### Scene 1: Order Query & Appeal Handling - Added: Order detail query by order number (`getUserOrderDetail`) - Added: Order list with rich filters — status, trade type, asset, date range (`listOrders`) - Added: Enhanced order history with counterpart nickname and advertisement role (`listUserOrderHistory`) - Added: Complaint/appeal status query with pagination and filters (`query-complaints`) - Added: Order status branch handling (completed → timeline, in-progress → countdown, appealing → auto-show appeal) ### Scene 2: Ad Publish & Management (Merchant Only) - Added: Market reference price query for pricing decisions (`getReferencePrice`) - Added: Market ad search with advertiser info (`search`) - Added: Get available ad categories for current user (`getAvailableAdsCategory`) - Added: Get user's configured payment methods (`getPayMethodByUserId`) - Added: List all system trade methods (`listAllTradeMethods`) - Added: Publish new advertisements with confirmation flow (`post`) **[write operation]** - Added: Update existing ad parameters with diff display (`update`) **[write operation]** - Added: Batch update ad status — online/offline/close (`updateStatus`) **[write operation]** ### Merchant & Support - Added: Merchant profile and ad listings query (`getAdDetails`) - Added: List supported digital currencies (`digitalCurrency/list`) - Added: List supported fiat currencies (`fiatCurrency/list`) ## 1.0.1 - 2026-03-25 - Changed: Update order placement link format from filtered list page to ad-specific detail page using `adNo` parameter (`https://c2c.binance.com/en/adv?code={adNo}`) ## 1.0.0 - 2026-03-24 - Initial release MIT License Copyright (c) 2026 Binance Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Agent SAPI API Reference Complete API reference for all C2C Agent SAPI endpoints used by the P2P Skill (Phase 3). All endpoints require authentication (API Key + HMAC SHA256 signature). See `authentication.md` for signing details. **Base URL:** `https://api.binance.com` **Common Headers:** ``` X-MBX-APIKEY: {your_api_key} User-Agent: binance-wallet/1.0.0 (Skill) ``` **Common Response Wrapper:** ```json { "code": "000000", "message": null, "data": { ... }, "success": true } ``` **Paginated Response Wrapper:** ```json { "code": "000000", "data": [ ... ], "total": 100, "success": true } ``` --- ## 1. Order Match APIs ### 1.1 Get Order Detail Get detailed information for a specific order. ``` POST /sapi/v1/c2c/agent/orderMatch/getUserOrderDetail ``` **Request Body (JSON):** | Field | Type | Required | Description | |-------|------|----------|-------------| | orderNumber | String | Yes | Order number to query | **Response (AgentOrderDetailResp):** | Field | Type | Description | |-------|------|-------------| | orderNumber | String | Order number | | advOrderNumber | String | Advertisement order number | | tradeType | String | BUY / SELL | | orderStatus | Integer | 1=Unpaid, 2=Paid, 3=Appealing, 4=Com