Browse documentation
PRODUCTOverviewHow it worksConnect a tokenCommunity APIFunding & accountingTreasury & activityFrequently asked questionsLive data & chartsAPI model profiles
BUILD & OPERATEDeploy to VercelSetup & operationsArchitectureSecurityVerificationLegacy computeOrbio researchDesign & assets
TERMS & PRIVACYTerms of servicePrivacy & pseudonymityRisk disclosuresSupport & complaintsAustralian considerations
TRIDENT PROTOCOL / DOCUMENTATION
Local build · Updated 22 September 2026 · Project-branded, wallet-based access

TRIDENT access token

TRIDENT is already deployed. This application does not launch coins, register new access tokens or create pools for users.

The configured contract is 0xd09bacf70d7f0310c13925a0f745bba443877798 on Robinhood Chain (4663). Its name and symbol were read through the configured Alchemy RPC. The token profile shows market observations with their source and verification status.

To use models, open API keys, connect your wallet and meet the displayed holding requirement. The default threshold is 10,000 TRIDENT. Tokens remain in the wallet. API usage draws from the shared OpenRouter treasury.

FEATURED_TOKEN_ADDRESS is the operator's contract setting. It must contain the actual deployed token, not a liquidity-pool address. Changing this setting creates a different holder policy; previously issued keys do not bypass the new token requirement. Do not change it casually once users depend on an existing deployment.

The RPC must report chain ID 4663. A token with the same address on a different chain is not the same asset. Solana access requires a separately configured genuine counterpart mint; the app does not create a bridge.