Make your APIs discoverable, understandable, and callable by AI.
We’re excited to announce the release of API Catalogs, a powerful new feature that makes your existing APIs instantly usable by AI applications via the Vendia MCP Server.
With API Catalogs, you can simply upload your OpenAPI or Swagger specification files to enable AI agents to automatically discover, understand, and call your APIs — no custom integrations or manual endpoint descriptions required.
Getting Started
Supported Formats
Supported Authentication
API Catalogs do not automatically handle authentication, giving you full control over how credentials are managed. Supported options include:
Credential Security Tip: Use caution when adding authentication credentials to headers. Ensure your Vendia account is secure and consider using short-lived tokens or API keys with limited scope.
Receipts
Receipts are automatically generated for all API interactions, providing visibility into who is accessing or modifying data. This makes it easier to audit activity, analyze usage patterns, and ensure compliance. GET requests generate read receipts, while POST, PUT, and DELETE requests generate write receipts.
API Catalog support is available in the Free, Pro and Enterprise tiers. For more information visit docs.vendia.com
With API Catalogs, you can simply upload your OpenAPI or Swagger specification files to enable AI agents to automatically discover, understand, and call your APIs — no custom integrations or manual endpoint descriptions required.
Getting Started
- Prepare Your Specification - Ensure you have a valid OpenAPI or Swagger file in .json, .yaml, or .yml format.
- Add to Vendia - Create a new API Catalog entry directly in the Vendia UI.
- Configure Settings - Optionally override base URLs, versions, headers, or descriptions to match your environment.
- Save the Catalog - Once saved, your Catalog is automatically enabled in your MCP Server tools
- Use with AI Applications - MCP-compatible AI applications can now discover and interact with your APIs.
Supported Formats
| Format | Extensions | Description |
|---|---|---|
| JSON | .json | OpenAPI/Swagger specifications in JSON format |
| YAML | .yaml, .yml | OpenAPI/Swagger specifications in YAML format |
Supported Authentication
API Catalogs do not automatically handle authentication, giving you full control over how credentials are managed. Supported options include:
- Custom Headers — Add API keys, bearer tokens, or other authentication headers in the catalog configuration.
- Public APIs — No additional configuration required for APIs without authentication.
Credential Security Tip: Use caution when adding authentication credentials to headers. Ensure your Vendia account is secure and consider using short-lived tokens or API keys with limited scope.
Receipts
Receipts are automatically generated for all API interactions, providing visibility into who is accessing or modifying data. This makes it easier to audit activity, analyze usage patterns, and ensure compliance. GET requests generate read receipts, while POST, PUT, and DELETE requests generate write receipts.
API Catalog support is available in the Free, Pro and Enterprise tiers. For more information visit docs.vendia.com