Turn any read-only smart contract function into a paid API endpoint. Fees enforced at the protocol level. Resellers earn commissions. Developers build revenue streams. Welcome to the on-chain API economy — where every function call is a transaction.
Read-only functions as paid endpoints, co-signature reseller model, and async billing — all protocol-native.
Any smart contract can designate read-only functions as "paid." The fee is automatically deducted and sent to the contract owner — no payment gateway, no middleman.
Protocol-EnforcedFee configuration (price per call, currency, discount tiers) lives directly in the contract state. Transparent, auditable, immutable until changed by the owner.
TransparentHow Paid Functions Work
Third parties co-sign function calls. The protocol automatically splits the fee between contract owner and reseller — an entire distribution network, trustlessly on-chain.
Co-SignatureExpensive computations run asynchronously. Results cached on-chain — pay once, read many times. Ideal for data feeds, analytics, and reporting.
Pay OnceFirst-class SDK support: discover endpoints, check pricing, call with automatic payment — build paid APIs as easily as free ones.
Developer-FriendlyAPIs have always required trust. Paid Functions replace trust with protocol enforcement.
Every smart contract becomes a potential revenue source. Data providers, oracle operators, analytics services — anyone with valuable on-chain logic can monetize it per-call without building payment infrastructure.
RevenueNo invoices, no payment disputes, no chargebacks. The protocol enforces payment at the moment of the function call. You get paid before the result is delivered. Every time. Guaranteed by mathematics.
SecurityBuild a global distribution network with zero trust required. Resellers co-sign calls and earn commissions automatically. No contracts, no negotiations, no payment reconciliation. Just deploy and earn.
DistributionThe SDK makes paid functions feel like regular API calls. Discover endpoints, check prices, attach payment, and handle results — all in familiar code patterns. No blockchain expertise required on the caller side.
Developer ExperienceExpensive computations are cached on-chain. The first caller pays full price; subsequent callers with identical parameters get the cached result at a fraction of the cost. Efficient, fair, and automatic.
PerformanceAll fees are stored in the contract state and publicly auditable. No hidden charges, no surprise rate hikes. Callers see the exact cost before invoking. Price changes are on-chain transactions — fully transparent.
TransparencyTraditional APIs require trust and intermediaries. ATSHI Paid Functions require neither.
| Feature | Chainlink Functions | AWS Lambda | Traditional APIs | ATSHI Paid Functions |
|---|---|---|---|---|
| Payment Enforcement | LINK token pre-fund | Credit card / billing | API keys / invoices | Protocol-enforced per-call |
| Middleman | Chainlink network | AWS | Payment processor | None — direct |
| Reseller Model | None | None native | Manual affiliates | Co-signature native |
| Result Caching | None on-chain | CloudFront (off-chain) | CDN / Redis | On-chain native |
| Revenue Transparency | Partial (on-chain) | Opaque billing | Opaque | Fully on-chain |
| Decentralization | Partially (DON) | Centralized | Centralized | Fully decentralized |
| Commission Splits | None | None | Manual setup | Automatic on-chain |
Turn your smart contracts into revenue-generating services. Set your price, deploy your function, recruit resellers, and let the protocol handle payments. The API economy just went trustless.