The Launch Sprint is our intensive, one-on-one partnership program designed to take a new project from concept to a live, on-chain product in just 30 days. It’s not just access to our software; it's a dedicated engagement with our core engineering team to guarantee your launch is successful and built correctly from day one.

The Sprint is designed for funded startups and serious project teams who have a clearly defined MVP scope and are ready to build immediately. It's for teams who want to move fast, de-risk their technical development, and get to market in one quarter.

Upon successful completion of the Sprint, your project is live in production. To ensure your application continues to run on our high-performance infrastructure and you retain access to our priority support, your account seamlessly transitions to our monthly Launch plan. This is communicated and agreed upon before the Sprint begins.

To ensure a successful Sprint, you should have a clear specification for your first version of the product, available engineering resources ready to build, and have the funding to support your project's launch and ongoing costs.

1 Response = 1 API Call. Each API call is counted as one request. You can monitor your usage directly on the platform. If you're using AbstractionKit SDK, it is optimized to minimize the number of calls required for interactions with the node, the Bundler, and the Paymaster. This ensures efficient usage of API requests.

‍For User Operations without a Paymaster: 

On maximum, a User Operation without a Paymaster requires 4 API calls to the Bundler:
- 1 call: eth_estimateUserOperationGas
- 1 call: eth_sendUserOperation
- 2 calls: eth_getUserOperationReceipt

To accommodate scenarios where users estimate gas twice before confirming a transaction, we factor in 5 API calls in our estimates.

For User Operations with a Paymaster

On maximum, a User Operation with a Paymaster requires 10 API calls to the Bundler and Paymaster:
2 call: eth_estimateUserOperationGas
1 call: pm_clientVersion
1 call: pm_supportedEntryPoints
1 call: pm_supportedERC20Tokens
2 call: pm_sponsorUserOperation
‍1 call: eth_sendUserOperation
2 calls: eth_getUserOperationReceipt

Think of it like a bridge. API Requests are the total number of cars allowed to cross the bridge in a whole month. Rate Limit is the number of lanes on the bridge, determining how many cars can cross at the exact same time.

A development project can handle a low number of lanes, but a live application with many concurrent users needs a multi-lane bridge to prevent traffic jams. That's why the Launch plan has a much higher Rate Limits.

An app provides you with an API key that allows you to monitor and manage your usage specifically for that app. Each app supports all mainnet and testnet networks.

The Launch plan's value is not solely based on API call volume. You are investing in three critical areas for any production application:

Performance, Reliability: The Launch plan includes a higher rate limit (RPM). This is a technical necessity for any live app with real users to ensure it is fast, responsive, and can handle concurrent activity without traffic jams. The Launch Plan also comes with advanced features such as Account Recovery Service.  

‍Expert Support as an Insurance Policy: The private channel gives your team a direct line to our core engineers. This is your insurance against costly bugs and project delays. For a fraction of an engineer's salary, you get an expert team dedicated to de-risking your project and ensuring you launch on time.

If you exceed the 50,000 requests on the Starter plan, we will contact you to discuss upgrading to the Launch plan, which is designed for the higher volume and performance needs of a production application. We do not automatically cut off access for minor overages.