qfex.com valid
QFEX API Documentation
For agents: QFEX API documentation: OpenAPI and AsyncAPI specs for trading, market data and funding, plus market maker, bank transfer and stablecoin guides.
trading apiwebsocketopenapimarket datastablecoinsfunding
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T19:53:15.112Z. Cached copy · Source on qfex.com
# QFEX API Documentation
- [About QFEX](https://docs.qfex.com/qfex/about.md): How Markets Should Be
- [Market Makers](https://docs.qfex.com/qfex/market-makers.md): Institutional connectivity enquiries
- [FAQ](https://docs.qfex.com/qfex/faq.md): Frequently Asked Questions
- [Bank Transfer](https://docs.qfex.com/qfex/bank-transfer.md): Pay via Bank Transfer
- [Stablecoins](https://docs.qfex.com/qfex/stablecoins.md): Pay via Stablecoins
- [Builder Codes](https://docs.qfex.com/qfex/builder-code.md): Create a builder code, integrate QFEX trading, and earn builder rewards
- [Referral and Affiliate Program](https://docs.qfex.com/qfex/referral.md): Two commission programs: open referrals and approved affiliates
- [Managed Account Strategy](https://docs.qfex.com/qfex/managed-account.md): Invite-only systematic market-neutral trading for eligible high-volume QFEX traders.
- [Agentic Trading](https://docs.qfex.com/qfex/agentic-trading.md): Use AI agents to research markets, manage positions, and trade on QFEX.
- [Definitions and Formulae](https://docs.qfex.com/qfex/definitions.md): Common Terms Used in the Rulebook
- [Exchange](https://docs.qfex.com/qfex/architecture.md): Technical Description of the Exchange
- [Order Entry](https://docs.qfex.com/qfex/order-types.md): Supported Order Types and Times in Force
- [Contract Specifications](https://docs.qfex.com/qfex/contract-specifications.md): Perpetual Futures Adapted for Traditional Assets
- [Pre-IPO Stock Perpetuals](https://docs.qfex.com/qfex/pre-ipo-stocks.md): How QFEX prices, funds, and adjusts perpetuals referencing companies before an IPO.
- [Specification Index](https://docs.qfex.com/qfex/specification-index.md): A consolidated view of active QFEX production contract, execution, session, and risk parameters.
- [Roll Schedules](https://docs.qfex.com/qfex/roll-schedules.md): Published dated-futures contracts and roll boundaries used by QFEX oracle pricing.
- [Funding](https://docs.qfex.com/qfex/funding.md): When funding is active, why it can be zero, and how rates are computed.
- [Risk Limits](https://docs.qfex.com/qfex/risk-limits.md): Stay Safe
- [Margin and Liquidations](https://docs.qfex.com/qfex/liquidation-margin-call.md): A Detailed Description of the Liquidation Cascade
- [Corporate Actions](https://docs.qfex.com/qfex/corporate-actions.md): QFEX Policy on Equity Corporate Actions
- [Fees](https://docs.qfex.com/qfex/fees.md)
- [Subaccounts](https://docs.qfex.com/qfex/subaccounts.md): Separate your margin and risk
- [Blocked Countries and Restrictions](https://docs.qfex.com/qfex/prohibited-jurisdictions.md)
- [Introduction](https://docs.qfex.com/api-reference/introduction.md)
- [API Keys](https://docs.qfex.com/api-reference/api-keys.md): Create and securely use account-scoped API keys with granular permissions.
- [Wallet authentication](https://docs.qfex.com/api-reference/wallet-authentication.md): Sign up or sign in to QFEX programmatically with an Ethereum wallet and use the resulting session.
…
Related sites
Find similar publishers by meaning →
Other listed sites in Finance and payments. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| forter.com | Forter — Identity Intelligence for Digital Commerce | interface Ecommerce Cybersecurity +1 | US | 75 | ✓ | ✓ | |
| paypal.com | PayPal | transactional Finance and payments | — | 73 | ✓ | ||
| stripe.com | Stripe | interface Finance and payments APIs and SDKs | IE | 72 | ✓ | ||
| coinmarketcap.com | CoinMarketCap API Documentation | interface Developer tools APIs and SDKs +2 | — | 71 | ✓ | ✓ | |
| opentext.com | OpenText | documentation Cybersecurity Finance and payments +4 | CA | 70 | ✓ | ✓ | |
| razorpay.com | Razorpay | interface Finance and payments APIs and SDKs | — | 69 | ✓ | ✓ | |
| clerk.com | Clerk | interface Finance and payments Authentication and identity +1 | US | 68 | ✓ | ✓ | |
| solana.com | Solana Documentation | documentation Finance and payments Documentation and reference +2 | US | 68 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=qfex.com · GET /v1/domain/qfex.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage qfex.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for qfex.com:
1. POST https://agentwebmap.com/v1/sites/qfex.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://qfex.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/qfex.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/qfex.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.