Scry answer · Agent routing
All Scry questionsWhich Scry route should an orchestrator agent call before choosing wallet, mint, cohort, or lineage depth?
Before choosing wallet, mint, cohort, or lineage depth, an orchestrator agent needs a compact routing layer that summarizes what is available and where to go next. The Scry agent orchestrator brief returns 24h and 7d context, data cutoffs, coverage gaps, product-ladder route recommendations, and next evidence-depth notes.
Direct answer
Before choosing wallet, mint, cohort, or lineage depth, an orchestrator agent needs a compact routing layer that summarizes what is available and where to go next. The Scry agent orchestrator brief returns 24h and 7d context, data cutoffs, coverage gaps, product-ladder route recommendations, and next evidence-depth notes.
| Question | Which Scry route should an orchestrator agent call before choosing wallet, mint, cohort, or lineage depth? |
|---|---|
| Request object | aggregated agent feed |
| Route | https://scry.solanahub.de/x402/solana/agent-intel-brief |
| Payment | 0.03 USDC per request (x402 v2 exact-scheme USDC) |
| Access | No API keys, no account, x402 per request |
| Evidence fields | 5 |
How an agent calls this route
- Send GET https://scry.solanahub.de/x402/solana/agent-intel-brief and read the returned HTTP 402 payment requirements.
- Sign a USDC payment for 0.03 on x402 v2 exact-scheme USDC.
- Retry the request with the X-PAYMENT header to receive the paid evidence response.
- Read the coverage, confidence, and freshness metadata before using the evidence in a wider workflow.
Agent decision
Request this route only when the object matches aggregated agent feed. Read coverage, confidence, and freshness metadata before using the evidence in a broader workflow.
Route contract
GET https://scry.solanahub.de/x402/solana/agent-intel-brief GET https://scry.solanahub.de/x402/agent-intel-brief https://solanahub.de/en/scry/use-cases/agent-orchestrator-solana-wallet-intelligence-routing/#agent-route-contract
Intent phrases
Evidence fields
Machine-readable discovery
Agent question index
https://solanahub.de/scry-agent-question-index.json
Well-known agent question index
https://solanahub.de/.well-known/scry-agent-question-index.json
Buyer intent index
https://solanahub.de/scry-buyer-intent-index.json
Well-known buyer intent index
https://solanahub.de/.well-known/scry-buyer-intent-index.json
Route contract manifest
https://solanahub.de/scry-route-contracts.json
Agent answers manifest
https://solanahub.de/scry-agent-answers.json
Scry agent card
https://solanahub.de/.well-known/agent-card.json
Scry machine map
https://solanahub.de/scry-agent-discovery.json
x402 coverage snapshot
https://scry.solanahub.de/x402/coverage.json
x402 freshness SLA
https://scry.solanahub.de/x402/freshness-sla.json
x402 agent guide
https://scry.solanahub.de/x402/agent-guide.json