{"uid":"cap_74uJQ0ykPh02mKmAA2Vji","slug":"multi-chain-onchain-data-sourcing-and-provider-selection-procedure-e6921562","name":"Multi-Chain Onchain Data Sourcing and Provider Selection Procedure","description":"Agent-facing decision procedure for choosing which onchain data layer to pay for a given query. Covers query class routing: raw RPC for state and balances, indexed explorer APIs for receipts and status, analytics warehouses for flows, whales, and decoded events. Covers cross-chain coverage decisions, per-provider cost guardrails, rate-limit handling, confirmation-depth and finality checks before acting on onchain truth, and an evidence log schema linking each decision to the source payload.","url":"https://k2so-8080.on.ascii.dev/api/services/multi-chain-onchain-data-sourcing-and-provider-s?utm_source=zero.xyz","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET","HEAD","DELETE"],"type":"string"},"queryParams":{"type":"object","properties":{"meta":{"enum":["0","1"],"type":"string","description":"Set to 1 for free metadata JSON (no payment required)"},"topic":{"type":"string","description":"Optional topic override for the decision procedure"}}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object","title":"Multi-chain onchain data sourcing and provider selection procedure paid response","$schema":"https://json-schema.org/draft/2020-12/schema","required":["ok","paid","service","provider","result"],"properties":{"ok":{"type":"boolean"},"paid":{"type":"boolean"},"result":{"type":"object","required":["ok","service"],"properties":{"ok":{"type":"boolean","description":"Handler success"},"brief":{"type":"string","description":"Decision procedure prose for agents"},"model":{"type":"string"},"topic":{"type":"string"},"service":{"type":"string","description":"Service slug"},"procedure":{"type":"string"},"generatedAt":{"type":"string","description":"ISO-8601 timestamp"},"generationSource":{"enum":["llm","reasoning","deterministic"],"type":"string"}}},"payment":{"type":"object","properties":{"code":{"type":"string"},"payer":{"type":"string"},"detail":{"type":"string"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_PY4TY6J7_XyfgLRudna2C","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns a structured decision procedure for AI agents on how to select and route onchain data queries across chains, providers, and indexing layers.","exampleAgentPrompt":"I need to query token balances and decoded contract events across Ethereum, Base, and Arbitrum — can you give me a decision procedure for which onchain data provider to use for each query type, including how to handle rate limits and confirm finality before acting?","exampleUseCases":[{"title":"Routing raw RPC vs indexed explorer queries","prompt":"My agent needs to check both current wallet balances and historical transaction receipts across Ethereum and Optimism — walk me through which data layer to use for each query type and how to stay within cost guardrails."},{"title":"Whale flow and analytics provider selection","prompt":"I'm building an agent that tracks large token flows and decoded DeFi events on Base and Arbitrum — which analytics warehouse providers should it use and how should it route those queries compared to regular state lookups?"},{"title":"Finality-safe decision evidence logging","prompt":"Before my agent acts on any onchain data, I want it to verify confirmation depth and log which provider and payload it used as evidence — can you give me the procedure for that, including how to handle cross-chain finality differences?"}],"resultDescription":"A paid response containing prose decision-procedure guidance (the 'brief' field), covering query class routing, provider selection, cross-chain coverage, cost guardrails, rate-limit handling, confirmation-depth checks, and an evidence log schema. Also includes metadata such as generation source (llm/reasoning/deterministic), topic, service slug, and ISO-8601 timestamp.","failureModes":["Payment not provided — returns 402 with payment details rather than the procedure","Invalid or unsupported topic override — may return generic procedure without topic-specific guidance","Rate limits on the upstream service — may return error or degraded response","Malformed input schema — missing required 'type' or 'method' fields returns validation error","Service unavailability — K-2SO host unreachable, returns network or 5xx error"],"whenToPreferThis":"Choose this endpoint when an AI agent needs structured, payable decision-procedure guidance for routing onchain data queries across multiple chains and providers — especially when the agent must balance cost, rate limits, finality requirements, and cross-chain coverage in a single coherent workflow. Prefer this over raw provider documentation when you need opinionated, agent-ready routing logic with built-in evidence logging schema rather than raw API specs.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-16T06:48:12.971Z","isFirstParty":false,"canonicalSlug":"multi-chain-onchain-data-sourcing-and-provider-selection-procedure-e6921562"}