Repository: WorqHat/worqhat-docs
Pull request #29: get started, quickstart
Author: login: Swapnaja964
Created: 2025-03-26T17:43:38Z | Merged: 2025-03-26T18:26:09Z



<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
## Summary by CodeRabbit

- **Documentation**
  - Introduced a “Get Started Here” guide that provides an overview of the WorqHat Public API, including setup instructions and links to additional resources.
  - Added a “Quickstart” guide detailing API usage, authentication steps, endpoint information, and best practices for secure API interactions.
  - Added a “Rate Limits” document explaining the rate limiting mechanisms of the WorqHat AI API, including request limits and optimization tips.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->


Diff:
diff --git a/Get Started.mdx b/Get Started.mdx
new file mode 100644
index 0000000..bcd504d
--- /dev/null
+++ b/Get Started.mdx	
@@ -0,0 +1,110 @@
+---
+title: '🚀 Get Started Here'
+---
+
+---
+title: 'About WorqHat API'
+---
+
+Welcome to WorqHat's Public API documentation.
+This documentation was built to help you build your own custom integration with WorqHat's REST-based Application Programming Interface (API).
+
+The WorqHatAPI can be applied to virtually any task that you want to perform on the WorqHat Applications but from your own codebases. This involves understanding or generating natural language, code, images and voices; adding in custom form data to the records and even making changes to the No-Code Applications.
+
+Some important notes to help you get started:
+1. Access to WorqHat's API is currently Generally Available to everyone.
+2. Review our terms of service before getting started with the development.
+
+## Setting up your API Access
+<CardGroup cols={2}>
+  <Card
+    title="Read More about the AI Models"
+    href="https://docs.worqhat.com/"
+  >
+    Read more about the AI Models available for use in the API.
+  </Card>
+  <Card
+    title="Read the API Documentation"
+    href="https://docs.worqhat.com/"
+  >
+    Read the API Documentation to understand how to use the API.
+  </Card>
+</CardGroup>
+
+## Create Your Own
+
+<CardGroup cols={2}>
+  <Card
+    title="Quickstart Guide"
+    href="https://docs.worqhat.com/605330m0"
+  >
+    Learn by building a Sample Application from scratch.
+  </Card>
+  <Card
+    title="Read about our Regular Updates"
+    href="https://updates.worqhat.com/"
+  >
+    Stay updated with our latest features and updates.
+  </Card>
+  <Card
+    title="Join our Community"
+    href="https://discord.com/invite/KHh9mguKBx"
+  >
+    Join our Community of Developers and Creators and get help.
+  </Card>
+  <Card
+    title="Get Inspiration"
+    href="https://www.instagram.com/worqhat/"
+  >
+    Follow our Showcase of Projects built by the Community.
+  </Card>
+  <Card
+    title="Schedule a Call"
+    href="https://worqhat.com/demo"
+  >
+    Schedule a Call with our Founders to discuss your use-case. We can help answer questions and discuss yur project in detail.
+  </Card>
+  <Card
+    title="Follow us on Twitter"
+    href="https://x.com/worqhat"
+  >
+    Follow us on twitter to stay updated with our latest features, news and updates.
+  </Card>
+</CardGroup>
+
+**👨‍👩‍👧‍👦 Community**
+**Individually, we’re a developer.**
+
+**Together, we’re a community, a team, helping each other to learn and build with code.**
+
+  <Card
+    title="Hang out on discord"
+    href="https://discord.com/invite/KHh9mguKBx"
+  >
+    For real-time news, fun memes, data engineering topics, and more, join us on ➝
+  </Card>
+
+  <Card
+    title="Twitter"
+    href="https://x.com/worqhat"
+  >
+  </Card>
+
+  <Card
+    title="LinkedIn"
+    href="https://www.linkedin.com/company/worqhat"
+  >
+  </Card>
+
+  <Card
+    title="Instagram"
+    href="https://www.instagram.com/worqhat/"
+  >
+  </Card>
+
+  <Card
+    title="YouTube"
+    href="https://www.youtube.com/@worqhat"
+  >
+  </Card>
+
diff --git a/Quickstart1.mdx b/Quickstart1.mdx
new file mode 100644
index 0000000..989c091
--- /dev/null
+++ b/Quickstart1.mdx
@@ -0,0 +1,85 @@
+---
+title: 'Quickstart'
+---
+
+## Base Endpoint for all API calls
+Right now, the API is only available on the `https://api.worqhat.com` domain. This is the only official domain that is applicable for all API Calls to the Application.
+
+The WorqHat API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The API key you use to authenticate the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted to the Organization you are using the API keys for.
+
+The WorqHat API doesn't support bulk updates. You can work on only one object per request. The WorqHat API differs for every account as we release new versions and tailor functionality. These docs are customized to your version of the API.
+
+If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API. You can subscribe to these notifications in your WorqHat account settings.
+
+**Base URL for all API calls**
+```
+https://api.worqhat.com/
+```
+
+<Card
+  title="No code applications"
+  href="https://worqhat.com/"
+>
+  Not a Developer Use WorqHat's No-Code Workspace options to get started with WorqHat and to do more with your WorqHat apps - without a single line of Code.
+</Card>
+
+**Authentication**
+You can get your Organization's API Key and your API Key from the Workspace Admin Panel. You can find the API Tokens screen under the Workspace Settings or by visiting the Developers Portal. You can also find the API Tokens screenby visiting the following URL:
+
+```
+https://$workspace.worqhat.app/workspace/developers
+```
+
+> $workspace is the name of your Workspace. You can find the name of your Workspace in the URL of your Workspace. For example, if your Workspace URL is https://myworkspace.worqhat.app, then your Workspace name is myworkspace.
+
+In case you are not the Admin/Leader/Developer of the Workspace, you will not be able to access the API Tokens screen. In such a case, please contact your Workspace Admin/Leader/Developer to get the API Keys or request them to add you as a Developer to the Workspace.
+
+You can copy the API Keys from the API Tokens screen and use them in your API Calls. You can also generate new API Keys from the API Tokens screen. You can also delete the API Keys from the API Tokens screen. Please note that deleting the API Keys will revoke access to the API for the respective API Keys.
+
+**Creating API Keys**
+
+In order to use the WorqHat API, you must first obtain an API key and the ORG Key. We offer a genenrous free tier that gets reset every month. You can also upgrade to a paid plan to get more API calls and more features.
+
+This key serves as a unique identifier that allows you to access WorqHat's API services. To generate an API key, follow the steps below:
+
+1. Go to the WorqHat API website and click on the **Get Started** button.
+2. Join the WorqHat community by entering your email address and clicking on the Join Now button. You can also sign up using your Google or Microsoft account.
+3. Once you've signed up, you'll be redirected to the dashboard. Click on the **Create a Workspace** button on the left-hand side of the screen.
+4. Add a name for your workspace and click on the **Create Workspace** button. We use workspaces to organize your projects and keep them separate from each other. This allows you to manage your projects more efficiently.
+5. Once you've created a workspace, you'll be redirected to the Workspace Signin page. Sign in to your workspace using your email address and password that you have set up during the signup process.
+6. After signing in, you'll be redirected to the dashboard. Click on the **Try Now** button on the **Build Your Own Applications with our API** card.
+7. You'll be redirected to the API page. You can find your API key and ORG key on the right-hand side of the screen. Click on the Copy button to copy the keys to your clipboard.
+8. Also, make sure to add your Domain name to the **Allowed Domains** section. This will allow you to make API calls from your domain. For example, if you're making API calls from a website hosted on `https://example.com`, you'll need to add `example.com` to the Allowed Domains section.
+
+Here's an example of what the API key & ORG key looks like:
+```
+curl --request POST \
+--url https://api.worqhat.com/authentication \
+--header 'Authorization: Bearer <token>'
+```
+
+If you're an Existing Customer but do not have access to the API Tokens screen, please contact our Support Assistance. You can visit https://help.worqhat.com or reach out to us at mailto:support@worqhat.com, and we will set you up with an Account.
+
+In order to use WorqHat's API, you will need to authenticate every request. We rely on
+`Authorization Bearer <YOUR_API_KEY>` tokens to authenticate API requests.
+
+```
+curl
+  --location --request GET 'https://api.worqhat.com/$endpoint' \
+```
+
+Tokens are scoped to an admin's permission settings and your workspace. Only workspace admins can enable API Access for the members of the workspace. Once the access has been enabled, you can generate API tokens in your workspace.
+
+Security is of utmost importance when working with API keys. Your API keys carry many privileges, so it's crucial to keep them secure. As part of our security measures, we require you to whitelist your Apps before you can use the API keys. However, once your Apps are whitelisted, you can use these API keys anywhere, including in your client-side code. We only serve valid requests from the endpoints listed in your App's whitelist. If you don't have any endpoints listed, requests to the API will fail.
+
+<warning>
+Please note that only code that sends a request from Client-Side requires authentication. If you are using our NodeSDKs or sending request from Server Code, it will not be restricted. In such scenarios you can add your API-Key to the `.env` file.
+</warning>
+
+```
+WORQHAT_API_KEY=<YOUR_API_KEY>
+```
+
+To ensure that your requests are authenticated and authorized to access our API, you must send the `WORQHAT_API_KEY` with every request that you send. Additionally, you have the option to set a per-request key, which is often useful for Connect applications that use multiple API keys during the lifetime of a process. Methods on the returned object reuse the same API key.
+
+Finally, it's important to note that all API requests must be made over HTTPS. Calls made over plain HTTP will fail, and API requests without authentication will also fail. By following these best practices, you can help keep your API requests secure and prevent unauthorized access to your data.
\ No newline at end of file
diff --git a/rate_limit.mdx b/rate_limit.mdx
new file mode 100644
index 0000000..5856bce
--- /dev/null
+++ b/rate_limit.mdx
@@ -0,0 +1,30 @@
+---
+title: 'Rate Limits'
+---
+
+## What are Rate Limits?
+
+Rate limits are the number of requests that can be made to the WorqHat AI API in a given time period. The rate limits are set to ensure that the API is used in a safe and fair manner.
+
+In the context of our API, rate limiting is an important mechanism that helps to ensure the stability, reliability, and fair usage of our services. A rate limit is a restriction that we impose on the number of requests that a user or client can make within a specified time period. This is to prevent any single user or client from overwhelming our servers with too many requests, which could cause downtime or other disruptions in service.
+
+By implementing rate limiting, we can ensure that our resources are utilized in a fair and efficient manner, and that all users of our API have a consistent level of access to our services. Our rate limiting algorithms are designed to balance the needs of different users and clients, and to prevent any single user from monopolizing our resources. This helps to ensure that our API remains stable, responsive, and reliable, even under heavy usage or traffic spikes.
+
+To help our users understand and work with our rate limiting mechanisms, we provide detailed documentation on our API rate limits, including the number of requests allowed within a given time period, the error codes that are returned when a user exceeds their rate limit, and tips for optimizing API usage to avoid hitting the rate limit. By working with our rate-limiting mechanisms and following best practices for API usage, our users can ensure a smooth and uninterrupted experience when working with our services.
+
+## Why do we need rate limits?
+
+Rate limits are a common mechanism used by APIs to restrict the number of requests a user or application can make in a given period of time. WorqHat AI, like many other APIs, has rate limits in place for several reasons.
+
+Firstly, rate limits help to protect the API from abuse or misuse. Without rate limits, a malicious user or bot could send an excessive number of requests to the API in a short period of time, potentially causing disruptions in service or overloading the API. By setting rate limits, WorqHat AI can prevent such activities and ensure that the API remains available to all users.
+
+Secondly, rate limits help to ensure that everyone has fair access to the API. Without limits, a single user or application could make an excessive number of requests, monopolizing the API's resources and causing slowdowns or poor performance for others. By throttling the number of requests that a single user can make, WorqHat AI can ensure that all users have an opportunity to use the API without experiencing issues.
+
+Thirdly, rate limits help to manage the overall load on WorqHat AI's infrastructure. If there is a sudden increase in the number of requests to the API, it could tax the servers and cause performance issues. By setting rate limits, WorqHat AI can help maintain a smooth and consistent experience for all users, even during periods of high demand.
+
+## What are the rate limits for our API?
+The rate limits for our API are as follows:
+
+<info>
+* 2000 requests per minute
+</info>
\ No newline at end of file


