A: Thanks for the thought-provoking tech questions!

---

For APIs where results are delayed, there are typically two approaches: polling and webhooks. We've chosen polling as the initial method because it doesn't require additional network configuration or extra functionalities on the API consumer's side.

If you're using one of our SDK clients, there's no need to set up cron jobs or other scheduled tasks—polling mode is built-in and works automatically. Most AI jobs are completed in seconds, so you can simply call the job dispatch and result-fetching functions sequentially.

Here are examples:

- Node SDK polling example:
https://github.com/sharpapi/sharpapi-node-client/blob/3aece05a15cff64f0a248ebdc03b86068940b7ad/src/SharpApiService.js#L89
- Python SDK polling example:
https://github.com/sharpapi/sharpapi-python-client/blob/e4e365fcba989b2b037a1930032bc41eb0593548/src/sharpapi/sharp_api_service.py#L49
- PHP SDK polling example:
https://github.com/sharpapi/php-core/blob/2b38f2707c16c357f088875a00d9aca67f4c633c/src/Client/SharpApiClient.php#L231

If you're planning to connect SharpAPI to other platforms, you'll need to check if those platforms support polling or scheduled modes for retrieving delayed results. Alternatively, you could suggest that these platforms add SharpAPI to their standard offerings! :-)

---

As you've noted, we’re a startup, and purchasing this deal supports our growth and development. We're continuously improving, with several new workflows expected to launch in the first half of December.

Finally, we plan to implement a webhooks system when there's sufficient demand from customers. While webhooks are straightforward to build, our SDKs have proven to be a great starting point for most users, allowing them to set up SharpAPI connectivity immediately.