ROUTE404 / ACCESS PROTOCOL
UTILITY IS
EXECUTABLE.
Wallet ownership, read-only onchain eligibility and server-enforced compute access.
01 / TOKEN UTILITY
CAPABILITIES, NOT PROMISES
HOLDER ACCESS — CONFIGURATION PENDING. Holder execution tools have server implementations and automated tests, but live activation awaits verified token configuration and eligibility. Live market data, enriched responses and distinct advanced routing optimization are COMING SOON; holding tokens does not unlock unfinished functionality.
| CAPABILITY | PUBLIC | HOLDER |
|---|---|---|
| Basic CHEAP routing + manual selection | Yes | Yes |
| AUTO / FAST routing | No | COMING SOON / shared tester primary |
| Compare two models | No | COMING SOON / activation pending |
| Batch up to three prompts | No | COMING SOON / activation pending |
| Execution trace | Model, reason, status and ID | COMING SOON / extended analytics |
| Daily success allowance | 10 per visitor | 20 per verified wallet / activation pending |
| Output limit | 256 tokens | 512 tokens |
| Docs and tokenomics | Open | Open |
All traffic also shares 5 execution units/minute per IP, 25/day per IP and a 100-unit global daily cap. Global and network provider-attempt reservations remain charged on failure. Failed provider requests restore visitor/wallet success allowance.
02 / ACCESS ARCHITECTURE
VERIFY → CHECK → EXECUTE
- Connect an injected wallet on Robinhood Chain 4663.
- Request a five-minute, single-use challenge bound to this origin, wallet and chain.
- Sign the SIWE-style message. The server verifies the signature; Redis atomically consumes the nonce.
- The server reads ERC-20 decimals and balanceOf from chain 4663 and compares integer units against the configured minimum.
- An eligible wallet receives a ten-minute HttpOnly, Secure production session. Each holder endpoint validates the session and reads the current balance again.
Signatures authenticate an account; the token balance determines eligibility. A frontend wallet connection alone grants no server access. Read-only RPC calls do not require gas. No signing approval authorizes a transfer.
03 / TOKEN METRICS
ONCHAIN DATA, WITHOUT ASSUMPTIONS
Checking token configuration…
- Token symbol
- Not verified
- Contract address
- Pending configuration
- Decimals
- Not verified
- Total supply
- Not verified
- Holder threshold
- Pending configuration
Target network: Robinhood Chain mainnet / chain ID 4663.
04 / DISTRIBUTION DISCLOSURES
NOT PUBLISHED
- Allocation
- Not published
- Vesting
- Not published
- Liquidity policy
- Not published
- Distribution schedule
- Not published
No credit ledger, token payments, staking, yield or revenue-sharing mechanism is implemented. Token access does not make AI execution onchain. Prompts and responses are not written to Robinhood Chain.