FR: checkEligibility in account-kit results in a sponsorhip, but I can't use it

[moldy530]

checkEligibilty results in a consumed sponsorship when used with alchemy, to mitigate this, this method should return a more detailed result that includes the UO that is being sponsored so that afterwards I can sign and send that UO

Discussed in #867

^{Originally posted by HatimPatwa July 26, 2024}

Gas Sponsorship Eligibility Check API increases the maxCounts of the policy

According to my current wallet flow, when the user lands on transaction summary page where we show the amounts, gas fees etc.

Since we use smart accounts and have paymasters policies, on this page we do call the GasSponsorshipEligibily API to check for his eligibility and show on UI accordingly, and since he is on the summary page he can truthfully go back if he changes his mind about the transaction and can do so multiple times.

The issue is this API call increases the maxCountspersender cap of the policy, meaning even without actually proceeding with the transaction his eligibility gets depleted every time he visits the summary page only??

Is there a better way to check eligibility without having this side effect..