Omni Oracle · WBTC token metadata lookup
Retrieve token metadata for WBTC (0x2260fac5e5542a773aa44fbcfedf7c193bc2c599) from on-chain sources.
What it does
Retrieve token metadata for WBTC (0x2260fac5e5542a773aa44fbcfedf7c193bc2c599) from on-chain sources.
- Verify WBTC contract details
- Fetch token decimals and symbol for trading calculations
- Validate token authenticity
Ideal buyer
DeFi agents and trading systems needing verified WBTC metadata on Base.
Run this through your governed agent wallet.
- 01Bootstrap AXON once with
npx @axon402/init. - 02Use the AXON runtime MCP tools to
search_x402_servicesorinspect_x402_offerfor this service. - 03Quote, test-buy, then run the governed paid fetch through AXON.
Send this
Prompt for your agent
A natural-language instruction for your LLM agent — with this endpoint exposed as a tool — to call this resource. Not sent to the endpoint; the endpoint consumes the JSON body below.
Pasting this prompt into a raw ChatGPT or unconfigured agent will notexecute the paid endpoint flow. Run it through an agent with the AXON runtime / MCP tools exposed (see “Use with AXON” above) so the 402 challenge, quote, and governed fetch are handled for you.
“Get the metadata for WBTC token at address 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599.”
Endpoint request body
The JSON payload your agent sends to the endpoint.
Advanced HTTP details
For integrators who need the raw protocol surface. Most agents should use AXON above instead of calling these directly.
Endpoint URL
curl fallback
curl https://omni-oracle.omnioracle.workers.dev/token/metadata/0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 \ -H "Content-Type: application/json" \ -H "X-PAYMENT: [signed_payment_envelope]"
Payment & settlement details
Raw on-chain settlement parameters. AXON above handles these automatically through quote / test-buy / governed fetch.
Price & network
Trust & risk
More in Data APIs
Browse all →Other resources in this category
Category proxy — we don't track live co-purchase signals yet.