CallPut Developer Guide
Developer documentation for CallPut protocol architecture, chain-specific contracts, option token IDs, request lifecycle handling, market data sources and integration patterns.
Integration model
CallPut interactions are chain-specific and request-based. An integration should model the request lifecycle explicitly instead of assuming immediate synchronous fills.
Chain separation
Base and Robinhood Chain use different chain IDs and deployments. Never reuse an address from one network on another.
Data discipline
Market catalogs, option rows and prices are dynamic. Build integrations that refresh state, handle unavailable data and validate the network before preparing a transaction.
Frequently asked questions
What does the CallPut Developer Guide page cover?
It covers developer documentation for CallPut protocol architecture, chain-specific contracts, option token IDs, request lifecycle handling, market data sources and integration patterns.
Does a documentation example guarantee a live market or fill?
No. Market availability, expiries, strikes, liquidity, fees and contract state can change. Check the live application and selected network before acting.
Are CallPut stock and ETF options ownership of the referenced security?
No. The documented stock and ETF options are synthetic onchain instruments and do not grant shares, fund units, dividends, voting rights or physical delivery.