Reviews:
user: login: coderabbitai[bot]
body: **Actionable comments posted: 4**

<details>
<summary>🧹 Nitpick comments (6)</summary><blockquote>

<details>
<summary>Get Started.mdx (4)</summary><blockquote>

`1-7`: **Multiple YAML Front Matter Blocks**  
There are two separate YAML front matter blocks at the top of the file. While this may be intentional, many MDX processors expect a single YAML block. Please verify that your build system supports multiple front matters; otherwise, consider merging these into one consolidated block.

---

`9-12`: **Long Introductory Sentence Clarity**  
The sentence on line 12 is quite long and may confuse readers. Consider splitting or rephrasing it for improved clarity and readability. For example:  
```diff
- The WorqHatAPI can be applied to virtually any task that you want to perform on the WorqHat Applications but from your own codebases. This involves understanding or generating natural language, code, images and voices; adding in custom form data to the records and even making changes to the No-Code Applications.
+ The WorqHat API can be used for a wide range of tasks on WorqHat Applications, from processing natural language and code to handling images and voices. It also supports adding custom form data to records and modifying No-Code Applications.
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~12-~12: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ustom form data to the records and even making changes to the No-Code Applications.  Some importa...

(MAKE_CHANGES)

</details>

</details>

---

`64-66`: **Typo in Call-to-Action Text**  
There is a typo in the call-to-action on line 65 (“yur project” should be “your project”).  
```diff
- Schedule a Call with our Founders to discuss your use-case. We can help answer questions and discuss yur project in detail.
+ Schedule a Call with our Founders to discuss your use-case. We can help answer questions and discuss your project in detail.
```

---

`68-72`: **Consistent Capitalization for Proper Nouns**  
Within the "Follow us on Twitter" card, the title is correct but the description (line 72) uses “twitter” in lowercase. Change it to “Twitter” for consistency with the proper noun.  
```diff
- Follow us on twitter to stay updated with our latest features, news and updates.
+ Follow us on Twitter to stay updated with our latest features, news and updates.
```

</blockquote></details>
<details>
<summary>Quickstart1.mdx (2)</summary><blockquote>

`8-8`: **Punctuation for Clarity in Technical Details**  
The sentence on line 8 could benefit from a comma to improve readability. For example, after "Organization":  
```diff
- ...the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted...
+ ...the request determines whether the request you are sending as a user is based on which Organization, as all our Billings are rerouted...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~8-~8: Possible missing comma found.
Context: ...are sending as a user is based on which Organization as all our Billings are rerouted to the...

