validate-connector

Validate a Sim knowledge base connector by cross-referencing its implementation, OAuth config, and registry entries against API documentation and repository conventions. This process handles authentication, pagination, document mapping, and tags to ensure accuracy and prevent runtime errors.

A connector code audit checks OAuth configuration and pagination to ensure compliance with API documentation and repository conventions. It validates authentication setup, configuration settings, and document mapping to identify critical issues, warnings, and suggestions for connector repair.

Fix critical connector validation errors by running a connector audit that identifies and categorizes issues. The validation process applies automatic fixes for critical issues where possible, ensuring the Sim knowledge base connector is correct and follows all repository conventions.

Yes, connector validation checks document mapping and tags for API compliance by cross-referencing implementation details against API documentation. It audits authentication, configuration, pagination, and registry entries to ensure the Sim knowledge base connector is accurate and complete.

Yes, you need access to both API documentation and connector code to validate repository conventions. The validation process cross-references the connector's implementation, OAuth config, and registry entries against these sources to ensure full API compliance and error-free operation.

A Sim knowledge base connector fails validation when its implementation, OAuth config, or registry entries do not match API documentation and repository conventions. The code audit identifies these mismatches across authentication, pagination, and document mapping, categorizing them as critical issues or warnings.