@openpets/quo 1.0.0

package/.env.example

@@ -0,0 +1,7 @@
+# Authentication
+# Credentials: https://my.quo.com/settings/api - Quo expects the raw API key in the Authorization header, without a Bearer prefix.
+QUO_API_KEY=
+
+# Optional host override
+# Defaults to https://api.openphone.com
+QUO_HOST=

package/CHANGELOG.md

@@ -0,0 +1,5 @@
+# Changelog
+
+## 1.0.0
+
+- Initial Quo pet generated from the official Quo OpenAPI specification.

package/README.md

@@ -0,0 +1,50 @@
+# Quo
+
+OpenPets plugin for the [Quo API](https://www.quo.com/docs/mdx/api-reference/introduction). It is generated from Quo's official OpenAPI spec and exposes tools for calls, contacts, conversations, messages, phone numbers, users, and webhooks.
+
+## Quick Start
+
+1. Generate a Quo API key from the API tab in workspace settings.
+2. Add the key to your environment:
+
+   ```bash
+   export QUO_API_KEY="your-api-key"
+   ```
+
+3. Test the plugin:
+
+   ```bash
+   pets exec quo-test-connection --plugin ./index.ts --args '{}' --json
+   ```
+
+## Available Tools
+
+The generated tools cover:
+
+- Calls and call recordings, summaries, transcripts, and voicemails
+- Contacts and contact custom fields
+- Conversations and messages
+- Phone numbers and users
+- Webhooks for messages, calls, call summaries, and call transcripts
+
+Write tools such as contact creation, message sending, webhook creation, updates, and deletes are filtered when Quo read-only mode is enabled.
+
+## Authentication
+
+Quo uses API-key authentication in the `Authorization` header. Use the raw API key value; Quo does not use a Bearer token prefix.
+
+Optional host override:
+
+```bash
+export QUO_HOST="https://api.openphone.com"
+```
+
+## Regenerating
+
+This pet uses Quo's hosted OpenAPI document:
+
+```bash
+pets generate-openapi
+```
+
+Generated OpenAPI files are split into `openapi-client.ts` for reusable client helpers and `openapi-tools.ts` for tool definitions.