(AI_HYDRA_LEO_MISSING_COMMA)

</details>

</details>

---

`83-83`: **Review Preposition Usage in API Key Reuse Statement**  
The sentence on line 83 (“Methods on the returned object reuse the same API key.”) might be clearer with a slight rewording. Consider:  
```diff
- Methods on the returned object reuse the same API key.
+ Methods of the returned object reuse the same API key.
```  
This change might enhance clarity.

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~83-~83: The preposition ‘to’ seems more likely in this position.
Context: ... per-request key, which is often useful for Connect applications that use multiple ...

(AI_HYDRA_LEO_REPLACE_FOR_TO)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 449c07b435778741d0c4421bd99df8152013d593 and 158431f46e4f67d967b1fb7b32c6015cd5a19204.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `Get Started.mdx` (1 hunks)
* `Quickstart1.mdx` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>Get Started.mdx</summary>

[style] ~12-~12: Consider shortening or rephrasing this to strengthen your wording.
Context: ...ustom form data to the records and even making changes to the No-Code Applications.  Some importa...

(MAKE_CHANGES)

</details>
<details>
<summary>Quickstart1.mdx</summary>

[uncategorized] ~8-~8: Possible missing comma found.
Context: ...are sending as a user is based on which Organization as all our Billings are rerouted to the...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~12-~12: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...date your API integration periodically. We also send out email notifications about...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[uncategorized] ~23-~23: Possible missing comma found.
Context: ...  href="https://worqhat.com/" >   Not a Developer Use WorqHat's No-Code Workspace options...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ew API Keys from the API Tokens screen. You can also delete the API Keys from the A...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~40-~40: Consider a shorter alternative to avoid wordiness.
Context: ...ctive API Keys.  **Creating API Keys**  In order to use the WorqHat API, you must first obt...

