add aidbase app

[TenTwo07]

Summary

This PR introduces updates and improvements to the functions.json file for the Aidbase application. The changes ensure consistency in naming conventions, descriptions, and parameter structures for all API functions.

APP_URL: https://aidbase.ai
APP_API_DOCS_URL: https://docs.aidbase.ai

Integrated API

AIDBASE__GET_ALL_CHATBOTS - Retrieve a list of all chatbots associated with the user. AIDBASE__GET_CHATBOT_BY_ID - Retrieve details of a specific chatbot by its unique ID. AIDBASE__POST_CHATBOT_REPLY - Send a reply to a specific chatbot. AIDBASE__GET_CHATBOT_KNOWLEDGE - Retrieve all knowledge items associated with a specific chatbot. AIDBASE__PUT_CHATBOT_KNOWLEDGE - Add or update a knowledge item in a chatbot. AIDBASE__REMOVE_CHATBOT_KNOWLEDGE - Remove a knowledge item from a chatbot.

Fuzzy Tests

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__GET_ALL_CHATBOTS --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "Can you show me all the chatbots in the system?"

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__GET_CHATBOT_BY_ID --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "Get the details of the chatbot with ID cvkHIqhSMWaiwRP5O763K."

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__POST_CHATBOT_REPLY --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "Send the message 'hello?' to the chatbot with ID cvkHIqhSMWaiwRP5O763K."

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__GET_CHATBOT_KNOWLEDGE --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "show me all the chatbot knowledge,ID='cvkHIqhSMWaiwRP5O763K'."

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__PUT_CHATBOT_KNOWLEDGE --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "Add the knowledge base of the chatbot with ID cvkHIqhSMWaiwRP5O763K for the knowledge item with ID 3facf6c9-4bfe-4524-838d-75ea395eecee."

docker compose exec runner python -m aipolabs.cli.aipolabs fuzzy-test-function-execution --function-name AIDBASE__REMOVE_CHATBOT_KNOWLEDGE --linked-account-owner-id <LINKED_ACCOUNT_OWNER_ID> --aipolabs-api-key <AIPOLABS_API_KEY> --prompt "Remove the knowledge item with ID 3facf6c9-4bfe-4524-838d-75ea395eecee from the chatbot with ID cvkHIqhSMWaiwRP5O763K."

Videos

aidbase.mp4

Summary by CodeRabbit

• Bug Fixes
  • Corrected formatting in a configuration file to ensure proper JSON structure.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This change involves a single modification to the apps/aidbase/functions.json file, where the trailing closing bracket ] at the end of the JSON array was removed. No other content or structure within the file was altered, and there were no changes to any exported or public entities.

Changes

File(s)	Change Summary
apps/aidbase/functions.json	Removed the trailing closing bracket ] from the JSON array. No other modifications were made.

Poem

A bracket hops away, so neat,
JSON lines now feel complete.
With every tidy, careful sweep,
The codebase dreams in order deep.
A rabbit grins, its work well done—
One little change, and order won!
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eac495b and 486df19.

📒 Files selected for processing (1)

• apps/aidbase/functions.json (0 hunks)

---

Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• 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 resolve resolve all the CodeRabbit review comments.
• @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 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 for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

ACI Integration Code Review (Sonnet 3.7) - 2025-04-18 14:47:31.120

This review analyzes changes to integration files in the app/ directories.

Code Review: Aidbase Integration

I've reviewed the provided Aidbase integration files. Let me provide my analysis of the functions.json file based on the API integration standards and requirements.

Issues and Recommendations

1. Missing functions.json content in the diff

Issue: The diff only shows the removal of a closing bracket at the end of the file, but doesn't show the actual content of the functions.json file that was added.

Recommendation: The complete functions.json content should be included in the diff for a proper review. Based on the PR description, there should be 6 functions defined (GET_ALL_CHATBOTS, GET_CHATBOT_BY_ID, etc.).

2. Potential JSON syntax error

Issue: The diff shows removal of the closing bracket ] at the end of the file, which would make the JSON invalid.

Recommendation: Ensure the JSON file is properly formatted with the correct closing brackets.

3. Server URL configuration

Issue: Based on the PR description, the API URL is https://aidbase.ai, but I can't verify if the server_url in each function's protocol_data is correctly configured.

Recommendation: Ensure that each function has the correct server_url that includes the base URL and API version path according to the special rules.

4. Function naming convention

Issue: The PR description mentions function names like AIDBASE__GET_ALL_CHATBOTS, which follows the correct naming convention, but I can't verify if all functions in the file follow this pattern.

Recommendation: Ensure all function names follow the pattern APPLICATIONNAME__FUNCTION_NAME in uppercase.

Overall Assessment

Due to the limited information in the diff (only showing the removal of a closing bracket), I cannot provide a comprehensive review of the actual function specifications, parameter structures, required fields, or visible fields.

Based on the PR description and the app.json file, the integration appears to be well-structured with:

• Proper authentication mechanism (Bearer token in Authorization header)
• Clear categorization (chat, integration, workflow)
• Comprehensive set of functions for chatbot management

However, without seeing the actual functions.json content, I can only provide a Needs Improvement assessment due to the potential JSON syntax error and inability to verify the function specifications.

Next Steps for the Developer

1. Fix the JSON syntax error by ensuring the file has proper closing brackets
2. Verify that all functions follow the naming convention AIDBASE__FUNCTION_NAME
3. Ensure each function has:
   • Proper server_url configuration including the base URL and API version
   • Correct required fields based on the API documentation
   • Appropriate visible fields (excluding authorization and version parameters)
4. Resubmit the PR with the complete functions.json content for a thorough review

Once these issues are addressed, the integration can be properly evaluated for functionality and adherence to the integration standards.

[thisisfixer]

duplicated, aidbase already exisit