Monetize Smart Contracts — On-Chain API Economy

Smart Contracts as Paid Services

Read-only functions as paid endpoints, co-signature reseller model, and async billing — all protocol-native

• Read-only functions as paid endpoints — any smart contract can designate specific read-only functions as "paid." When a caller invokes a paid function, the fee is automatically deducted and sent to the contract owner. No payment gateway, no subscription service, no middleman — just protocol-enforced payment for value.
• Fees stored in contract state — fee configuration (price per call, currency, discount tiers) lives directly in the smart contract's state. The contract owner updates pricing through a standard transaction. Transparent, auditable, immutable until changed by the authorized key.
• Co-signature reseller model — third parties can become resellers by co-signing function calls. The reseller adds their signature to the call, and the protocol automatically splits the fee between the contract owner and the reseller. An entire distribution network, trustlessly on-chain.
• Async billing & result caching — for expensive computations, callers can request async execution. The result is cached on-chain and delivered when ready. Subsequent calls for the same parameters hit the cache — pay once, read many times. Ideal for data feeds, analytics, and reporting.
• SDK integration — the ATSHI SDK provides first-class support for paid functions. Discover available endpoints, check pricing, call with automatic payment, and handle results — all in a few lines of code. Build paid APIs as easily as you build free ones.