(IN_ORDER_TO_PREMIUM)

---

[style] ~62-~62: Consider a shorter alternative to avoid wordiness.
Context: ...nd we will set you up with an Account.  In order to use WorqHat's API, you will need to aut...

(IN_ORDER_TO_PREMIUM)

---

[uncategorized] ~83-~83: The preposition ‘to’ seems more likely in this position.
Context: ... per-request key, which is often useful for Connect applications that use multiple ...

(AI_HYDRA_LEO_REPLACE_FOR_TO)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>Quickstart1.mdx (1)</summary>

`1-4`: **YAML Front Matter Block**  
The file begins with a standard YAML front matter block setting the title. No issues noted here.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-26T17:46:35Z
user: login: coderabbitai[bot]
body: **Actionable comments posted: 0**

<details>
<summary>🧹 Nitpick comments (2)</summary><blockquote>

<details>
<summary>rate_limit.mdx (2)</summary><blockquote>

`9-11`: **Hyphenate Compound Adjective for Clarity.**  
In line 11, the phrase "rate limiting algorithms" serves as a compound adjective modifying "algorithms." Consider updating it to "rate-limiting algorithms" for improved readability.  
  
Apply diff:  
```diff
-... our rate limiting algorithms are designed ...
+... our rate-limiting algorithms are designed ...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~11-~11: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...nt level of access to our services. Our rate limiting algorithms are designed to balance the ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

</details>

</details>

---

`13-13`: **Consistent Hyphenation Requested.**  
On this line, "rate limiting mechanisms" should be changed to "rate-limiting mechanisms" to maintain uniformity in compound adjective usage throughout the document.  
  
Apply diff:  
```diff
-... our rate limiting mechanisms, we provide ...
+... our rate-limiting mechanisms, we provide ...
```

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~13-~13: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... our users understand and work with our rate limiting mechanisms, we provide detailed documen...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

</details>

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: CodeRabbit UI**
**Review profile: CHILL**
**Plan: Pro**

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 158431f46e4f67d967b1fb7b32c6015cd5a19204 and 744ac4034ed4e9c2f2bbb3577fc1c1dd854d2037.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `rate_limit.mdx` (1 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>rate_limit.mdx</summary>

[uncategorized] ~11-~11: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...nt level of access to our services. Our rate limiting algorithms are designed to balance the ...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[uncategorized] ~13-~13: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... our users understand and work with our rate limiting mechanisms, we provide detailed documen...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (5)</summary><blockquote>

<details>
<summary>rate_limit.mdx (5)</summary>

`1-3`: **Frontmatter is Properly Structured.**  
The YAML frontmatter defines the title correctly and uses the expected delimiters. No issues here.

---

`5-7`: **Clear Overview of Rate Limits.**  
The section "What are Rate Limits?" offers a concise introduction to the concept and its significance, which is appropriate for new documentation.

---

`15-19`: **Effective Explanation of the Need for Rate Limits.**  
The section "Why do we need rate limits?" clearly outlines multiple reasons — from mitigating abuse to ensuring fair access — which adds useful context for the reader.

---

`21-23`: **Well-Structured Sequential Reasoning.**  
The explanation of how rate limits protect resources and manage load is logically organized and easy to follow.

---

`25-30`: **Clear Rate Limit Specifications with Custom Tag Consideration.**  
The final section effectively communicates the specific rate limit (2000 requests per minute). Please ensure that the custom `<info>` tag is supported by your MDX rendering environment; otherwise, consider using a standard markdown callout or blockquote for compatibility.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->
state: COMMENTED
author_association: NONE
submitted_at: 2025-03-26T17:50:53Z
user: login: khatri-viren
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-03-26T18:26:04Z

Review comments:
diff_hunk: @@ -0,0 +1,85 @@
+---
+title: 'Quickstart'
+---
+
+## Base Endpoint for all API calls
+Right now, the API is only available on the `https://api.worqhat.com` domain. This is the only official domain that is applicable for all API Calls to the Application.
+
+The WorqHat API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The API key you use to authenticate the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted to the Organization you are using the API keys for.
+
+The WorqHat API doesn't support bulk updates. You can work on only one object per request. The WorqHat API differs for every account as we release new versions and tailor functionality. These docs are customized to your version of the API.
+
+If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API. You can subscribe to these notifications in your WorqHat account settings.
+
+**Base URL for all API calls**
+```
+https://api.worqhat.com/
+```
+
+<Card
+  title="No code applications"
+  href="https://worqhat.com/"
+>
+  Not a Developer Use WorqHat's No-Code Workspace options to get started with WorqHat and to do more with your WorqHat apps - without a single line of Code.
+</Card>
path: Quickstart1.mdx
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Rephrase “Not a Developer” Card Description**  
The content inside the "No code applications" card (lines 20–24) appears to be missing punctuation and could be clarified. Consider reformatting as follows:  
```diff
-   Not a Developer Use WorqHat's No-Code Workspace options to get started with Worqhat and to do more with your Worqhat apps - without a single line of Code.
+   Not a Developer? Use WorqHat's No-Code Workspace options to get started with Worqhat and do more with your apps—without writing a single line of code.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
  title="No code applications"
  href="https://worqhat.com/"
>
  Not a Developer? Use WorqHat's No-Code Workspace options to get started with Worqhat and do more with your apps—without writing a single line of code.
</Card>
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[uncategorized] ~23-~23: Possible missing comma found.
Context: ...  href="https://worqhat.com/" >   Not a Developer Use WorqHat's No-Code Workspace options...

(AI_HYDRA_LEO_MISSING_COMMA)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-03-26T17:46:34Z
author_association: NONE
diff_hunk: @@ -0,0 +1,85 @@
+---
+title: 'Quickstart'
+---
+
+## Base Endpoint for all API calls
+Right now, the API is only available on the `https://api.worqhat.com` domain. This is the only official domain that is applicable for all API Calls to the Application.
+
+The WorqHat API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The API key you use to authenticate the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted to the Organization you are using the API keys for.
+
+The WorqHat API doesn't support bulk updates. You can work on only one object per request. The WorqHat API differs for every account as we release new versions and tailor functionality. These docs are customized to your version of the API.
+
+If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API. You can subscribe to these notifications in your WorqHat account settings.
+
+**Base URL for all API calls**
+```
+https://api.worqhat.com/
+```
+
+<Card
+  title="No code applications"
+  href="https://worqhat.com/"
+>
+  Not a Developer Use WorqHat's No-Code Workspace options to get started with WorqHat and to do more with your WorqHat apps - without a single line of Code.
+</Card>
+
+**Authentication**
+You can get your Organization's API Key and your API Key from the Workspace Admin Panel. You can find the API Tokens screen under the Workspace Settings or by visiting the Developers Portal. You can also find the API Tokens screenby visiting the following URL:
+
+```
+https://$workspace.worqhat.app/workspace/developers
+```
+
+> $workspace is the name of your Workspace. You can find the name of your Workspace in the URL of your Workspace. For example, if your Workspace URL is https://myworkspace.worqhat.app, then your Workspace name is myworkspace.
+
+In case you are not the Admin/Leader/Developer of the Workspace, you will not be able to access the API Tokens screen. In such a case, please contact your Workspace Admin/Leader/Developer to get the API Keys or request them to add you as a Developer to the Workspace.
+
+You can copy the API Keys from the API Tokens screen and use them in your API Calls. You can also generate new API Keys from the API Tokens screen. You can also delete the API Keys from the API Tokens screen. Please note that deleting the API Keys will revoke access to the API for the respective API Keys.
+
+**Creating API Keys**
+
+In order to use the WorqHat API, you must first obtain an API key and the ORG Key. We offer a genenrous free tier that gets reset every month. You can also upgrade to a paid plan to get more API calls and more features.
path: Quickstart1.mdx
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Refine Instructional Wording & Correct Spelling**  
On line 41, consider simplifying the sentence and fixing a typo (“genenrous” should be “generous”). For example:  
```diff
- In order to use the WorqHat API, you must first obtain an API key and the ORG Key. We offer a genenrous free tier that gets reset every month. You can also upgrade to a paid plan to get more API calls and more features.
+ To use the WorqHat API, obtain an API key and the ORG Key. We offer a generous free tier that resets monthly, with an option to upgrade for additional API calls and features.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
To use the WorqHat API, obtain an API key and the ORG Key. We offer a generous free tier that resets monthly, with an option to upgrade for additional API calls and features.
`````

