fiat▌
binance/binance-skills-hub · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Query Binance fiat payment capabilities, available payment methods, pricing, and supported currencies/countries using public APIs (no authentication required). For order and payment history, see Authenticated Endpoints.
Binance Fiat Skill
Query Binance fiat payment capabilities, available payment methods, pricing, and supported currencies/countries using public APIs (no authentication required). For order and payment history, see Authenticated Endpoints.
Base URL
https://www.binance.com/bapi/fiat/v1/public/fiatpayment/agent
Available APIs
1. get_capabilities
Query supported fiat currencies, cryptos, and business types for a country.
curl "https://www.binance.com/bapi/fiat/v1/public/fiatpayment/agent/get-capabilities?country={COUNTRY_CODE}"
Optional: businessType (BUY, SELL, DEPOSIT, WITHDRAW) to filter.
Response: data.supportedBusinessTypes, data.fiatCurrencies[] (with code, name, supportedBusinessTypes), data.cryptoCurrencies[]
2. get_buy_and_sell_payment_methods
curl "https://www.binance.com/bapi/fiat/v1/public/fiatpayment/agent/get-buy-and-sell-payment-methods?businessType={BUY|SELL}&fiatCurrency={FIAT}&cryptoCurrency={CRYPTO}&country={COUNTRY_CODE}"
All 4 parameters required.
Response: data.paymentMethods[] and data.p2pPaymentMethods[], each with code, paymentMethodName, fiatMinLimit, fiatMaxLimit, cryptoMinLimit, cryptoMaxLimit, quotation, suspended
3. get_deposit_and_withdraw_payment_methods
curl "https://www.binance.com/bapi/fiat/v1/public/fiatpayment/agent/get-deposit-and-withdraw-payment-methods?businessType={DEPOSIT|WITHDRAW}&fiatCurrency={FIAT}&country={COUNTRY_CODE}"
All 3 parameters required. No cryptoCurrency, no quotation, no P2P methods.
Response: data.paymentMethods[] with code, paymentMethodName, fiatMinLimit, fiatMaxLimit, suspended
4. get_price
curl "https://www.binance.com/bapi/fiat/v1/public/fiatpayment/agent/get-price?fiatCurrency={FIAT}&cryptoCurrency={CRYPTO}&country={COUNTRY_CODE}"
Optional: businessType (BUY or SELL, defaults to BUY).
Response: data.bestPrice — indicative reference price, may differ from execution price
Recommended Workflow
get_capabilitiesfirst — confirms what's supported before making other calls- Payment methods API — BUY/SELL →
get_buy_and_sell_payment_methods; DEPOSIT/WITHDRAW →get_deposit_and_withdraw_payment_methods get_price— add if the user wants exchange rate info
Skip step 1 for simple price queries (e.g., "What's BTC in USD?").
Calling APIs
Use WebFetch or Bash (curl). All responses follow:
{ "code": "000000", "message": null, "data": { ... }, "success": true }
code: "000000" = success; otherwise check message.
Action Links
After presenting API results, always include a relevant action link so the user can proceed directly on Binance. Build the URL dynamically based on the fiat currency, crypto currency, and business type from the conversation context.
URL Templates
| Business Type | URL Template | Example |
|---|---|---|
| BUY | https://www.binance.com/en/crypto/buy/{FIAT}/{CRYPTO} |
Buy BTC with USD |
| SELL | https://www.binance.com/en/crypto/sell/{FIAT}/{CRYPTO} |
Sell BTC for USD |
| DEPOSIT | https://www.binance.com/en/fiat/deposit/{FIAT} |
Deposit USD |
| WITHDRAW | https://www.binance.com/en/fiat/withdraw/{FIAT} |
Withdraw USD |
Language-aware URL
Replace the /en/ locale segment to match the user's language. Supported locales:
en, zh-CN, zh-TC, ru, es, es-LA, fr, vi, en-TR, it, pl, id, uk-UA, ar,
en-AU, pt-BR, en-IN, en-NG, ro, bg, cs, lv, sv, pt, es-MX, el, sk, sl,
es-AR, fr-AF, en-KZ, en-ZA, en-NZ, en-BH, ar-BH, ru-UA, de, kk-KZ,
ru-KZ, ja, da-DK, en-AE, en-JP, hu, lo-LA, si-LK, az-AZ, uz-UZ, pt-AO
Common mapping examples:
| User language | Locale | Example URL |
|---|---|---|
| English | en |
https://www.binance.com/en/crypto/buy/USD/BTC |
| 简体中文 | zh-CN |
https://www.binance.com/zh-CN/crypto/buy/CNY/BTC |
| Português (BR) | pt-BR |
https://www.binance.com/pt-BR/crypto/buy/BRL/BTC |
| Türkçe | en-TR |
https://www.binance.com/en-TR/crypto/buy/TRY/BTC |
For regional English variants (en-AU, en-IN, en-NG, en-AE, en-NZ, etc.), use the specific regional locale rather than plain en — this ensures the user sees region-appropriate content.
Default to en if the user's language is unclear.
Always include at least one action link when the conversation involves a specific fiat/crypto pair or business type. For general questions, include all relevant links from get_capabilities. Format as a call-to-action, e.g.: "Ready to buy? Buy BTC with USD on Binance"
Presenting Results
- Table format for payment methods (names, limits, pricing); flag suspended methods
- Note that prices are indicative/reference prices
- Respond in the user's language
- Always end with the relevant action link(s)
Price Sorting and Best Value Logic
Price direction depends on the business type — always apply the correct comparison:
| Business Type | Better price direction | Rationale |
|---|---|---|
| BUY | Lower price is better | You pay less fiat per unit of crypto — same fiat buys more crypto |
| SELL | Higher price is better | You receive more fiat per unit of crypto sold |
When summarizing: for BUY highlight the lowest quotation; for SELL highlight the highest quotation. Example (BUY USD/BTC): $70,236 beats $74,291 — more BTC per dollar.
Wallet Payment Method (BUY)
If the BUY response includes a payment method with code containing WALLET (case-insensitive), it represents buying crypto using the user's Binance fiat wallet balance.
When this occurs, proactively mention:
"One of the available payment methods is your Binance fiat wallet balance. If your wallet doesn't have sufficient funds, you'll need to deposit fiat first. Would you like me to look up the available deposit methods for you?"
If the user confirms, call get_deposit_and_withdraw_payment_methods with businessType=DEPOSIT using the same fiat currency and country, and present the results along with the Deposit action link.
Order & Payment History (Authenticated)
See references/sapi-endpoints.md for authenticated endpoints (order/payment history, deposit/withdraw records). Requires Binance API key and secret.
Country Code Reference
Use ISO 3166-1 alpha-2 codes: BR, GB, DE, FR, JP, KR, AU, etc. Never use US as the country parameter — US users are not supported by Binance fiat payment APIs.
Country Inference Rules
Determine the country parameter using this priority order:
-
Explicit context — If the country is already known from the conversation (user stated it, or inferred in a prior turn), reuse it without re-inferring.
-
Fiat currency → country mapping — Map directly from currency. Examples:
SGD→SG,BRL→BR,JPY→JP,KRW→KR,AUD→AU,GBP→GB,CAD→CA,INR→IN,TRY→TR,MXN→MX,NGN→NGEUR→FR(since the user did not specify a country, useFRas the default for EUR)USD→SG(since the user did not specify a country, useSGas the default for USD)
MANDATORY:
USMUST NEVER be used as the country parameter under any circumstances. -
Empty results — If the API returns no payment methods or an unsupported combination, ask: "No results found for your current settings. Would you like to try a different country? If so, please tell me which country." Then use the country the user provides.
How to use fiat on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add fiat
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches fiat from GitHub repository binance/binance-skills-hub and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate fiat. Access the skill through slash commands (e.g., /fiat) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★50 reviews- ★★★★★Valentina Martin· Dec 28, 2024
Registry listing for fiat matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Emma Thomas· Dec 24, 2024
I recommend fiat for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chaitanya Patil· Dec 8, 2024
fiat is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ishan Taylor· Dec 4, 2024
Keeps context tight: fiat is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Piyush G· Nov 27, 2024
Keeps context tight: fiat is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Valentina Rahman· Nov 23, 2024
fiat is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Emma Ramirez· Nov 19, 2024
fiat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Omar Torres· Nov 15, 2024
Useful defaults in fiat — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Shikha Mishra· Oct 18, 2024
Registry listing for fiat matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Valentina Harris· Oct 14, 2024
fiat fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 50