Read-only data and trading are different integrations
Aster’s V3 API exposes public market data as well as authenticated account and trading operations. Reading prices does not require granting a third-party interface permission to trade. AsterAtlas uses public market data only and never asks for a private key, seed phrase or agent approval.
Aster Code lets builders create trading interfaces and receive builder fees on qualifying executions. Its user flow includes agent approval and approval of a maximum builder-fee rate. Treat those as explicit permissions with economic consequences.
What to check before approving an interface
- Identify the operator and verify that you are on its intended domain.
- Read the agent permission, its scope and any expiration or revocation controls.
- Find the maximum builder-fee rate and distinguish it from Aster’s venue fees.
- Calculate the additional fee on your expected traded notional.
- Confirm how you can revoke permissions, and keep a record of what you approved.
For example, an illustrative builder rate of 0.01% on a 20,000-unit fill adds 2 units. A round trip contains separate executions; the total depends on both fills. This is fee arithmetic, not a statement that any specific interface charges that rate.
What developers should use as the source of truth
The official repository recommends V3 for new integrations. Endpoint versions, authentication requirements and account prerequisites can change. Use the current repository and changelog rather than copying an old tutorial’s signing code.
For market-data applications, validate API responses at the boundary, cache shared data, respect rate limits and display timestamps. Handle missing and stale fields explicitly. A price table that silently substitutes zero for a failed request can be more misleading than an error state.
How AsterAtlas handles market data
Our server requests public tickers, mark/funding information, funding configuration and active instrument metadata. It combines only usable active perpetual-market records. Quote volumes remain in their reported quote assets; we do not add USDT, USD1 and other quote units into a claimed universal-dollar total.
The methodology page explains cache freshness and fallback behavior. Data is informational and can lag the trading interface. There is no order routing or builder fee in AsterAtlas’s tools.
Common questions
Does using the market explorer authorize trading?
No. It reads public data without a wallet connection or trading permission.
Is a builder fee the same as a referral rebate?
No. A builder fee is a fee on qualifying routed executions. A referral rebate is a separate program benefit governed by its own terms.
Sources & review
Updated · Reviewed . Monthly review cadence. Check official terms before acting.
- Aster Code — accessed 5 September 2026
- Official Aster V3 API documentation — accessed 5 September 2026
Prepared by AsterAtlas. How we source and review information.