ritual-dapp-x402

Pay-per-call API access in a smart contract is enabled by routing paid HTTP requests through Ritual's HTTP precompile, encrypting credentials client-side and decrypting them inside a TEE to execute billed calls within a single on-chain transaction.

Encrypted API credentials in on-chain dApps are handled by encrypting them client-side and decrypting inside a Trusted Execution Environment (TEE), ensuring per-call billing and optional shared access via dKMS across multiple executors.

Yes, on-chain budget tracking and per-call payments are supported in consumer contracts, providing cost awareness and allowing you to set spending limits for premium API data access directly on-chain.

Credential rotation for paid on-chain API calls is supported natively, allowing you to update encrypted credentials securely while maintaining continuous access to premium APIs through the HTTP precompile without interrupting active dApp workflows.

Yes, shared credentials across multiple executors are supported via dKMS (distributed Key Management System), enabling optional shared access to encrypted API credentials while maintaining secure per-call billing and on-chain auditability.

Pay-per-call on-chain transactions are ideal when building dApps requiring automatic paid data access, granular per-call pricing, strict budget control, or shared credentials via dKMS, replacing flat-rate subscriptions with auditable, usage-based billing.