</details>

<!-- suggestion_end -->

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-03-26T17:46:34Z
author_association: NONE
diff_hunk: @@ -0,0 +1,85 @@
+---
+title: 'Quickstart'
+---
+
+## Base Endpoint for all API calls
+Right now, the API is only available on the `https://api.worqhat.com` domain. This is the only official domain that is applicable for all API Calls to the Application.
+
+The WorqHat API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The API key you use to authenticate the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted to the Organization you are using the API keys for.
+
+The WorqHat API doesn't support bulk updates. You can work on only one object per request. The WorqHat API differs for every account as we release new versions and tailor functionality. These docs are customized to your version of the API.
+
+If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API. You can subscribe to these notifications in your WorqHat account settings.
+
+**Base URL for all API calls**
+```
+https://api.worqhat.com/
+```
+
+<Card
+  title="No code applications"
+  href="https://worqhat.com/"
+>
+  Not a Developer Use WorqHat's No-Code Workspace options to get started with WorqHat and to do more with your WorqHat apps - without a single line of Code.
+</Card>
+
+**Authentication**
+You can get your Organization's API Key and your API Key from the Workspace Admin Panel. You can find the API Tokens screen under the Workspace Settings or by visiting the Developers Portal. You can also find the API Tokens screenby visiting the following URL:
+
+```
+https://$workspace.worqhat.app/workspace/developers
+```
+
+> $workspace is the name of your Workspace. You can find the name of your Workspace in the URL of your Workspace. For example, if your Workspace URL is https://myworkspace.worqhat.app, then your Workspace name is myworkspace.
+
+In case you are not the Admin/Leader/Developer of the Workspace, you will not be able to access the API Tokens screen. In such a case, please contact your Workspace Admin/Leader/Developer to get the API Keys or request them to add you as a Developer to the Workspace.
+
+You can copy the API Keys from the API Tokens screen and use them in your API Calls. You can also generate new API Keys from the API Tokens screen. You can also delete the API Keys from the API Tokens screen. Please note that deleting the API Keys will revoke access to the API for the respective API Keys.
path: Quickstart1.mdx
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Concise Description for API Keys Management**  
On line 37, three similar sentences about API Keys could be streamlined. For instance, they could be combined to improve readability:  
```diff
- You can copy the API Keys from the API Tokens screen and use them in your API Calls. You can also generate new API Keys from the API Tokens screen. You can also delete the API Keys from the API Tokens screen.
+ You can copy, generate, or delete API Keys directly from the API Tokens screen for use in your API calls.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
You can copy, generate, or delete API Keys directly from the API Tokens screen for use in your API calls. Please note that deleting the API Keys will revoke access to the API for the respective API Keys.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~37-~37: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ew API Keys from the API Tokens screen. You can also delete the API Keys from the A...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-03-26T17:46:35Z
author_association: NONE
diff_hunk: @@ -0,0 +1,85 @@
+---
+title: 'Quickstart'
+---
+
+## Base Endpoint for all API calls
+Right now, the API is only available on the `https://api.worqhat.com` domain. This is the only official domain that is applicable for all API Calls to the Application.
+
+The WorqHat API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The API key you use to authenticate the request determines whether the request you are sending as a user is based on which Organization as all our Billings are rerouted to the Organization you are using the API keys for.
+
+The WorqHat API doesn't support bulk updates. You can work on only one object per request. The WorqHat API differs for every account as we release new versions and tailor functionality. These docs are customized to your version of the API.
+
+If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API. You can subscribe to these notifications in your WorqHat account settings.
path: Quickstart1.mdx
user: login: coderabbitai[bot]
body: _🛠️ Refactor suggestion_

