Token Support
Understand token support without guessing.
Artax publishes curated token profiles, but that list is not the full transfer coverage list. Standard SPL transfer review can still evaluate unfamiliar mints. When confidence is low, Artax shows a conservative result instead of guessing.
The public token list is guidance, not a hidden wall.
Builders and AI agents see supportedTokens in the public config because Artax wants a stable list of curated examples and profile hints. That field should not be read as a promise that every other standard SPL mint is automatically unsupported. The real boundary is the review result Artax returns for the mint in front of it.
Published list
Curated token profiles are a public convenience surface for builders and agents. They make examples, dashboards, and pickers easier to use.
Broader transfer rail
The transfer rail can still review standard SPL transfers outside the curated list when the route remains explainable, recoverable, and economically sound.
Fail-closed rule
If token mechanics, route confidence, risk signals, or economics are weak, Artax may show higher pricing or a clear no instead of pretending every mint qualifies for the cheapest path.
Current API truth
What supportedTokens means today
- GET /api/config/public publishes supportedTokens as curated token profiles for UI hints, examples, and predictable known-asset suggestions.
- That list is not a hidden allowlist for every standard SPL transfer Artax may review.
- Builders should treat the published list as a stable starting set, not as the only mints a user may enter.
Builder rule
Use the published list to make your product easier to use, but let Artax analyze the actual mint before you assume sponsorship, pricing, or support status.
Broader transfer review still has rules
- Standard SPL transfer review can still evaluate unfamiliar SPL mints outside the curated profile list.
- Artax still checks token mechanics, route confidence, risk signals, and economics before sponsorship or lower pricing is approved.
- Safety classification and sponsorship eligibility remain separate: a token can be explainable without becoming sponsor-eligible.
Artax still says no when confidence is low
- Unclear or unsupported token mechanics.
- Weak route confidence or missing recovery detail.
- Economics that cannot support a predictable recovery path.
- Risk signals that require a higher fee or a direct no.
Build against the real boundary
Allow manual mint entry in your product instead of blocking every mint that is missing from supportedTokens.
Use the curated profile list for autocomplete, examples, and happy-path docs, then let Artax analyze the real mint before the user signs.
Keep your own UX ready to show warnings, more conservative fees, or a denial when a thinner-confidence mint is reviewed.
Validate unfamiliar mints on devnet first, then create a separate mainnet-beta key for the same project when the live path is actually ready.
Keep this caveat attached
This page is about standard SPL transfer review.
It does not widen swap sponsorship, universal mainnet support, or production-certification claims. It explains how to read the current public token-profile surface without mistaking it for a secret allowlist or a promise that every mint clears the cheapest path.
Developers
Read API, SDK, hosted-review, and account-flow guidance alongside token support details.
Quickstart
Follow the setup flow from devnet testing into a separate mainnet-beta launch path.
Pricing
Keep token-support expectations tied to simple pricing and to more conservative fees on lower-confidence routes.
Migration guide
Keep your sandbox key alive while you add a separate mainnet-beta key to the same project.