INFERENCE ROUTING PROTOCOL
4663 — MAINNET
LATENCY
COST
CAPABILITY
—
INFERENCE
ROUTING PROTOCOL
ONE REQUEST.
THE OPTIMAL
MODEL.
—
SEND A PROMPT
CONFIGURATION REQUIREDInference setup is incomplete. See the configuration diagnostics below. No simulated responses.
TESTER RELEASE: AUTO, FAST and CHEAP share Liquid as the primary. No distinct optimization claimed. One free alternative may be tried; providers can be temporarily unavailable. Failed provider requests do not spend success allowance.
OUTPUT / SESSION HISTORY
Awaiting your first execution. Public trace: model, reason, status and ID. Extended metadata requires holder verification.
ACCESS / 4663
HOLDER EXECUTION LAYER
Basic public AI inference is free and requires no wallet. Richer external data and advanced tools require server-verified token eligibility when operational. Shared network and global limits still apply.
TOKEN: Symbol and contract not verified
PUBLIC / HOLDER CAPABILITIES
| CAPABILITY | PUBLIC | HOLDER |
|---|---|---|
| Basic AI inference | ACTIVE · free, no wallet | Same basic inference |
| Basic execution trace | ACTIVE · model, status, reason, ID | Same basic trace |
| Live market data integrationNo operational live feed. | Not included | COMING SOON |
| Data-enriched AI responsesNo verified external-data enrichment. | Not included | COMING SOON |
| Advanced model routingTester modes currently share one primary; distinct optimization is not active. | Shared tester primary | COMING SOON |
| Extended execution analyticsServer implementation tested; live holder activation pending. | Not included | COMING SOON |
| Model comparisonsTwo-model server endpoint tested; live holder activation pending. | Not included | COMING SOON |
| Higher request quotas20 successful responses/day after verified eligibility; activation pending. | 10 successful responses/day | COMING SOON |
| Small batch inferenceUp to three prompts implemented and tested; live holder activation pending. | Not included | COMING SOON |
COMING SOON is not an active entitlement. Purchasing or holding tokens does not activate unfinished integrations. Existing server implementations require verified token configuration and holder validation before live activation.
HOLDER ACCESS — CONFIGURATION PENDING.
Session expires after ten minutes. Current balance is read on every holder request. No hardcoded wallets, token approvals, onchain prompts or fabricated outputs.