**Vary Sentence Beginnings for Improved Readability**  
Several sentences on line 12 begin with "We". Consider rephrasing some of these sentences to avoid repetition and improve flow. For example, merging related ideas could help:  
```diff
- We recommend that you use the latest version of the API whenever possible. We release new versions of the API frequently, so you may need to update your API integration periodically. We also send out email notifications about new versions of the API.
+ We recommend using the latest API version whenever possible. Since new versions are released frequently, you might need to update your integration periodically; email notifications will alert you of these changes.
```  



<!-- suggestion_start -->

<details>
<summary>📝 Committable suggestion</summary>

> ‼️ **IMPORTANT**
> Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

`````suggestion
If you're using a version of the API that is older than the latest version, you may see older endpoints and outdated response schemas. We recommend using the latest API version whenever possible. Since new versions are released frequently, you might need to update your integration periodically; email notifications will alert you of these changes. You can subscribe to these notifications in your WorqHat account settings.
`````

</details>

<!-- suggestion_end -->

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 LanguageTool</summary>

[style] ~12-~12: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...date your API integration periodically. We also send out email notifications about...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit -->
created_at: 2025-03-26T17:46:35Z
author_association: NONE

PR comments:
user: login: coderabbitai[bot]
created_at: 2025-03-26T17:43:46Z
body: <!-- This is an auto-generated comment: summarize by coderabbit.ai -->
<!-- walkthrough_start -->

## Walkthrough
Three new documentation files for the WorqHat Public API have been introduced. The "Get Started.mdx" file provides an overview of the API, including setup instructions and links to additional resources for community engagement. The "Quickstart1.mdx" file details the API’s usage, endpoints, authentication procedures, and best practices for secure requests. Additionally, the "rate_limit.mdx" file explains the rate limiting mechanisms of the API, including allowed request limits and guidelines for optimal usage.

## Changes
| File(s)                          | Change Summary                                                                                                                                              |
|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Get Started.mdx                  | Added new documentation file outlining the overview of the WorqHat API, setup instructions, and community engagement resources.                             |
| Quickstart1.mdx                  | Added new documentation file detailing API usage, endpoints, authentication procedures, and best practices for secure requests.                             |
| rate_limit.mdx                   | Added new documentation file explaining the rate limits of the API, including definitions, allowed requests, error codes, and optimization tips.            |

## Suggested reviewers
- khatri-viren

## Poem
> Hopping through pages with a joyful beat,  
> I found new docs that are super neat!  
> API guides to nibble, a carrot delight,  
> Setup and quickstart shining bright.  
> I bounce with glee and a whiskered cheer—  
> Here's to progress, my dear API peer!  
> 🥕🐇✨

<!-- walkthrough_end -->
<!-- internal state start -->


