binance-tokenized-securities-info▌
binance/binance-skills-hub · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Each token represents multiplier shares of the underlying stock, not exactly 1 share. Most tokens have a multiplier near 1.0 (cumulative dividend adjustment), but stock-split tokens can be 5.0 or 10.0 (e.g. multiplier = 10.0 means 1 token = 10 shares).
Binance Tokenized Securities Info Skill
Overview
| API | Function | Use Case |
|---|---|---|
| Token Symbol List | List all tokenized stocks | Browse Ondo supported tickers, filter by type |
| RWA Meta | Tokenized stock metadata | Company info, concepts, attestation reports |
| Market Status | Overall market open/close | Check if Ondo market is currently trading |
| Asset Market Status | Per-asset trading status | Detect corporate actions (earnings, dividends, splits, mergers) |
| RWA Dynamic V2 | Full real-time data | On-chain price, holders, US stock fundamentals, order limits |
| Token K-Line | Candlestick charts | OHLC data for on-chain token price technical analysis |
Recommended Workflows
| Scenario | Steps |
|---|---|
| Look up a stock's fundamentals and on-chain data | API 1 (get chainId + contractAddress by ticker) → API 5 (dynamic data) |
| Check if a stock token is tradable | API 3 (overall market status) → API 4 (per-asset status with reason code) |
| Research a tokenized stock | API 1 (find token) → API 2 (company metadata + attestation reports) |
| Get K-Line chart data | API 1 (find token) → API 6 (K-Line with interval) |
Use Cases
- List Supported Stocks: Get all Ondo tokenized tickers with chain and contract info
- Company Research: Get company metadata, CEO, industry, concept tags, and attestation reports
- Market Status Check: Determine if the Ondo market is open, closed, or in pre/post-market session
- Corporate Action Detection: Check if a specific asset is paused or limited due to earnings, dividends, stock splits, mergers, or maintenance
- Real-Time Data: Get on-chain price, holder count, circulating supply, US stock P/E, dividend yield, 52-week range, and order limits
- Technical Analysis: Fetch token K-Line (candlestick) data with configurable intervals and time ranges
Key Concept: Token ≠ Share
Each token represents multiplier shares of the underlying stock, not exactly 1 share. Most tokens have a multiplier near 1.0 (cumulative dividend adjustment), but stock-split tokens can be 5.0 or 10.0 (e.g. multiplier = 10.0 means 1 token = 10 shares).
referencePrice = tokenInfo.price ÷ sharesMultiplier
See Notes §6 for common multiplier categories.
Supported Chains
| Chain | chainId |
|---|---|
| Ethereum | 1 |
| BSC | 56 |
API 1: Token Symbol List
Method: GET
URL:
https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/stock/detail/list/ai
Request Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| type | integer | No | Filter by platform: 1 = Ondo Finance (currently the only supported tokenized stock provider). Omit to return all platforms. Use type=1 to retrieve only Ondo tokens. |
Headers: Accept-Encoding: identity
Example:
curl 'https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/stock/detail/list/ai' \
-H 'Accept-Encoding: identity' \
-H 'User-Agent: binance-web3/1.1 (Skill)'
Response:
{
"code": "000000",
"data": [
{
"chainId": "1",
"contractAddress": "<CONTRACT_ADDRESS>",
"symbol": "<TOKEN_SYMBOL_ON>",
"ticker": "<UNDERLYING_TICKER>",
"type": 1,
"multiplier": "1.021663864228987186"
},
{
"chainId": "56",
"contractAddress": "<CONTRACT_ADDRESS>",
"symbol": "<TOKEN_SYMBOL_ON>",
"ticker": "<UNDERLYING_TICKER>",
"type": 1,
"multiplier": "1.010063782256545489"
}
],
"success": true
}
Response Fields (each item in data):
| Field | Type | Description |
|---|---|---|
| chainId | string | Chain ID (1 = Ethereum, 56 = BSC) |
| contractAddress | string | Token contract address |
| symbol | string | Token symbol (ticker + on suffix, e.g. <TOKEN_SYMBOL_ON>) |
| ticker | string | Underlying US stock ticker |
| type | integer | Platform type: 1 = Ondo |
| multiplier | string | Shares multiplier (see Key Concept above, Notes §6) |
API 2: RWA Meta
Method: GET
URL:
https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/meta/ai
Request Parameters:
| Parameter | Type | Required | Description |
|---|---|---|---|
| chainId | string | Yes | Chain ID (e.g. 56 for BSC, 1 for Ethereum) |
| contractAddress | string | Yes | Token contract address |
Headers: Accept-Encoding: identity
Example:
curl 'https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/meta/ai?chainId=56&contractAddress=<CONTRACT_ADDRESS>' \
-H 'Accept-Encoding: identity' \
-H 'User-Agent: binance-web3/1.1 (Skill)'
Response:
{
"code": "000000",
"data": {
"tokenId": "<TOKEN_ID>",
"name": "<TOKEN_DISPLAY_NAME>",
"symbol": "<TOKEN_SYMBOL_ON>",
"ticker": "<UNDERLYING_TICKER>",
"icon": "/images/web3-data/public/token/logos/<TOKEN_ID>.png",
"dailyAttestationReports": "/images/web3-data/public/token/ondo/pdf/daily-<DATE>.pdf",
"monthlyAttestationReports": "/images/web3-data/public/token/ondo/pdf/monthly-<MONTH>.pdf",
"companyInfo": {
"companyName": "<COMPANY_NAME_EN>",
"companyNameZh": "<公司名称>",
"homepageUrl": "",
"description": "<COMPANY_DESCRIPTION_EN>",
"descriptionZh": "<COMPANY_DESCRIPTION_CN>",
"ceo": "<CEO_NAME>",
"industry": "<INDUSTRY>",
"industryKey": "<INDUSTRY_KEY>",
"conceptsCn": ["概念标签A", "概念标签B", "概念标签C"],
"conceptsEn": ["Concept Tag A", "Concept Tag B", "Concept Tag C"]
},
"decimals": 18
},
"success": true
}
Response Fields (data):
| Field | Type | Description |
|---|---|---|
| tokenId | string | Token unique ID |
| name | string | Full token name (e.g. <TOKEN_DISPLAY_NAME>) |
| symbol | string | Token symbol (e.g. <TOKEN_SYMBOL_ON>) |
| ticker | string | Underlying stock ticker (e.g. <UNDERLYING_TICKER>) |
| icon | string | Icon image relative path. To get the full URL, prepend https://bin.bnbstatic.com (e.g. https://bin.bnbstatic.com/images/web3-data/public/token/logos/<TOKEN_ID>.png) |
| dailyAttestationReports | string | Daily attestation report relative path. Prepend https://bin.bnbstatic.com to get the full URL |
| monthlyAttestationReports | string | Monthly attestation report relative path. Prepend https://bin.bnbstatic.com to get the full URL |
| companyInfo | object | Company details (see below) |
| decimals | integer | Token decimals (typically 18) |
Company Info Fields (data.companyInfo):
| Field | Type | Description |
|---|---|---|
| companyName | string | Company name in English |
| companyNameZh | string | Company name in Chinese |
| homepageUrl | string | Company homepage URL |
| description | string | Company description (English) |
| descriptionZh | string | Company description (Chinese) |
| ceo | string | CEO name |
| industry | string | Industry classification |
| industryKey | string | Industry i18n key |
| conceptsCn | string[] | Concept/theme tags in Chinese |
| conceptsEn | string[] | Concept/theme tags in English (e.g. Concept Tag A, Concept Tag B) |
API 3: Market Status
Method: GET
URL:
https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/market/status/ai
Request Parameters: None
Headers: Accept-Encoding: identity
Example:
curl 'https://www.binance.com/bapi/defi/v1/public/wallet-direct/buw/wallet/market/token/rwa/market/status/ai' \
-H 'Accept-Encoding: identity' \
-H 'User-Agent: binance-web3/1.1 (Skill)'
Response:
{
"code": "000000",
"data": {
"openState": false,
"reasonCode": "MARKET_PAUSED",
"reasonMsg": "Paused for session transition",
"nextOpen": "2026-03-23T08:01:00Z",
"nextClose": "2026-03-23T13:29:00Z",
"nextOpenTime": 1774252860000,
"nextCloseTime": 1774272540000
},
"success": true
}
Note: The sample above is captured with
openState=false(market closed/paused), sonextOpenis earlier thannextClose.
Response Fields (data):
| Field | Type | Description |
|---|---|---|
| openState | boolean | Whether the Ondo market is currently open for trading |
| reasonCode | string|null | Reason code if market is not in normal trading state (see Reason Codes) |
| reasonMsg | string|null | Human-readable reason message |
| nextOpen | string | Next market open time from current state (ISO 8601 UTC) |
| nextClose | string | Next market close time from current state (ISO 8601 UTC) |
| nextOpenTime | number | Next market open time from current state (Unix timestamp in ms) |
| nextCloseTime | number | Next market close time from current state (Unix timestamp in ms) |
Interpretation: These fields are state-dependent. When
openState=true,nextCloseis expected to be earlier thannextOpen(market closes before the next open). WhenopenState=false,nextOpenis expected to be earlier thannextClose(market opens before the next close).
API 4: Asset Market Status
Method: GET
URL:
How to use binance-tokenized-securities-info 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 binance-tokenized-securities-info
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches binance-tokenized-securities-info 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 binance-tokenized-securities-info. Access the skill through slash commands (e.g., /binance-tokenized-securities-info) 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.6★★★★★56 reviews- ★★★★★Dhruvi Jain· Dec 24, 2024
binance-tokenized-securities-info has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Benjamin Anderson· Dec 20, 2024
Registry listing for binance-tokenized-securities-info matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Camila Mehta· Dec 8, 2024
Useful defaults in binance-tokenized-securities-info — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Hiroshi Robinson· Nov 27, 2024
I recommend binance-tokenized-securities-info for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Oshnikdeep· Nov 15, 2024
Keeps context tight: binance-tokenized-securities-info is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Diya Thomas· Nov 11, 2024
Solid pick for teams standardizing on skills: binance-tokenized-securities-info is focused, and the summary matches what you get after install.
- ★★★★★Sakura Bansal· Oct 18, 2024
Solid pick for teams standardizing on skills: binance-tokenized-securities-info is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Oct 6, 2024
We added binance-tokenized-securities-info from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ira Malhotra· Oct 2, 2024
I recommend binance-tokenized-securities-info for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Sep 25, 2024
Useful defaults in binance-tokenized-securities-info — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 56