ritual-dapp-http

Fetch external HTTP data via the Ritual HTTP precompile with GET and POST requests.

62|56|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/ritual-foundation/ritual-dapp-skills --skill ritual-dapp-http
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ritual-dapp-http
Source: https://github.com/ritual-foundation/ritual-dapp-skills/tree/main/skills/ritual-dapp-http
Command: npx skills add https://github.com/ritual-foundation/ritual-dapp-skills --skill ritual-dapp-http

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smart contracts on Ritual Chain need to fetch external data or interact with web services; this Skill provides a safe, programmable HTTP precompile pattern to perform off-chain HTTP requests and settle results on-chain.

Core Features & Use Cases

  • GET/POST HTTP calls through the 0x0000000000000000000000000000000000000801 precompile with short-running async lifecycle.
  • Flexible request composition: TTL, headers, body, and optional secrets or encryption flows, including dKMS and JQ post-processing.
  • Example use cases: fetch price data from APIs, trigger webhooks, or verify API responses within a dApp.

Quick Start

Install and explore the ritual-dapp-http skill and begin issuing on-chain HTTP requests via the precompile.

Frequently Asked Questions about ritual-dapp-http

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make HTTP requests from a smart contract on-chain?

You can make on-chain HTTP requests by routing GET and POST calls through the Ritual HTTP precompile, which handles off-chain data fetching and settles the asynchronous response back on-chain.

How does the on-chain HTTP precompile handle asynchronous API responses?

The on-chain precompile uses a short-running asynchronous lifecycle, allowing smart contracts to issue HTTP calls and later settle the fetched API responses on-chain using ABI-encoded formats.

Can I configure custom headers and request bodies for dApp API calls?

Yes, dApp API calls support flexible request composition, allowing you to configure custom HTTP headers, request bodies, TTLs, and optional secret handling for secure external data retrieval.

What is the best way to fetch price feeds and trigger webhooks on Ritual Chain?

Fetching price feeds and triggering webhooks is handled by sending GET or POST requests via the HTTP precompile, enabling secure off-chain API interaction with on-chain settlement.

Do I need to deposit fees to fetch external data through the HTTP precompile?

Yes, fetching external data requires deposit and fee handling, with the precompile providing specific fee guidance and TTL rules to manage the lifecycle of the asynchronous HTTP request.

How are errors handled when on-chain HTTP calls fail or time out?

The precompile provides clear error handling patterns for failed or timed-out HTTP calls, utilizing helper utilities for encoding and decoding the ABI-encoded request and response formats.