<!-- DwQgtGAEAqAWCWBnSTIEMB26CuAXA9mAOYCmGJATmriQCaQDG+Ats2bgFyQAOFk+AIwBWJBrngA3EsgEBPRvlqU0AgfFwA6NPEgQAfACgjoCEejqANiS6lckRLjQUatADSQAjtngMA1g6dcAwA5bGYBSi4AJgBOAwBVREjIAGUAdzRuDDQhNBiANgAWI31jcCgyenwAMxwCYjJlFwVWdi5efmFRcSkZeSYlKlV1LR1Skyg4VFRMOsJScipmplaMTkgqNPsw5id5OQVBlTVNbV0wQzLTAwBxEjsUx2c6DWZaAA8OAwAiX4MAYn+kAAggBJBqLah0basPb8WoMWCYUiIIzAyDkLa0fAMMLsajwfBYarwKyQcS4Kz0b53B5PZoACUoJG+kCRMhIZBQawoimwDDo7l4+Ak8Fo8AwRHQWBFlFFJC2NXJsBIkAA6vgKB4GdRIAAFbACCw+EF60EaGAqyDY3FsNb8PDG8jIXBW7jYCjcfBJeHK1XAs3uNIIRGQapoBik9RQ5C4hwsbk0IhLQkYZBpdSwdWa7XUADkyAASgBRFLQMACNBJehJCiigWIdxkFROqXYWsu/A8SjVTXMSASJyE9vkqv+bahqsY6getAWSAWZHYNCkHi8huICVEdwDVULJqp9yYejMRTwEkMAlEzuQYKEADCin93G4xsv4mvFtBdhIzG47PgAAvaRlV1CMN3JLtXX9M0UGQfcqAsCx5DQQdSRbVVj3QWhRSSZB20oG8KBIeUtmg8lKGYZAlVretVV4Qk+AIa0SJICx8G4O1NDMK0bTxe0JQYCxsCUZAkjEVNkF7PgklwcRJUgbBuFNUF0AYDd3GqEgZwoLd0Ege8nFoG5eSUhc0FkfA8EgDNXQXCVx2YtBaHFD9snnYjECsigG3cQThPFBSwUgU8lHnCVpN2Nz3ADVS+K4q8MCPTxvD8AJnEgIhvCUHcWGYbAMHUeQyCIFdf3YfgX01XACvUeBpCPDAaxxeA5xCuhWvsjB/AtYsIyzS8KHoYVRVE/SKTJLC0AUChPK9Jq9NgWRuEoJ1fDDTUww9aC+BId5X01RKLTgVUVnywrcBQxAVrEOC2XgIhYGNR6XCbDAmFnIg9KYJCVEOtz0FPBSlCkdiVooZAsIYYjqE1RANCMQEQQsGgU2vSC/RYoSnES6jaj2r1niqPh3SNE12Dq6QSlvBUw1JTCXLoLgAANaVSekXjed5mZszNyUsVU80AXg3AAC9yA2ceQJoSZYi82leg82BAQrLsDUtR1OxYrl8S3Phn4/gMCAwCMABFVL/HpABGV4Pi+X5vgBIEwQhJpoUQHY4SVRFkSpgx0Uxa0cX4xwAZJMkJuhb4zZ8C3AlZdlIAiLkJVwXlaH5QUWMcKMFPI9syt9ci1dzTWzWO3ig64h1KQlEDyMrH1Ki9FONr4WLGDnCxG3sG7z1kPTXV1cj25mdTpE3I1MLsZnYDk7hEA4AB6RfMngDQ0hzJFNBWZmvzsUTofgCIXStEsy2qbB52yGriMLq1Yr896Ar09RkE87yBTATV6rWaF4kLAAMt3SKYAyC7noMRLw0g7DK3FA1SAAApFIAB5YIoD3pPggdIeaeFGo1kcE1IykAGTQGgHqDY2DrynSfPDS0qp4oVV/P+KsQE65b0xu3XwJB5AEXoNJOoKo1g+ESndcQ0JmJ51rAWfgFBSqFUAolI81QtISQUmoJCekppj0QHrAwJ1A62nxADbGukSRsN1AIS+60lK0BjOgW+GB8B2HdlVImeDFIdnsLAKyFh6AbwoOtWyWYiSqkECIW64MKFQIcHvbCuEQIEQhhjPAUZgKY0XDQBwKkByEVTBjVC+AxTV1sc0JuhS1iQyahQ66VD7CIl/FWIMfNHHiAvLjVuGJaZSAhpJdAaFFyT2VKZR6akPr2lkvJIgujgR4EEeId8eThQCnTp5ex9D7jaCpI/ISIlFr4DIl2QQ2csCcO4VJXk/Yi6an8NwCM/paDMAlPqTAbF5aY3gH+aqmABS+n8Tcu53YKCPJ0ZJC0iRCJrO5A4Cg/JmhEkyo0FMCksK7GyF9IKsEuGyG7v5XZucrTkA3EVX5CAaDGgcHpbEuwJRSU2u3S8SFaHAiwHtNAf4yRKlmKcnhiAC6oBGmKTOc4iRSiCfpDIFBCrIuVtZcSHpiW8AjPMkCxEMniK7Ny3R+iGH2iYE/ESIExXHzsIqiSDYOm7F8HpOVt926QOwNA7uTCAKAQHlae18BiJV34SQshKQ3nCkiWgWZFMFnwuYrwVi9oCrBtdN/YC9BwLjwRkYR2yNUbtIkbxUQi40Zpl9ATaq0JNqkzfJACmYjUSGxpliSuRi8lh1OjDFwLNo5pStjbbm+sHaG2uEsEgAB9Y0jzNBcztn8JGzsEJQhrB7Cg8gvZIklL7f2tNG380pJHQsUJIAAI+a/eOU4k5YBTmnDObg1wijFN9FgkbBGbikAY4OIjw3up3cOuqCk2De0KogKid9VTFw1iCVSsVy70LrfaFWTo2HrJJBdPJSp+32RHU6/ai4JRupIJ6ngHovQ+ieailcWGMRhAiHwJDJBom4BPrqS8WAIghWcqqLNMFVJBKedNa6ohzz1XoOINgYYqBsFic6lhwET6qg+YTAhPykPvv3TR7k5a0zyvxaqAI6iiruFVa1LTl13Hhhw/nVcSph6BjXFGyZ0p5CbklGSRJQmEyygoMGNijz1P2GxTQfsUNg12alLRHw9CkAwu4LrFN2rIP7w2aSSTGxEpzlVBEBAVTpNWC4npZDH6aPbOfgpYUNAJLwpXNoNMdgVAETeu7XSCkjN8CTTojpncPGEXcUR9FUoIpUGhbCj0qp2LOWtGpqUCARmpzQMok04NCS0Fod+dAXcuzccjGY+L2XFO0qYvfCzARrODzsIkyGt9O77OhGZZiUQAAMN2okOocMgSJHm8AkAtMCFydUiSd1kO4ciOqQ55NxWNCKfYX0stmptXcb97genIH4wRKHX6Qr2gKOg0IsI1C0kk8Q88OkcQE0BPS7cTMsa7AUoppL9sqh9Dl3RyDumd1+wStd9N7ByhAlOaah95ltXfh6H5/CjvJKaoRAhiaqkkGUd0SQbF5DZFFKVGgmMNsjr0l6N89U8aYyA7qYKYHU1puBCjA86NWNY1ze0pUhaiYyNw2TBgKmKSa+psEWm/2RHruckoWgLN+1DsU525m3aSgXCuBUKpnK8DzERTOloXEuCbBhLsedid+hPiGCcUY5xDATDj+oAdYpEADuIqROgA70p2FKAYXPlsACsAAOQoABmS21RCj5BIIUao+QADstACg94EK3gQg+m9RAYPkK7deGC0Fr2gS2MRruFGz9X8okAe+FEKBGQoV2m+FDoPvmIDAojVCiKoAQTfa89579UBgls78uXr7XwotBrtN57yv1fEA8+4AL3N4vJE9UaQZelQ2eQAA= -->

<!-- internal state end -->
<!-- tips_start -->

---



<details>
<summary>🪧 Tips</summary>

### Chat

There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=WorqHat/worqhat-docs&utm_content=29):

- Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  - `I pushed a fix in commit <commit_id>, please review it.`
  - `Generate unit testing code for this file.`
  - `Open a follow-up GitHub issue for this discussion.`
- Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples:
  - `@coderabbitai generate unit testing code for this file.`
  -	`@coderabbitai modularize this function.`
- PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.`
  - `@coderabbitai read src/utils.ts and generate unit testing code.`
  - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.`
  - `@coderabbitai help me debug CodeRabbit configuration file.`

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

### CodeRabbit Commands (Invoked using PR comments)

- `@coderabbitai pause` to pause the reviews on a PR.
- `@coderabbitai resume` to resume the paused reviews.
- `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
- `@coderabbitai full review` to do a full review from scratch and review all the files again.
- `@coderabbitai summary` to regenerate the summary of the PR.
- `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR.
- `@coderabbitai resolve` resolve all the CodeRabbit review comments.
- `@coderabbitai plan` to trigger planning for file edits and PR creation.
- `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository.
- `@coderabbitai help` to get help.

### Other keywords and placeholders

- Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed.
- Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description.
- Add `@coderabbitai` anywhere in the PR title to generate the title automatically.

### CodeRabbit Configuration File (`.coderabbit.yaml`)

- You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository.
- Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information.
- If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json`

### Documentation and Community

- Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit.
- Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback.
- Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

</details>

<!-- tips_end -->
author_association: NONE
user: login: devactivity-app[bot]
created_at: 2025-03-26T18:26:12Z
body: ## Pull Request Summary by [devActivity](https://app.devactivity.com/analytics/?activeTab=pullRequests&organizationId=70) 
  
### Metrics
<img alt="Cycle Time: 44m" title="Cycle Time: 44m" src="https://img.shields.io/badge/cycle_time-44m-darkblue" /> <img alt="Coding Time: 2m" title="Coding Time: 2m" src="https://img.shields.io/badge/coding_time-2m-blue" /> <img alt="Pickup Time: 2m" title="Pickup Time: 2m" src="https://img.shields.io/badge/pickup_time-2m-blue" /> <img alt="Review Time: 39m" title="Review Time: 39m" src="https://img.shields.io/badge/review_time-39m-blue" /> <img alt="Comments: 1" title="Comments: 1" src="https://img.shields.io/badge/comments-1-darkgreen" />
    
  ### Achievements
  - @khatri-viren
  Earned XP: 15⭐
    [Sign up here to check your progress](https://app.devactivity.com/login)
  
- @Swapnaja964
  Earned XP: 5⭐
    [Sign up here to check your progress](https://app.devactivity.com/login)
  
  
author_association: NONE