mirror of
https://github.com/outbackdingo/optimclaw.git
synced 2026-08-25 14:53:34 +00:00
feat(skills): add 245 Pica integration skills covering full catalog
Add SKILL.md files for all 252 Pica platform integrations (245 new, 7 internal skills already existed). Covers the full Pica catalog: - CRM: attio, close, freshdesk, gorgias, hubspot, intercom, klaviyo, zoho, etc. - Communication: bluesky, linked-in, meta, x, teams, twilio, ring-central, etc. - DevOps: git-lab, circle-ci, netlify, render, n8n, neon, ngrok, posthog, etc. - AI/LLM: anthropic, deep-seek, gemini, perplexity, open-router, x-ai - E-commerce: big-commerce, shopify-admin, shopify-storefront, square, woocommerce - Payments: chargebee, paystack, square, stripe - Email: sendgrid, mailchimp-marketing, mailgun, loops - And 190+ more across all categories ~83 skills have detailed API docs (base URLs, example http() calls, notes). ~122 skills have auth setup and credential config from Pica metadata. Skills are embedded into the binary at compile time via the bundling infrastructure added to v2-architecture, making them available on every IronClaw install without needing ClawHub. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
This commit is contained in:
@@ -0,0 +1,61 @@
|
||||
---
|
||||
name: 1-password
|
||||
version: "1.0.0"
|
||||
description: 1Password API — 1Password is a secure password manager that consolidates credentials
|
||||
activation:
|
||||
keywords:
|
||||
- "1-password"
|
||||
- "1password"
|
||||
- "security"
|
||||
patterns:
|
||||
- "(?i)1.?password"
|
||||
tags:
|
||||
- "security"
|
||||
- "identity"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [1PASSWORD_CONNECT_SERVER_URL, 1PASSWORD_CONNECT_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# 1Password API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`{1PASSWORD_CONNECT_SERVER_URL}/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**List vaults:**
|
||||
```
|
||||
http(method="GET", url="{1PASSWORD_CONNECT_SERVER_URL}/v1/vaults")
|
||||
```
|
||||
|
||||
**List items in vault:**
|
||||
```
|
||||
http(method="GET", url="{1PASSWORD_CONNECT_SERVER_URL}/v1/vaults/{vault_id}/items")
|
||||
```
|
||||
|
||||
**Get item details:**
|
||||
```
|
||||
http(method="GET", url="{1PASSWORD_CONNECT_SERVER_URL}/v1/vaults/{vault_id}/items/{item_id}")
|
||||
```
|
||||
|
||||
**Create item:**
|
||||
```
|
||||
http(method="POST", url="{1PASSWORD_CONNECT_SERVER_URL}/v1/vaults/{vault_id}/items", body={"vault": {"id": "<vault_id>"},"category": "LOGIN","title": "My Login","fields": [{"purpose": "USERNAME","value": "[email protected]"},{"purpose": "PASSWORD","value": "secret"}]})
|
||||
```
|
||||
|
||||
**Delete item:**
|
||||
```
|
||||
http(method="DELETE", url="{1PASSWORD_CONNECT_SERVER_URL}/v1/vaults/{vault_id}/items/{item_id}")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Item categories: `LOGIN`, `PASSWORD`, `SECURE_NOTE`, `CREDIT_CARD`, `IDENTITY`, `DOCUMENT`.
|
||||
- Fields have `purpose`: `USERNAME`, `PASSWORD`, `NOTES`.
|
||||
- The Connect server must be running and accessible at the configured URL.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: 7-shifts
|
||||
version: "1.0.0"
|
||||
description: 7shifts API — 7Shifts is a cloud‑based workforce management platform tailored for restaurants
|
||||
activation:
|
||||
keywords:
|
||||
- "7-shifts"
|
||||
- "7shifts"
|
||||
- "hospitality"
|
||||
patterns:
|
||||
- "(?i)7.?shifts"
|
||||
tags:
|
||||
- "hospitality"
|
||||
- "scheduling"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# 7shifts API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> 7Shifts is a cloud‑based workforce management platform tailored for restaurants, combining intuitive drag‑and‑drop scheduling, mobile time tracking, automated payroll and tip management, labor complia
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: ably-control
|
||||
version: "1.0.0"
|
||||
description: Ably Control API — Ably Control API is a RESTful interface that enables developers and DevOps teams
|
||||
activation:
|
||||
keywords:
|
||||
- "ably-control"
|
||||
- "ably control"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)ably.?control"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABLY_CONTROL_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Ably Control API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Ably Control API is a RESTful interface that enables developers and DevOps teams to programmatically provision, configure, and manage real-time infrastructure—such as apps, API keys, namespaces, queue
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABLY_CONTROL_ACCESS_TOKEN` — Access Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: ably
|
||||
version: "1.0.0"
|
||||
description: Ably API — Ably Pub/Sub is a global serverless real-time messaging platform that delivers s
|
||||
activation:
|
||||
keywords:
|
||||
- "ably"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)ably"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABLY_ENCODED_API_KEY]
|
||||
---
|
||||
|
||||
# Ably API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> Ably Pub/Sub is a global serverless real-time messaging platform that delivers sub‑60 ms latency pub/sub capabilities—including message history, presence detection, exactly‑once delivery, and guarante
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Basic ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABLY_ENCODED_API_KEY` — API Key (RFC 4648 Base64 Encoded)
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: abstract-avatars
|
||||
version: "1.0.0"
|
||||
description: Abstract Avatars API — An API that generates customizable user avatars based on names or unique identif
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-avatars"
|
||||
- "abstract avatars"
|
||||
- "avatar generation"
|
||||
patterns:
|
||||
- "(?i)abstract.?avatars"
|
||||
tags:
|
||||
- "avatar"
|
||||
- "images"
|
||||
- "avatar-generation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_AVATARS_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Avatars API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that generates customizable user avatars based on names or unique identifiers, enabling applications to automatically create consistent, visually distinct profile images without requiring users
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_AVATARS_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-company-enrichment
|
||||
version: "1.0.0"
|
||||
description: Abstract Company Enrichment API — An API that enriches company records with firmographic data such as industry
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-company-enrichment"
|
||||
- "abstract company enrichment"
|
||||
- "data enrichment"
|
||||
patterns:
|
||||
- "(?i)abstract.?company.?enrichment"
|
||||
tags:
|
||||
- "data-enrichment"
|
||||
- "enrichment"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_COMPANY_ENRICHMENT_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Company Enrichment API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that enriches company records with firmographic data such as industry, size, location, and domain details, enabling businesses to enhance lead profiles, improve segmentation, and power more acc
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_COMPANY_ENRICHMENT_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-email-reputation
|
||||
version: "1.0.0"
|
||||
description: Abstract Email Reputation API — An API that evaluates the reputation of email addresses by analyzing risk factor
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-email-reputation"
|
||||
- "abstract email reputation"
|
||||
- "email verification"
|
||||
patterns:
|
||||
- "(?i)abstract.?email.?reputation"
|
||||
tags:
|
||||
- "tools"
|
||||
- "email-verification"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_EMAIL_REPUTATION_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Email Reputation API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that evaluates the reputation of email addresses by analyzing risk factors to help applications improve deliverability, reduce fraud, and enhance email validation accuracy.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_EMAIL_REPUTATION_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-iban-validation
|
||||
version: "1.0.0"
|
||||
description: Abstract IBAN Validation API — An API that validates IBAN numbers by checking format, bank details
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-iban-validation"
|
||||
- "abstract iban validation"
|
||||
- "iban validation"
|
||||
patterns:
|
||||
- "(?i)abstract.?iban.?validation"
|
||||
tags:
|
||||
- "tools"
|
||||
- "iban-validation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_IBAN_VALIDATION_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract IBAN Validation API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that validates IBAN numbers by checking format, bank details, and country-specific rules to help businesses prevent payment errors, reduce fraud risk, and streamline international transactions.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_IBAN_VALIDATION_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-ip-intelligence
|
||||
version: "1.0.0"
|
||||
description: Abstract IP Intelligence API — An API that provides IP address data including geolocation, ISP
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-ip-intelligence"
|
||||
- "abstract ip intelligence"
|
||||
- "ip intelligence"
|
||||
patterns:
|
||||
- "(?i)abstract.?ip.?intelligence"
|
||||
tags:
|
||||
- "tools"
|
||||
- "ip-intelligence"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_IP_INTELLIGENCE_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract IP Intelligence API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that provides IP address data including geolocation, ISP, proxy and VPN detection, and risk signals to help applications enhance security, prevent fraud, and deliver location-aware experiences.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_IP_INTELLIGENCE_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-phone-intelligence
|
||||
version: "1.0.0"
|
||||
description: Abstract Phone Intelligence API — An API that validates and enriches phone numbers with carrier, location
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-phone-intelligence"
|
||||
- "abstract phone intelligence"
|
||||
- "phone validation"
|
||||
patterns:
|
||||
- "(?i)abstract.?phone.?intelligence"
|
||||
tags:
|
||||
- "tools"
|
||||
- "phone-validation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_PHONE_INTELLIGENCE_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Phone Intelligence API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that validates and enriches phone numbers with carrier, location, and line type data, enabling applications to verify user input, detect fraud risk, and improve communication accuracy globally.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_PHONE_INTELLIGENCE_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-public-holidays
|
||||
version: "1.0.0"
|
||||
description: Abstract Public Holidays API — An API that delivers official public holiday data by country and year
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-public-holidays"
|
||||
- "abstract public holidays"
|
||||
- "public holidays"
|
||||
patterns:
|
||||
- "(?i)abstract.?public.?holidays"
|
||||
tags:
|
||||
- "tools"
|
||||
- "public-holidays"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_PUBLIC_HOLIDAYS_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Public Holidays API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that delivers official public holiday data by country and year, enabling applications to access national and regional holiday calendars for scheduling, localization, and compliance use cases.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_PUBLIC_HOLIDAYS_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abstract-vat-validation
|
||||
version: "1.0.0"
|
||||
description: Abstract Vat Validation API — An API that validates VAT numbers against official registries
|
||||
activation:
|
||||
keywords:
|
||||
- "abstract-vat-validation"
|
||||
- "abstract vat validation"
|
||||
- "vat validation"
|
||||
patterns:
|
||||
- "(?i)abstract.?vat.?validation"
|
||||
tags:
|
||||
- "tools"
|
||||
- "vat-validation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABSTRACT_VAT_VALIDATION_API_KEY]
|
||||
---
|
||||
|
||||
# Abstract Vat Validation API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_key` query parameter.
|
||||
|
||||
> An API that validates VAT numbers against official registries, confirms company details, and helps businesses ensure tax compliance, reduce fraud risk, and automate cross-border invoicing workflows.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_key`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABSTRACT_VAT_VALIDATION_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: abyssale
|
||||
version: "1.0.0"
|
||||
description: Abyssale API — A cloud-based creative automation solution that helps teams design, generate
|
||||
activation:
|
||||
keywords:
|
||||
- "abyssale"
|
||||
- "creative automation platform"
|
||||
patterns:
|
||||
- "(?i)abyssale"
|
||||
tags:
|
||||
- "tools"
|
||||
- "creative-automation-platform"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ABYSSALE_API_KEY]
|
||||
---
|
||||
|
||||
# Abyssale API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `x-api-key` header — **never construct auth headers manually**.
|
||||
|
||||
> A cloud-based creative automation solution that helps teams design, generate, and scale thousands of on-brand visual assets in minutes from a single template, accelerates production through APIs and i
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `x-api-key` header.
|
||||
Format: `x-api-key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ABYSSALE_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,81 @@
|
||||
---
|
||||
name: activecampaign
|
||||
version: "1.0.0"
|
||||
description: ActiveCampaign API — contacts, deals, automations, campaigns, lists
|
||||
activation:
|
||||
keywords:
|
||||
- "activecampaign"
|
||||
- "active campaign"
|
||||
- "marketing automation"
|
||||
exclude_keywords:
|
||||
- "hubspot"
|
||||
- "mailchimp"
|
||||
patterns:
|
||||
- "(?i)active.?campaign.*(contact|deal|automation|campaign)"
|
||||
tags:
|
||||
- "marketing"
|
||||
- "crm"
|
||||
- "automation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ACTIVECAMPAIGN_URL, ACTIVECAMPAIGN_API_KEY]
|
||||
---
|
||||
|
||||
# ActiveCampaign API v3
|
||||
|
||||
Use the `http` tool. Include `Api-Token` header.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://{ACTIVECAMPAIGN_URL}.api-us1.com/api/3`
|
||||
|
||||
## Actions
|
||||
|
||||
**List contacts:**
|
||||
```
|
||||
http(method="GET", url="https://{account}.api-us1.com/api/3/contacts?limit=20", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Search contacts:**
|
||||
```
|
||||
http(method="GET", url="https://{account}.api-us1.com/api/3/[email protected]", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Create contact:**
|
||||
```
|
||||
http(method="POST", url="https://{account}.api-us1.com/api/3/contacts", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}], body={"contact": {"email": "[email protected]", "firstName": "John", "lastName": "Doe", "phone": "+1234567890"}})
|
||||
```
|
||||
|
||||
**Update contact:**
|
||||
```
|
||||
http(method="PUT", url="https://{account}.api-us1.com/api/3/contacts/<contact_id>", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}], body={"contact": {"firstName": "Updated"}})
|
||||
```
|
||||
|
||||
**List deals:**
|
||||
```
|
||||
http(method="GET", url="https://{account}.api-us1.com/api/3/deals?limit=20", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Create deal:**
|
||||
```
|
||||
http(method="POST", url="https://{account}.api-us1.com/api/3/deals", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}], body={"deal": {"title": "New Deal", "value": 5000, "currency": "usd", "contact": "<contact_id>", "group": "<pipeline_id>", "stage": "<stage_id>"}})
|
||||
```
|
||||
|
||||
**Add contact to automation:**
|
||||
```
|
||||
http(method="POST", url="https://{account}.api-us1.com/api/3/contactAutomations", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}], body={"contactAutomation": {"contact": "<contact_id>", "automation": "<automation_id>"}})
|
||||
```
|
||||
|
||||
**List automations:**
|
||||
```
|
||||
http(method="GET", url="https://{account}.api-us1.com/api/3/automations?limit=20", headers=[{"name": "Api-Token", "value": "{ACTIVECAMPAIGN_API_KEY}"}])
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- All request/response bodies wrap data in the resource name: `{"contact": {...}}`, `{"contacts": [...]}`.
|
||||
- Deal values are in cents (integer).
|
||||
- Pagination: `limit` + `offset`. Check `meta.total` for count.
|
||||
- Tags can be added via `/api/3/contactTags` with `{"contactTag": {"contact": "id", "tag": "id"}}`.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: affinity-co
|
||||
version: "1.0.0"
|
||||
description: Affinity.co API — Affinity is a relationship intelligence CRM that automatically captures and anal
|
||||
activation:
|
||||
keywords:
|
||||
- "affinity-co"
|
||||
- "affinity.co"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)affinity.?co"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AFFINITY_CO_API_KEY]
|
||||
---
|
||||
|
||||
# Affinity.co API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
> Affinity is a relationship intelligence CRM that automatically captures and analyzes your team's communication data to surface valuable connections, streamline deal management, and help you close more
|
||||
|
||||
## Authentication
|
||||
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `AFFINITY_CO_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: agent-mail
|
||||
version: "1.0.0"
|
||||
description: AgentMail API — Agent Mail enables developers to give AI agents unique
|
||||
activation:
|
||||
keywords:
|
||||
- "agent-mail"
|
||||
- "agentmail"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)agent.?mail"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AGENT_MAIL_API_KEY]
|
||||
---
|
||||
|
||||
# AgentMail API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Agent Mail enables developers to give AI agents unique, programmable email inboxes that can send, receive, and act on emails at scale—featuring API-first integration, custom domains, and built-in deli
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `AGENT_MAIL_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: agent-ql
|
||||
version: "1.0.0"
|
||||
description: AgentQL API — AgentQL is a natural language interface that allows users to query their data us
|
||||
activation:
|
||||
keywords:
|
||||
- "agent-ql"
|
||||
- "agentql"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)agent.?ql"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AGENTQL_API_KEY]
|
||||
---
|
||||
|
||||
# AgentQL API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-API-Key` header — **never construct auth headers manually**.
|
||||
|
||||
> AgentQL is a natural language interface that allows users to query their data using plain English, enabling seamless interaction with databases and APIs without writing traditional code.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `X-API-Key` header.
|
||||
Format: `X-API-Key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `AGENTQL_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: agiled
|
||||
version: "1.0.0"
|
||||
description: Agiled API — Agiled is an all-in-one business management platform that helps freelancers and
|
||||
activation:
|
||||
keywords:
|
||||
- "agiled"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)agiled"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Agiled API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_token` query parameter.
|
||||
|
||||
> Agiled is an all-in-one business management platform that helps freelancers and small businesses manage CRM, projects, finances, contracts, invoicing and client portals within a unified workspace.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_token`.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
name: ahrefs
|
||||
version: "1.0.0"
|
||||
description: Ahrefs API — Ahrefs is an all-in-one SEO toolset that helps businesses and marketers improve
|
||||
activation:
|
||||
keywords:
|
||||
- "ahrefs"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)ahrefs"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AHREFS_API_KEY]
|
||||
---
|
||||
|
||||
# Ahrefs API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.ahrefs.com/v3`
|
||||
|
||||
## Actions
|
||||
|
||||
**Get domain rating:**
|
||||
```
|
||||
http(method="GET", url="https://api.ahrefs.com/v3/site-explorer/domain-rating?target=example.com&date=2026-03-01")
|
||||
```
|
||||
|
||||
**Get backlinks:**
|
||||
```
|
||||
http(method="GET", url="https://api.ahrefs.com/v3/site-explorer/all-backlinks?target=example.com&limit=10&mode=subdomains")
|
||||
```
|
||||
|
||||
**Get organic keywords:**
|
||||
```
|
||||
http(method="GET", url="https://api.ahrefs.com/v3/site-explorer/organic-keywords?target=example.com&limit=10&country=us")
|
||||
```
|
||||
|
||||
**Get referring domains:**
|
||||
```
|
||||
http(method="GET", url="https://api.ahrefs.com/v3/site-explorer/refdomains?target=example.com&limit=10&mode=subdomains")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- `target` can be a domain, subdomain, or URL.
|
||||
- `mode`: `exact`, `prefix`, `domain`, `subdomains`.
|
||||
- Dates in `YYYY-MM-DD` format.
|
||||
- Results are paginated with `offset` and `limit`.
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
name: airtable
|
||||
version: "1.0.0"
|
||||
description: Airtable API — bases, tables, records, fields, views
|
||||
activation:
|
||||
keywords:
|
||||
- "airtable"
|
||||
- "airtable base"
|
||||
- "airtable record"
|
||||
exclude_keywords:
|
||||
- "google sheets"
|
||||
- "notion"
|
||||
patterns:
|
||||
- "(?i)airtable.*(base|table|record|field)"
|
||||
- "(?i)(create|list|update).*airtable"
|
||||
tags:
|
||||
- "database"
|
||||
- "spreadsheet"
|
||||
- "productivity"
|
||||
max_context_tokens: 1500
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AIRTABLE_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Airtable Web API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.airtable.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.airtable.com/v0`
|
||||
|
||||
## Actions
|
||||
|
||||
**List bases:**
|
||||
```
|
||||
http(method="GET", url="https://api.airtable.com/v0/meta/bases")
|
||||
```
|
||||
|
||||
**List tables in base:**
|
||||
```
|
||||
http(method="GET", url="https://api.airtable.com/v0/meta/bases/<base_id>/tables")
|
||||
```
|
||||
|
||||
**List records:**
|
||||
```
|
||||
http(method="GET", url="https://api.airtable.com/v0/<base_id>/<table_name>?maxRecords=20&view=Grid%20view")
|
||||
```
|
||||
|
||||
**List with filter:**
|
||||
```
|
||||
http(method="GET", url="https://api.airtable.com/v0/<base_id>/<table_name>?filterByFormula={Status}='Active'&sort[0][field]=Name&sort[0][direction]=asc&maxRecords=20")
|
||||
```
|
||||
|
||||
**Get record:**
|
||||
```
|
||||
http(method="GET", url="https://api.airtable.com/v0/<base_id>/<table_name>/<record_id>")
|
||||
```
|
||||
|
||||
**Create records:**
|
||||
```
|
||||
http(method="POST", url="https://api.airtable.com/v0/<base_id>/<table_name>", body={"records": [{"fields": {"Name": "Alice", "Email": "[email protected]", "Status": "Active"}}]})
|
||||
```
|
||||
|
||||
**Update records:**
|
||||
```
|
||||
http(method="PATCH", url="https://api.airtable.com/v0/<base_id>/<table_name>", body={"records": [{"id": "<record_id>", "fields": {"Status": "Done"}}]})
|
||||
```
|
||||
|
||||
**Delete records:**
|
||||
```
|
||||
http(method="DELETE", url="https://api.airtable.com/v0/<base_id>/<table_name>?records[]=<record_id1>&records[]=<record_id2>")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Base IDs start with `app`, table IDs with `tbl`, record IDs with `rec`.
|
||||
- Table name in URL must be URL-encoded if it contains spaces.
|
||||
- `filterByFormula` uses Airtable formula syntax: `{Field Name}='value'`, `AND(...)`, `OR(...)`.
|
||||
- Create/update accept up to 10 records per request.
|
||||
- Pagination: use `offset` from response. When absent, no more records.
|
||||
- Rate limit: 5 requests/second per base.
|
||||
- Field names are case-sensitive and must match exactly.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: alt-text-ai
|
||||
version: "1.0.0"
|
||||
description: AltText AI API — An AI-driven service that automatically analyzes images and generates descriptiv
|
||||
activation:
|
||||
keywords:
|
||||
- "alt-text-ai"
|
||||
- "alttext ai"
|
||||
- "generation tool"
|
||||
patterns:
|
||||
- "(?i)alt.?text.?ai"
|
||||
tags:
|
||||
- "tools"
|
||||
- "generation-tool"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ALT_TEXT_AI_API_KEY]
|
||||
---
|
||||
|
||||
# AltText AI API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-API-Key` header — **never construct auth headers manually**.
|
||||
|
||||
> An AI-driven service that automatically analyzes images and generates descriptive, SEO-friendly alt text to improve website accessibility, enhance search visibility across languages, and streamline im
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `X-API-Key` header.
|
||||
Format: `X-API-Key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ALT_TEXT_AI_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: amazon-ads
|
||||
version: "1.0.0"
|
||||
description: Amazon Ads API — Amazon Ads is an advertising platform that enables brands to promote their produ
|
||||
activation:
|
||||
keywords:
|
||||
- "amazon-ads"
|
||||
- "amazon ads"
|
||||
- "marketing"
|
||||
patterns:
|
||||
- "(?i)amazon.?ads"
|
||||
tags:
|
||||
- "marketing"
|
||||
- "email"
|
||||
- "campaigns"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Amazon Ads API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Amazon Ads is an advertising platform that enables brands to promote their products across Amazon’s ecosystem, helping them reach shoppers through targeted ads, sponsored listings, and display campaig
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: anchor-browser
|
||||
version: "1.0.0"
|
||||
description: Anchor Browser API — Anchor Browser is a cloud-hosted automation platform that lets AI agents interac
|
||||
activation:
|
||||
keywords:
|
||||
- "anchor-browser"
|
||||
- "anchor browser"
|
||||
- "web automation"
|
||||
patterns:
|
||||
- "(?i)anchor.?browser"
|
||||
tags:
|
||||
- "tools"
|
||||
- "web-automation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ANCHOR_BROWSER_API_KEY]
|
||||
---
|
||||
|
||||
# Anchor Browser API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `anchor-api-key` header — **never construct auth headers manually**.
|
||||
|
||||
> Anchor Browser is a cloud-hosted automation platform that lets AI agents interact with web pages like a human—navigating sites, clicking, typing, submitting forms and extracting data—so teams can auto
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `anchor-api-key` header.
|
||||
Format: `anchor-api-key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ANCHOR_BROWSER_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: anthropic-admin
|
||||
version: "1.0.0"
|
||||
description: Anthropic Admin API — Anthropic Admin provides administrative tools for managing access, API keys
|
||||
activation:
|
||||
keywords:
|
||||
- "anthropic-admin"
|
||||
- "anthropic admin"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)anthropic.?admin"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ANTHROPIC_ADMIN_API_KEY]
|
||||
---
|
||||
|
||||
# Anthropic Admin API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-Api-Key` header — **never construct auth headers manually**.
|
||||
|
||||
> Anthropic Admin provides administrative tools for managing access, API keys, usage, billing, and organizational settings for applications built with Claude AI models, allowing teams to control permiss
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `X-Api-Key` header.
|
||||
Format: `X-Api-Key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `ANTHROPIC_ADMIN_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
name: anthropic
|
||||
version: "1.0.0"
|
||||
description: Anthropic API — Anthropic is an AI safety and research company focused on building reliable
|
||||
activation:
|
||||
keywords:
|
||||
- "anthropic"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)anthropic"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ANTHROPIC_API_KEY]
|
||||
---
|
||||
|
||||
# Anthropic API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `x-api-key` header — **never construct auth headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.anthropic.com/v1`
|
||||
|
||||
**Required headers**: `x-api-key: {ANTHROPIC_API_KEY}`, `anthropic-version: 2023-06-01`
|
||||
|
||||
## Actions
|
||||
|
||||
**Create message:**
|
||||
```
|
||||
http(method="POST", url="https://api.anthropic.com/v1/messages", headers=[{"name": "x-api-key","value": "{ANTHROPIC_API_KEY}"},{"name": "anthropic-version","value": "2023-06-01"}], body={"model": "claude-sonnet-4-20250514","max_tokens": 1024,"messages": [{"role": "user","content": "Hello"}]})
|
||||
```
|
||||
|
||||
**Create message with system prompt:**
|
||||
```
|
||||
http(method="POST", url="https://api.anthropic.com/v1/messages", headers=[{"name": "x-api-key","value": "{ANTHROPIC_API_KEY}"},{"name": "anthropic-version","value": "2023-06-01"}], body={"model": "claude-sonnet-4-20250514","max_tokens": 1024,"system": "You are a helpful assistant.","messages": [{"role": "user","content": "Explain quantum computing"}]})
|
||||
```
|
||||
|
||||
**List models:**
|
||||
```
|
||||
http(method="GET", url="https://api.anthropic.com/v1/models")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Always include `anthropic-version: 2023-06-01` header.
|
||||
- Models: `claude-sonnet-4-20250514`, `claude-haiku-4-5-20251001`, `claude-opus-4-20250514`.
|
||||
- Max tokens is required for all message requests.
|
||||
- Streaming: set `stream: true` in body.
|
||||
@@ -0,0 +1,55 @@
|
||||
---
|
||||
name: apify
|
||||
version: "1.0.0"
|
||||
description: Apify API — Apify is a full‑stack web scraping and browser automation platform where develop
|
||||
activation:
|
||||
keywords:
|
||||
- "apify"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)apify"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [APIFY_API_KEY]
|
||||
---
|
||||
|
||||
# Apify API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.apify.com/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List actors:**
|
||||
```
|
||||
http(method="GET", url="https://api.apify.com/v2/acts?limit=10")
|
||||
```
|
||||
|
||||
**Run actor:**
|
||||
```
|
||||
http(method="POST", url="https://api.apify.com/v2/acts/{actor_id}/runs", body={"memory": 256,"timeout": 60})
|
||||
```
|
||||
|
||||
**Get run details:**
|
||||
```
|
||||
http(method="GET", url="https://api.apify.com/v2/acts/{actor_id}/runs/{run_id}")
|
||||
```
|
||||
|
||||
**Get dataset items:**
|
||||
```
|
||||
http(method="GET", url="https://api.apify.com/v2/datasets/{dataset_id}/items?limit=100")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Actor IDs look like `username~actor-name` or a hash.
|
||||
- Run status: `READY`, `RUNNING`, `SUCCEEDED`, `FAILED`, `TIMED-OUT`, `ABORTED`.
|
||||
- Default dataset is created per run; check `defaultDatasetId` in run details.
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
name: apollo
|
||||
version: "1.0.0"
|
||||
description: Apollo API — Apollo is a sales intelligence and engagement platform that helps teams find and
|
||||
activation:
|
||||
keywords:
|
||||
- "apollo"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)apollo"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Apollo API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.apollo.io/api/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**Search people:**
|
||||
```
|
||||
http(method="POST", url="https://api.apollo.io/api/v1/mixed_people/search", body={"person_titles": ["CEO"],"person_locations": ["San Francisco"],"page": 1,"per_page": 10})
|
||||
```
|
||||
|
||||
**Search organizations:**
|
||||
```
|
||||
http(method="POST", url="https://api.apollo.io/api/v1/mixed_companies/search", body={"organization_locations": ["United States"],"page": 1,"per_page": 10})
|
||||
```
|
||||
|
||||
**Get person:**
|
||||
```
|
||||
http(method="GET", url="https://api.apollo.io/api/v1/people/{person_id}")
|
||||
```
|
||||
|
||||
**Enrich person:**
|
||||
```
|
||||
http(method="POST", url="https://api.apollo.io/api/v1/people/match", body={"email": "[email protected]"})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- API key goes in the request body as `api_key` or as a header.
|
||||
- Search supports filters: `person_titles`, `person_locations`, `organization_domains`.
|
||||
- Rate limit: 50 requests per minute on free tier.
|
||||
@@ -0,0 +1,87 @@
|
||||
---
|
||||
name: asana
|
||||
version: "1.0.0"
|
||||
description: Asana REST API — tasks, projects, sections, comments, search
|
||||
activation:
|
||||
keywords:
|
||||
- "asana"
|
||||
- "asana task"
|
||||
- "asana project"
|
||||
exclude_keywords:
|
||||
- "jira"
|
||||
- "trello"
|
||||
patterns:
|
||||
- "(?i)asana.*(task|project|section)"
|
||||
- "(?i)(create|list|update|complete).*asana"
|
||||
tags:
|
||||
- "project-management"
|
||||
- "task-management"
|
||||
max_context_tokens: 1500
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ASANA_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Asana REST API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `app.asana.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://app.asana.com/api/1.0`
|
||||
|
||||
## Actions
|
||||
|
||||
**List my tasks:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/user_task_lists/me/tasks?workspace=<workspace_gid>&opt_fields=name,completed,due_on,assignee_section.name&limit=20")
|
||||
```
|
||||
|
||||
**Get task:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/tasks/<task_gid>?opt_fields=name,notes,completed,due_on,assignee.name,projects.name,tags.name")
|
||||
```
|
||||
|
||||
**Create task:**
|
||||
```
|
||||
http(method="POST", url="https://app.asana.com/api/1.0/tasks", body={"data": {"name": "Task title", "notes": "Description", "projects": ["<project_gid>"], "due_on": "2026-04-01", "assignee": "me"}})
|
||||
```
|
||||
|
||||
**Update task:**
|
||||
```
|
||||
http(method="PUT", url="https://app.asana.com/api/1.0/tasks/<task_gid>", body={"data": {"completed": true}})
|
||||
```
|
||||
|
||||
**List project tasks:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/projects/<project_gid>/tasks?opt_fields=name,completed,due_on,assignee.name&limit=50")
|
||||
```
|
||||
|
||||
**Add comment:**
|
||||
```
|
||||
http(method="POST", url="https://app.asana.com/api/1.0/tasks/<task_gid>/stories", body={"data": {"text": "Comment text"}})
|
||||
```
|
||||
|
||||
**Search tasks:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/workspaces/<workspace_gid>/tasks/search?text=search+term&opt_fields=name,completed&limit=20")
|
||||
```
|
||||
|
||||
**List projects:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/projects?workspace=<workspace_gid>&opt_fields=name,current_status&limit=50")
|
||||
```
|
||||
|
||||
**List workspaces:**
|
||||
```
|
||||
http(method="GET", url="https://app.asana.com/api/1.0/workspaces")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- All response data is wrapped in `{"data": ...}`. Errors: `{"errors": [{"message": "..."}]}`.
|
||||
- Use `opt_fields` to request specific fields (comma-separated). Without it, you get minimal data.
|
||||
- GIDs are numeric strings like `"1234567890123456"`.
|
||||
- Dates are ISO format `YYYY-MM-DD`. Due times use `due_at` (ISO 8601 with timezone).
|
||||
- Pagination: `offset` token from `next_page.offset`. Check `next_page` for more.
|
||||
@@ -0,0 +1,58 @@
|
||||
---
|
||||
name: attio
|
||||
version: "1.0.0"
|
||||
description: Attio API — Attio is a modern CRM platform that offers fully customizable workspaces
|
||||
activation:
|
||||
keywords:
|
||||
- "attio"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)attio"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Attio API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.attio.com/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List records:**
|
||||
```
|
||||
http(method="POST", url="https://api.attio.com/v2/objects/{object_slug}/records/query", body={"limit": 20})
|
||||
```
|
||||
|
||||
**Get record:**
|
||||
```
|
||||
http(method="GET", url="https://api.attio.com/v2/objects/{object_slug}/records/{record_id}")
|
||||
```
|
||||
|
||||
**Create record:**
|
||||
```
|
||||
http(method="POST", url="https://api.attio.com/v2/objects/{object_slug}/records", body={"data": {"values": {"name": [{"value": "Acme Corp"}]}}})
|
||||
```
|
||||
|
||||
**List objects:**
|
||||
```
|
||||
http(method="GET", url="https://api.attio.com/v2/objects")
|
||||
```
|
||||
|
||||
**List lists:**
|
||||
```
|
||||
http(method="GET", url="https://api.attio.com/v2/lists")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Standard objects: `companies`, `people`, `deals`.
|
||||
- Values are arrays of typed entries: `[{"value": "..."}]`.
|
||||
- Use `/objects/{slug}/records/query` with filters for searching.
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
name: auth0-management
|
||||
version: "1.0.0"
|
||||
description: Auth0 Management API — Auth0 delivers a flexible, drop-in authentication and authorization platform tha
|
||||
activation:
|
||||
keywords:
|
||||
- "auth0-management"
|
||||
- "auth0 management"
|
||||
- "authentication"
|
||||
patterns:
|
||||
- "(?i)auth0.?management"
|
||||
tags:
|
||||
- "tools"
|
||||
- "authentication"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AUTH0_API_TOKEN, AUTH0_MANAGEMENT_TENANT_DOMAIN]
|
||||
---
|
||||
|
||||
# Auth0 Management API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://{AUTH0_DOMAIN}/api/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List users:**
|
||||
```
|
||||
http(method="GET", url="https://{AUTH0_DOMAIN}/api/v2/users?page=0&per_page=10")
|
||||
```
|
||||
|
||||
**Get user:**
|
||||
```
|
||||
http(method="GET", url="https://{AUTH0_DOMAIN}/api/v2/users/{user_id}")
|
||||
```
|
||||
|
||||
**Create user:**
|
||||
```
|
||||
http(method="POST", url="https://{AUTH0_DOMAIN}/api/v2/users", body={"email": "[email protected]","password": "SecureP@ss1","connection": "Username-Password-Authentication"})
|
||||
```
|
||||
|
||||
**Update user:**
|
||||
```
|
||||
http(method="PATCH", url="https://{AUTH0_DOMAIN}/api/v2/users/{user_id}", body={"name": "John Doe"})
|
||||
```
|
||||
|
||||
**List roles:**
|
||||
```
|
||||
http(method="GET", url="https://{AUTH0_DOMAIN}/api/v2/roles")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- `user_id` is URL-encoded: `auth0|abc123` → `auth0%7Cabc123`.
|
||||
- Connections: `Username-Password-Authentication`, `google-oauth2`, etc.
|
||||
- Use `q` param for Lucene query syntax search: `?q=email:"*@acme.com"`.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: autodesk
|
||||
version: "1.0.0"
|
||||
description: Autodesk API — Autodesk is a global leader in design and engineering software
|
||||
activation:
|
||||
keywords:
|
||||
- "autodesk"
|
||||
- "software"
|
||||
patterns:
|
||||
- "(?i)autodesk"
|
||||
tags:
|
||||
- "software"
|
||||
- "development"
|
||||
- "tools"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Autodesk API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Autodesk is a global leader in design and engineering software, offering a cloud‑connected Design and Make Platform—including AutoCAD, Revit, Fusion 360, and Autodesk Platform Services—that connects d
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: ayrshare
|
||||
version: "1.0.0"
|
||||
description: Ayrshare API — Ayrshare provides a unified REST-based social media API that lets developers pro
|
||||
activation:
|
||||
keywords:
|
||||
- "ayrshare"
|
||||
- "social media"
|
||||
patterns:
|
||||
- "(?i)ayrshare"
|
||||
tags:
|
||||
- "social-media"
|
||||
- "social"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [AYRSHARE_API_KEY]
|
||||
---
|
||||
|
||||
# Ayrshare API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> Ayrshare provides a unified REST-based social media API that lets developers programmatically post, schedule, delete, and analyze content across 13 major networks, manage comments and messages, and au
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Bearer ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `AYRSHARE_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: basin
|
||||
version: "1.0.0"
|
||||
description: Basin API — Basin is a form backend service that captures form submissions from static sites
|
||||
activation:
|
||||
keywords:
|
||||
- "basin"
|
||||
- "workflow automation"
|
||||
patterns:
|
||||
- "(?i)basin"
|
||||
tags:
|
||||
- "tools"
|
||||
- "workflow-automation"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BASIN_API_KEY]
|
||||
---
|
||||
|
||||
# Basin API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `api_token` query parameter.
|
||||
|
||||
> Basin is a form backend service that captures form submissions from static sites and forwards data to email, webhooks or integrations—enabling developers to handle form data without building a custom
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `api_token`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BASIN_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,55 @@
|
||||
---
|
||||
name: beehiiv
|
||||
version: "1.0.0"
|
||||
description: Beehiiv API — Beehiiv is a newsletter platform designed for creators and publishers to grow
|
||||
activation:
|
||||
keywords:
|
||||
- "beehiiv"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)beehiiv"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BEEHIIV_API_KEY]
|
||||
---
|
||||
|
||||
# Beehiiv API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.beehiiv.com/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List publications:**
|
||||
```
|
||||
http(method="GET", url="https://api.beehiiv.com/v2/publications")
|
||||
```
|
||||
|
||||
**List subscribers:**
|
||||
```
|
||||
http(method="GET", url="https://api.beehiiv.com/v2/publications/{pub_id}/subscriptions?limit=10")
|
||||
```
|
||||
|
||||
**Create subscriber:**
|
||||
```
|
||||
http(method="POST", url="https://api.beehiiv.com/v2/publications/{pub_id}/subscriptions", body={"email": "[email protected]","reactivate_existing": true})
|
||||
```
|
||||
|
||||
**List posts:**
|
||||
```
|
||||
http(method="GET", url="https://api.beehiiv.com/v2/publications/{pub_id}/posts?status=confirmed&limit=10")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Publication IDs start with `pub_`.
|
||||
- Post status: `draft`, `confirmed` (published), `archived`.
|
||||
- Subscriber status: `active`, `inactive`, `validating`.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: benchmark-email
|
||||
version: "1.0.0"
|
||||
description: Benchmark Email API — Benchmark Email is an intuitive email-marketing platform that enables marketers
|
||||
activation:
|
||||
keywords:
|
||||
- "benchmark-email"
|
||||
- "benchmark email"
|
||||
- "marketing"
|
||||
patterns:
|
||||
- "(?i)benchmark.?email"
|
||||
tags:
|
||||
- "marketing"
|
||||
- "email"
|
||||
- "campaigns"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BENCHMARK_EMAIL_AUTH_TOKEN]
|
||||
---
|
||||
|
||||
# Benchmark Email API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `AuthToken` header — **never construct auth headers manually**.
|
||||
|
||||
> Benchmark Email is an intuitive email-marketing platform that enables marketers to design mobile-responsive campaigns with drag-and-drop ease, segment contacts for targeted sends, and track real-time
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `AuthToken` header.
|
||||
Format: `AuthToken: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BENCHMARK_EMAIL_AUTH_TOKEN` — Auth Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: benzinga
|
||||
version: "1.0.0"
|
||||
description: Benzinga API — A real-time financial news and market data service that delivers breaking market
|
||||
activation:
|
||||
keywords:
|
||||
- "benzinga"
|
||||
- "financial data"
|
||||
patterns:
|
||||
- "(?i)benzinga"
|
||||
tags:
|
||||
- "tools"
|
||||
- "financial-data"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BENZINGA_API_KEY]
|
||||
---
|
||||
|
||||
# Benzinga API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `token` query parameter.
|
||||
|
||||
> A real-time financial news and market data service that delivers breaking market updates, analysis, earnings, and trading insights to investors, traders, and finance professionals.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `token`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BENZINGA_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: better-proposals
|
||||
version: "1.0.0"
|
||||
description: Better Proposals API — A web-based platform that enables businesses to create, customize, send
|
||||
activation:
|
||||
keywords:
|
||||
- "better-proposals"
|
||||
- "better proposals"
|
||||
- "proposal software"
|
||||
patterns:
|
||||
- "(?i)better.?proposals"
|
||||
tags:
|
||||
- "tools"
|
||||
- "proposal-software"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BETTER_PROPOSALS_API_TOKEN]
|
||||
---
|
||||
|
||||
# Better Proposals API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Bptoken` header — **never construct auth headers manually**.
|
||||
|
||||
> A web-based platform that enables businesses to create, customize, send, and track professional sales proposals and contracts with interactive elements, e-signatures, and analytics to streamline clien
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Bptoken` header.
|
||||
Format: `Bptoken: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BETTER_PROPOSALS_API_TOKEN` — API Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
name: big-commerce
|
||||
version: "1.0.0"
|
||||
description: BigCommerce API — BigCommerce is an open SaaS eCommerce platform that enables businesses to build
|
||||
activation:
|
||||
keywords:
|
||||
- "big-commerce"
|
||||
- "bigcommerce"
|
||||
- "ecommerce"
|
||||
patterns:
|
||||
- "(?i)big.?commerce"
|
||||
tags:
|
||||
- "tools"
|
||||
- "ecommerce"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BIG_COMMERCE_STORE_HASH, BIG_COMMERCE_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# BigCommerce API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-Auth-Token` header — **never construct auth headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3`
|
||||
|
||||
## Actions
|
||||
|
||||
**List products:**
|
||||
```
|
||||
http(method="GET", url="https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3/catalog/products?limit=10")
|
||||
```
|
||||
|
||||
**Get product:**
|
||||
```
|
||||
http(method="GET", url="https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3/catalog/products/{product_id}")
|
||||
```
|
||||
|
||||
**Create product:**
|
||||
```
|
||||
http(method="POST", url="https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3/catalog/products", body={"name": "Widget","type": "physical","weight": 1.0,"price": 29.99})
|
||||
```
|
||||
|
||||
**List orders:**
|
||||
```
|
||||
http(method="GET", url="https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3/orders?limit=10")
|
||||
```
|
||||
|
||||
**List customers:**
|
||||
```
|
||||
http(method="GET", url="https://api.bigcommerce.com/stores/{BIGCOMMERCE_STORE_HASH}/v3/customers?limit=10")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Auth via `X-Auth-Token` header (auto-injected).
|
||||
- Products have `type`: `physical`, `digital`.
|
||||
- Prices are decimals, weights in the store's configured unit.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
name: bigquery
|
||||
version: "1.0.0"
|
||||
description: BigQuery API — BigQuery is a serverless, highly scalable
|
||||
activation:
|
||||
keywords:
|
||||
- "bigquery"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)bigquery"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# BigQuery API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://bigquery.googleapis.com/bigquery/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List datasets:**
|
||||
```
|
||||
http(method="GET", url="https://bigquery.googleapis.com/bigquery/v2/projects/{project_id}/datasets")
|
||||
```
|
||||
|
||||
**List tables:**
|
||||
```
|
||||
http(method="GET", url="https://bigquery.googleapis.com/bigquery/v2/projects/{project_id}/datasets/{dataset_id}/tables")
|
||||
```
|
||||
|
||||
**Run query:**
|
||||
```
|
||||
http(method="POST", url="https://bigquery.googleapis.com/bigquery/v2/projects/{project_id}/queries", body={"query": "SELECT * FROM `project.dataset.table` LIMIT 10","useLegacySql": false})
|
||||
```
|
||||
|
||||
**Get query results:**
|
||||
```
|
||||
http(method="GET", url="https://bigquery.googleapis.com/bigquery/v2/projects/{project_id}/queries/{job_id}")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses OAuth 2.0 — credentials are auto-injected.
|
||||
- Queries use Standard SQL by default (`useLegacySql: false`).
|
||||
- Large results: check `jobComplete` field; poll with `getQueryResults` if `false`.
|
||||
- Table references: `project.dataset.table`.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: blaze-meter-functional
|
||||
version: "1.0.0"
|
||||
description: BlazeMeter Functional API — BlazeMeter is a testing platform for web and API applications
|
||||
activation:
|
||||
keywords:
|
||||
- "blaze-meter-functional"
|
||||
- "blazemeter functional"
|
||||
- "developer tool"
|
||||
patterns:
|
||||
- "(?i)blaze.?meter.?functional"
|
||||
tags:
|
||||
- "tools"
|
||||
- "developer-tool"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BLAZE_METER_FUNCTIONAL_API_KEY, BLAZE_METER_FUNCTIONAL_API_SECRET, BLAZE_METER_ACCOUNT_ID]
|
||||
---
|
||||
|
||||
# BlazeMeter Functional API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
> BlazeMeter is a testing platform for web and API applications, and its Functional API enables developers to programmatically create, manage, and run automated API tests to validate responses, workflow
|
||||
|
||||
## Authentication
|
||||
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BLAZE_METER_FUNCTIONAL_API_KEY` — API Key
|
||||
- `BLAZE_METER_FUNCTIONAL_API_SECRET` — API Secret
|
||||
- `BLAZE_METER_ACCOUNT_ID` — Account ID
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: blaze-meter-performance
|
||||
version: "1.0.0"
|
||||
description: BlazeMeter Performance API — BlazeMeter is a testing platform for web and API applications
|
||||
activation:
|
||||
keywords:
|
||||
- "blaze-meter-performance"
|
||||
- "blazemeter performance"
|
||||
- "developer tool"
|
||||
patterns:
|
||||
- "(?i)blaze.?meter.?performance"
|
||||
tags:
|
||||
- "tools"
|
||||
- "developer-tool"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BLAZE_METER_PERFORMANCE_API_KEY, BLAZE_METER_PERFORMANCE_API_SECRET]
|
||||
---
|
||||
|
||||
# BlazeMeter Performance API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
> BlazeMeter is a testing platform for web and API applications, and its Performance API enables developers to programmatically create, configure, run, and retrieve results from large-scale performance
|
||||
|
||||
## Authentication
|
||||
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BLAZE_METER_PERFORMANCE_API_KEY` — API Key
|
||||
- `BLAZE_METER_PERFORMANCE_API_SECRET` — API Secret
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: blaze-meter-service-virtualization
|
||||
version: "1.0.0"
|
||||
description: BlazeMeter Service Virtualization API — BlazeMeter is a testing platform for web and API applications
|
||||
activation:
|
||||
keywords:
|
||||
- "blaze-meter-service-virtualization"
|
||||
- "blazemeter service virtualization"
|
||||
- "developer tool"
|
||||
patterns:
|
||||
- "(?i)blaze.?meter.?service.?virtualization"
|
||||
tags:
|
||||
- "tools"
|
||||
- "developer-tool"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BLAZE_METER_SERVICE_VIRTUALIZATION_API_KEY, BLAZE_METER_SERVICE_VIRTUALIZATION_API_SECRET]
|
||||
---
|
||||
|
||||
# BlazeMeter Service Virtualization API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
> BlazeMeter is a testing platform for web and API applications, and its Service Virtualization API enables developers to programmatically create and manage virtual services that simulate APIs and syste
|
||||
|
||||
## Authentication
|
||||
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BLAZE_METER_SERVICE_VIRTUALIZATION_API_KEY` — API Key
|
||||
- `BLAZE_METER_SERVICE_VIRTUALIZATION_API_SECRET` — API Secret
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: bluebeam
|
||||
version: "1.0.0"
|
||||
description: Bluebeam API — Bluebeam is a PDF-centric collaboration platform tailored for architecture
|
||||
activation:
|
||||
keywords:
|
||||
- "bluebeam"
|
||||
- "software"
|
||||
patterns:
|
||||
- "(?i)bluebeam"
|
||||
tags:
|
||||
- "software"
|
||||
- "development"
|
||||
- "tools"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Bluebeam API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Bluebeam is a PDF-centric collaboration platform tailored for architecture, engineering, and construction professionals, offering industry-grade markup, measurement, takeoff, and document management t
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
name: bluesky
|
||||
version: "1.0.0"
|
||||
description: Bluesky API — Bluesky is a decentralized social media platform built on the open-source AT Pro
|
||||
activation:
|
||||
keywords:
|
||||
- "bluesky"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)bluesky"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BLUESKY_ACCESS_TOKEN, BLUESKY_ENTRYWAY]
|
||||
---
|
||||
|
||||
# Bluesky API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://bsky.social/xrpc`
|
||||
|
||||
## Actions
|
||||
|
||||
**Create session (login):**
|
||||
```
|
||||
http(method="POST", url="https://bsky.social/xrpc/com.atproto.server.createSession", body={"identifier": "your.handle","password": "app-password"})
|
||||
```
|
||||
|
||||
**Create post:**
|
||||
```
|
||||
http(method="POST", url="https://bsky.social/xrpc/com.atproto.repo.createRecord", body={"repo": "did:plc:xxx","collection": "app.bsky.feed.post","record": {"text": "Hello Bluesky!","$type": "app.bsky.feed.post","createdAt": "2026-03-27T00:00:00Z"}})
|
||||
```
|
||||
|
||||
**Get profile:**
|
||||
```
|
||||
http(method="GET", url="https://bsky.social/xrpc/app.bsky.actor.getProfile?actor=your.handle")
|
||||
```
|
||||
|
||||
**Get timeline:**
|
||||
```
|
||||
http(method="GET", url="https://bsky.social/xrpc/app.bsky.feed.getTimeline?limit=20")
|
||||
```
|
||||
|
||||
**Search posts:**
|
||||
```
|
||||
http(method="GET", url="https://bsky.social/xrpc/app.bsky.feed.searchPosts?q=search+term&limit=10")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- First create a session to get an access token.
|
||||
- Posts are AT Protocol records in collection `app.bsky.feed.post`.
|
||||
- Handles look like `username.bsky.social` or custom domains.
|
||||
- DIDs are persistent identifiers: `did:plc:xxxxx`.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: bookingmood
|
||||
version: "1.0.0"
|
||||
description: Bookingmood API — A flexible booking platform that lets rental and vacation property owners embed
|
||||
activation:
|
||||
keywords:
|
||||
- "bookingmood"
|
||||
- "booking software"
|
||||
patterns:
|
||||
- "(?i)bookingmood"
|
||||
tags:
|
||||
- "tools"
|
||||
- "booking-software"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BOOKINGMOOD_API_KEY]
|
||||
---
|
||||
|
||||
# Bookingmood API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> A flexible booking platform that lets rental and vacation property owners embed customizable calendars on their websites, manage availability and reservations, track payments, sync with external calen
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BOOKINGMOOD_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: bot-star
|
||||
version: "1.0.0"
|
||||
description: BotStar API — A visual bot-building platform that enables businesses to design, deploy
|
||||
activation:
|
||||
keywords:
|
||||
- "bot-star"
|
||||
- "botstar"
|
||||
- "chatbot builder"
|
||||
patterns:
|
||||
- "(?i)bot.?star"
|
||||
tags:
|
||||
- "tools"
|
||||
- "chatbot-builder"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BOT_STAR_API_TOKEN]
|
||||
---
|
||||
|
||||
# BotStar API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> A visual bot-building platform that enables businesses to design, deploy, and manage AI-powered chatbots for websites, messaging apps, and customer support workflows without coding.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BOT_STAR_API_TOKEN` — API Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: bouncer
|
||||
version: "1.0.0"
|
||||
description: Bouncer API — A cloud-based platform that verifies and cleans email lists by identifying inval
|
||||
activation:
|
||||
keywords:
|
||||
- "bouncer"
|
||||
- "email verification"
|
||||
patterns:
|
||||
- "(?i)bouncer"
|
||||
tags:
|
||||
- "tools"
|
||||
- "email-verification"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BOUNCER_API_KEY]
|
||||
---
|
||||
|
||||
# Bouncer API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `x-api-key` header — **never construct auth headers manually**.
|
||||
|
||||
> A cloud-based platform that verifies and cleans email lists by identifying invalid, risky, or disposable email addresses to improve deliverability, reduce bounce rates, and enhance email campaign perf
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `x-api-key` header.
|
||||
Format: `x-api-key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BOUNCER_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: box-hero
|
||||
version: "1.0.0"
|
||||
description: BoxHero API — A cloud-based inventory and stock management platform that enables businesses to
|
||||
activation:
|
||||
keywords:
|
||||
- "box-hero"
|
||||
- "boxhero"
|
||||
- "inventory management"
|
||||
patterns:
|
||||
- "(?i)box.?hero"
|
||||
tags:
|
||||
- "tools"
|
||||
- "inventory-management"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BOX_HERO_API_TOKEN]
|
||||
---
|
||||
|
||||
# BoxHero API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> A cloud-based inventory and stock management platform that enables businesses to track products, manage warehouses, monitor stock levels in real time, and automate order fulfillment across sales chann
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BOX_HERO_API_TOKEN` — API Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
name: box
|
||||
version: "1.0.0"
|
||||
description: Box API — files, folders, collaborations, search, comments
|
||||
activation:
|
||||
keywords:
|
||||
- "box"
|
||||
- "box.com"
|
||||
- "box file"
|
||||
exclude_keywords:
|
||||
- "dropbox"
|
||||
- "google drive"
|
||||
patterns:
|
||||
- "(?i)box\\.com.*(file|folder|share)"
|
||||
- "(?i)(upload|download|share).*box"
|
||||
tags:
|
||||
- "file-storage"
|
||||
- "cloud-storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BOX_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Box Content API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.box.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.box.com/2.0`
|
||||
|
||||
## Actions
|
||||
|
||||
**Get folder items:**
|
||||
```
|
||||
http(method="GET", url="https://api.box.com/2.0/folders/<folder_id>/items?fields=id,name,type,modified_at,size&limit=20")
|
||||
```
|
||||
Root folder ID is `"0"`.
|
||||
|
||||
**Get file info:**
|
||||
```
|
||||
http(method="GET", url="https://api.box.com/2.0/files/<file_id>?fields=id,name,size,modified_at,shared_link")
|
||||
```
|
||||
|
||||
**Search:**
|
||||
```
|
||||
http(method="GET", url="https://api.box.com/2.0/search?query=report&type=file&limit=20")
|
||||
```
|
||||
|
||||
**Create folder:**
|
||||
```
|
||||
http(method="POST", url="https://api.box.com/2.0/folders", body={"name": "New Folder", "parent": {"id": "0"}})
|
||||
```
|
||||
|
||||
**Copy file:**
|
||||
```
|
||||
http(method="POST", url="https://api.box.com/2.0/files/<file_id>/copy", body={"parent": {"id": "<folder_id>"}})
|
||||
```
|
||||
|
||||
**Create shared link:**
|
||||
```
|
||||
http(method="PUT", url="https://api.box.com/2.0/files/<file_id>?fields=shared_link", body={"shared_link": {"access": "open"}})
|
||||
```
|
||||
|
||||
**Add collaboration:**
|
||||
```
|
||||
http(method="POST", url="https://api.box.com/2.0/collaborations", body={"item": {"type": "folder", "id": "<folder_id>"}, "accessible_by": {"type": "user", "login": "[email protected]"}, "role": "editor"})
|
||||
```
|
||||
|
||||
**Add comment:**
|
||||
```
|
||||
http(method="POST", url="https://api.box.com/2.0/comments", body={"item": {"type": "file", "id": "<file_id>"}, "message": "Please review"})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Root folder is always `"0"`.
|
||||
- Collaboration roles: `editor`, `viewer`, `previewer`, `uploader`, `co-owner`.
|
||||
- Shared link access: `open` (anyone), `company` (organization), `collaborators` (invited only).
|
||||
- Use `fields` param to request specific properties.
|
||||
- Pagination: `offset` + `limit`. Check `total_count`.
|
||||
- File uploads use `https://upload.box.com/api/2.0/files/content` (different host).
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: breathe
|
||||
version: "1.0.0"
|
||||
description: Breathe API — Breathe is a cloud-based HR software designed for small and medium-sized busines
|
||||
activation:
|
||||
keywords:
|
||||
- "breathe"
|
||||
- "hris"
|
||||
patterns:
|
||||
- "(?i)breathe"
|
||||
tags:
|
||||
- "tools"
|
||||
- "hris"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BREATHE_API_KEY]
|
||||
---
|
||||
|
||||
# Breathe API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-API-KEY` header — **never construct auth headers manually**.
|
||||
|
||||
> Breathe is a cloud-based HR software designed for small and medium-sized businesses, providing tools for managing employee records, leave requests, performance reviews, document storage, and reporting
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `X-API-KEY` header.
|
||||
Format: `X-API-KEY: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BREATHE_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
name: brevo
|
||||
version: "1.0.0"
|
||||
description: Brevo (Sendinblue) API — email campaigns, contacts, transactional email, SMS
|
||||
activation:
|
||||
keywords:
|
||||
- "brevo"
|
||||
- "sendinblue"
|
||||
- "email campaign"
|
||||
exclude_keywords:
|
||||
- "mailchimp"
|
||||
- "resend"
|
||||
patterns:
|
||||
- "(?i)(brevo|sendinblue).*(email|contact|campaign|sms)"
|
||||
tags:
|
||||
- "email"
|
||||
- "marketing"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BREVO_API_KEY]
|
||||
---
|
||||
|
||||
# Brevo API (formerly Sendinblue)
|
||||
|
||||
Use the `http` tool. Include `api-key` header.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.brevo.com/v3`
|
||||
|
||||
## Actions
|
||||
|
||||
**Send transactional email:**
|
||||
```
|
||||
http(method="POST", url="https://api.brevo.com/v3/smtp/email", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}], body={"sender": {"name": "My App", "email": "[email protected]"}, "to": [{"email": "[email protected]", "name": "John"}], "subject": "Welcome!", "htmlContent": "<h1>Hello John</h1><p>Welcome aboard.</p>"})
|
||||
```
|
||||
|
||||
**List contacts:**
|
||||
```
|
||||
http(method="GET", url="https://api.brevo.com/v3/contacts?limit=20&offset=0", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Create contact:**
|
||||
```
|
||||
http(method="POST", url="https://api.brevo.com/v3/contacts", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}], body={"email": "[email protected]", "attributes": {"FIRSTNAME": "Alice", "LASTNAME": "Smith"}, "listIds": [1]})
|
||||
```
|
||||
|
||||
**Update contact:**
|
||||
```
|
||||
http(method="PUT", url="https://api.brevo.com/v3/contacts/[email protected]", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}], body={"attributes": {"FIRSTNAME": "Updated"}})
|
||||
```
|
||||
|
||||
**List email campaigns:**
|
||||
```
|
||||
http(method="GET", url="https://api.brevo.com/v3/emailCampaigns?limit=20&status=sent", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Get campaign stats:**
|
||||
```
|
||||
http(method="GET", url="https://api.brevo.com/v3/emailCampaigns/<campaign_id>", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Send SMS:**
|
||||
```
|
||||
http(method="POST", url="https://api.brevo.com/v3/transactionalSMS/sms", headers=[{"name": "api-key", "value": "{BREVO_API_KEY}"}], body={"sender": "MyApp", "recipient": "+1234567890", "content": "Your code is 123456", "type": "transactional"})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Contact attributes are uppercase: `FIRSTNAME`, `LASTNAME`, `SMS`.
|
||||
- `listIds` are integer IDs of contact lists.
|
||||
- Campaign statuses: `draft`, `sent`, `queued`, `suspended`, `in_process`.
|
||||
- Pagination: `limit` + `offset`. Check `count` for total.
|
||||
- Transactional email returns `messageId` for tracking.
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: brex
|
||||
version: "1.0.0"
|
||||
description: Brex API — Brex combines corporate cards, business accounts, expense management, bill pay
|
||||
activation:
|
||||
keywords:
|
||||
- "brex"
|
||||
- "finance"
|
||||
patterns:
|
||||
- "(?i)brex"
|
||||
tags:
|
||||
- "tools"
|
||||
- "finance"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Brex API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Brex combines corporate cards, business accounts, expense management, bill pay, and travel booking into a single AI-powered financial operations platform—offering unified spend control, real-time visi
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: bright-data
|
||||
version: "1.0.0"
|
||||
description: BrightData API — Bright Data (formerly Luminati) is a comprehensive web data platform offering a
|
||||
activation:
|
||||
keywords:
|
||||
- "bright-data"
|
||||
- "brightdata"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)bright.?data"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BRIGHT_DATA_API_KEY]
|
||||
---
|
||||
|
||||
# BrightData API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Bright Data (formerly Luminati) is a comprehensive web data platform offering a global proxy network (residential, mobile, ISP, data center), browser-based scraping, SERP APIs, and managed data pipeli
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BRIGHT_DATA_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: browse-ai
|
||||
version: "1.0.0"
|
||||
description: Browse AI API — Browse AI is a no-code, AI-powered web scraping and monitoring platform that ena
|
||||
activation:
|
||||
keywords:
|
||||
- "browse-ai"
|
||||
- "browse ai"
|
||||
- "scraper"
|
||||
patterns:
|
||||
- "(?i)browse.?ai"
|
||||
tags:
|
||||
- "tools"
|
||||
- "scraper"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BROWSE_AI_API_KEY]
|
||||
---
|
||||
|
||||
# Browse AI API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Browse AI is a no-code, AI-powered web scraping and monitoring platform that enables users to extract structured data from any website, set automated alerts for changes, and funnel the output into spr
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BROWSE_AI_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
name: browserbase
|
||||
version: "1.0.0"
|
||||
description: Browserbase API — Browserbase is a cloud platform that lets developers run headless browsers at sc
|
||||
activation:
|
||||
keywords:
|
||||
- "browserbase"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)browserbase"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BROWSERBASE_API_KEY]
|
||||
---
|
||||
|
||||
# Browserbase API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-BB-API-Key` header — **never construct auth headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.browserbase.com/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**Create session:**
|
||||
```
|
||||
http(method="POST", url="https://api.browserbase.com/v1/sessions", body={"projectId": "<project_id>"})
|
||||
```
|
||||
|
||||
**List sessions:**
|
||||
```
|
||||
http(method="GET", url="https://api.browserbase.com/v1/sessions?limit=10")
|
||||
```
|
||||
|
||||
**Get session:**
|
||||
```
|
||||
http(method="GET", url="https://api.browserbase.com/v1/sessions/{session_id}")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Sessions provide a headless browser instance.
|
||||
- Connect via CDP (Chrome DevTools Protocol) using the session's debug URL.
|
||||
- Project ID is required for session creation.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: bug-bug
|
||||
version: "1.0.0"
|
||||
description: BugBug API — A no-code testing platform that automatically crawls websites and web apps to de
|
||||
activation:
|
||||
keywords:
|
||||
- "bug-bug"
|
||||
- "bugbug"
|
||||
- "bug detection"
|
||||
patterns:
|
||||
- "(?i)bug.?bug"
|
||||
tags:
|
||||
- "tools"
|
||||
- "bug-detection"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BUG_BUG_API_KEY]
|
||||
---
|
||||
|
||||
# BugBug API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> A no-code testing platform that automatically crawls websites and web apps to detect visual issues, broken links, and UI regressions, helping teams maintain quality, catch bugs early, and streamline Q
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Token ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BUG_BUG_API_KEY` — API key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: bug-herd
|
||||
version: "1.0.0"
|
||||
description: BugHerd API — A web-based issue and feedback tracking tool that lets teams capture visual bugs
|
||||
activation:
|
||||
keywords:
|
||||
- "bug-herd"
|
||||
- "bugherd"
|
||||
- "bug tracking"
|
||||
patterns:
|
||||
- "(?i)bug.?herd"
|
||||
tags:
|
||||
- "tools"
|
||||
- "bug-tracking"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BUG_HERD_USERNAME, BUG_HERD_PASSWORD]
|
||||
---
|
||||
|
||||
# BugHerd API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
> A web-based issue and feedback tracking tool that lets teams capture visual bugs directly on web pages, annotate problems, manage tickets, and collaborate on fixes for faster design and development cy
|
||||
|
||||
## Authentication
|
||||
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BUG_HERD_USERNAME` — API Key
|
||||
- `BUG_HERD_PASSWORD` — Password
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: byte-forms
|
||||
version: "1.0.0"
|
||||
description: ByteForms API — A no-code form creation tool that enables businesses to design, deploy
|
||||
activation:
|
||||
keywords:
|
||||
- "byte-forms"
|
||||
- "byteforms"
|
||||
- "form builder"
|
||||
patterns:
|
||||
- "(?i)byte.?forms"
|
||||
tags:
|
||||
- "tools"
|
||||
- "form-builder"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [BYTE_FORMS_API_KEY]
|
||||
---
|
||||
|
||||
# ByteForms API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> A no-code form creation tool that enables businesses to design, deploy, and embed customizable online forms for data collection, surveys, and customer feedback with optional logic and integrations.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `BYTE_FORMS_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,81 @@
|
||||
---
|
||||
name: calcom
|
||||
version: "1.0.0"
|
||||
description: Cal.com API v2 — event types, bookings, availability, schedules
|
||||
activation:
|
||||
keywords:
|
||||
- "cal.com"
|
||||
- "calcom"
|
||||
- "cal dot com"
|
||||
exclude_keywords:
|
||||
- "calendly"
|
||||
- "google calendar"
|
||||
patterns:
|
||||
- "(?i)cal\\.?com.*(event|booking|availability|schedule)"
|
||||
tags:
|
||||
- "scheduling"
|
||||
- "calendar"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CALCOM_API_KEY]
|
||||
---
|
||||
|
||||
# Cal.com API v2
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.cal.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.cal.com/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List event types:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/event-types")
|
||||
```
|
||||
|
||||
**Get event type:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/event-types/<event_type_id>")
|
||||
```
|
||||
|
||||
**List bookings:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/bookings?status=upcoming&take=20")
|
||||
```
|
||||
|
||||
**Get booking:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/bookings/<booking_uid>")
|
||||
```
|
||||
|
||||
**Create booking:**
|
||||
```
|
||||
http(method="POST", url="https://api.cal.com/v2/bookings", body={"eventTypeId": 123, "start": "2026-04-01T10:00:00Z", "attendee": {"name": "John Doe", "email": "[email protected]", "timeZone": "America/New_York"}, "metadata": {}})
|
||||
```
|
||||
|
||||
**Cancel booking:**
|
||||
```
|
||||
http(method="POST", url="https://api.cal.com/v2/bookings/<booking_uid>/cancel", body={"cancellationReason": "Schedule conflict"})
|
||||
```
|
||||
|
||||
**Get availability:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/slots/available?startTime=2026-04-01T00:00:00Z&endTime=2026-04-07T00:00:00Z&eventTypeId=123")
|
||||
```
|
||||
|
||||
**List schedules:**
|
||||
```
|
||||
http(method="GET", url="https://api.cal.com/v2/schedules")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Responses: `{"status": "success", "data": {...}}`.
|
||||
- Booking status: `upcoming`, `recurring`, `past`, `cancelled`, `unconfirmed`.
|
||||
- Times are always UTC (ISO 8601). Attendee specifies their timezone.
|
||||
- Booking UIDs are UUID strings.
|
||||
- Use `take` and `skip` for pagination.
|
||||
@@ -0,0 +1,77 @@
|
||||
---
|
||||
name: calendly
|
||||
version: "1.0.0"
|
||||
description: Calendly API v2 — event types, scheduled events, invitees
|
||||
activation:
|
||||
keywords:
|
||||
- "calendly"
|
||||
- "calendly event"
|
||||
- "booking"
|
||||
- "scheduling link"
|
||||
exclude_keywords:
|
||||
- "cal.com"
|
||||
- "google calendar"
|
||||
patterns:
|
||||
- "(?i)calendly.*(event|booking|invitee|schedule)"
|
||||
tags:
|
||||
- "scheduling"
|
||||
- "calendar"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CALENDLY_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Calendly API v2
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.calendly.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.calendly.com`
|
||||
|
||||
## Actions
|
||||
|
||||
**Get current user:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/users/me")
|
||||
```
|
||||
|
||||
**List event types:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/event_types?user=<user_uri>&count=20")
|
||||
```
|
||||
|
||||
**List scheduled events:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/scheduled_events?user=<user_uri>&min_start_time=2026-03-27T00:00:00Z&max_start_time=2026-04-30T00:00:00Z&status=active&count=20")
|
||||
```
|
||||
|
||||
**Get event details:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/scheduled_events/<event_uuid>")
|
||||
```
|
||||
|
||||
**List invitees for event:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/scheduled_events/<event_uuid>/invitees?count=20")
|
||||
```
|
||||
|
||||
**Cancel event:**
|
||||
```
|
||||
http(method="POST", url="https://api.calendly.com/scheduled_events/<event_uuid>/cancellation", body={"reason": "Schedule conflict"})
|
||||
```
|
||||
|
||||
**List organization members:**
|
||||
```
|
||||
http(method="GET", url="https://api.calendly.com/organization_memberships?organization=<org_uri>")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Resources are identified by URIs (e.g., `https://api.calendly.com/users/ABCDEF123456`), not plain IDs.
|
||||
- First call `GET /users/me` to get your `uri` and `current_organization`.
|
||||
- Event status: `active`, `canceled`.
|
||||
- Pagination: use `page_token` from `pagination.next_page_token`.
|
||||
- Dates are ISO 8601 with timezone (UTC recommended).
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
name: canva
|
||||
version: "1.0.0"
|
||||
description: Canva API — Canva is a cloud-based graphic design platform with a drag‑and‑drop editor
|
||||
activation:
|
||||
keywords:
|
||||
- "canva"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)canva"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Canva API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.canva.com/rest/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**List designs:**
|
||||
```
|
||||
http(method="GET", url="https://api.canva.com/rest/v1/designs?limit=10")
|
||||
```
|
||||
|
||||
**Get design:**
|
||||
```
|
||||
http(method="GET", url="https://api.canva.com/rest/v1/designs/{design_id}")
|
||||
```
|
||||
|
||||
**Create design:**
|
||||
```
|
||||
http(method="POST", url="https://api.canva.com/rest/v1/designs", body={"title": "My Design","design_type": {"type": "preset","name": "doc"}})
|
||||
```
|
||||
|
||||
**Export design:**
|
||||
```
|
||||
http(method="POST", url="https://api.canva.com/rest/v1/designs/{design_id}/exports", body={"format": {"type": "png"}})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses OAuth 2.0 — credentials are auto-injected.
|
||||
- Design types: `doc`, `presentation`, `whiteboard`, `social_media`.
|
||||
- Export formats: `png`, `jpg`, `pdf`, `svg`, `mp4`.
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: capsule
|
||||
version: "1.0.0"
|
||||
description: Capsule API — Capsule CRM is a streamlined cloud-based CRM designed for small businesses and s
|
||||
activation:
|
||||
keywords:
|
||||
- "capsule"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)capsule"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Capsule API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Capsule CRM is a streamlined cloud-based CRM designed for small businesses and sales teams, furnishing contact and organisation management, sales pipelines, tasks, projects, and analytics in one place
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: cats
|
||||
version: "1.0.0"
|
||||
description: CATS API — CATS is a web-based applicant tracking system designed for recruiting agencies a
|
||||
activation:
|
||||
keywords:
|
||||
- "cats"
|
||||
- "ats"
|
||||
patterns:
|
||||
- "(?i)cats"
|
||||
tags:
|
||||
- "tools"
|
||||
- "ats"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CATS_API_KEY]
|
||||
---
|
||||
|
||||
# CATS API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> CATS is a web-based applicant tracking system designed for recruiting agencies and HR teams, offering tools for job posting, resume parsing, candidate tracking, custom workflows, analytics, and integr
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `authorization` header.
|
||||
Format: `authorization: Token ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CATS_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: central-station-crm
|
||||
version: "1.0.0"
|
||||
description: Central Station CRM API — CentralStationCRM is a lightweight CRM designed for small businesses to manage c
|
||||
activation:
|
||||
keywords:
|
||||
- "central-station-crm"
|
||||
- "central station crm"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)central.?station.?crm"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CENTRAL_STATION_CRM_API_KEY]
|
||||
---
|
||||
|
||||
# Central Station CRM API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `X-apikey` header — **never construct auth headers manually**.
|
||||
|
||||
> CentralStationCRM is a lightweight CRM designed for small businesses to manage contacts, track deals, organize tasks and streamline customer relationships with a simple, user-friendly interface.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `X-apikey` header.
|
||||
Format: `X-apikey: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CENTRAL_STATION_CRM_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,65 @@
|
||||
---
|
||||
name: chargebee
|
||||
version: "1.0.0"
|
||||
description: Chargebee API — Chargebee is a subscription billing and revenue operations platform that helps S
|
||||
activation:
|
||||
keywords:
|
||||
- "chargebee"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)chargebee"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CHARGEBEE_SUBDOMAIN, CHARGEBEE_API_KEY]
|
||||
---
|
||||
|
||||
# Chargebee API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://{CHARGEBEE_SITE}.chargebee.com/api/v2`
|
||||
|
||||
**Content-Type**: `application/x-www-form-urlencoded` for POST/PUT requests.
|
||||
|
||||
## Actions
|
||||
|
||||
**List subscriptions:**
|
||||
```
|
||||
http(method="GET", url="https://{CHARGEBEE_SITE}.chargebee.com/api/v2/subscriptions?limit=10")
|
||||
```
|
||||
|
||||
**Get subscription:**
|
||||
```
|
||||
http(method="GET", url="https://{CHARGEBEE_SITE}.chargebee.com/api/v2/subscriptions/{subscription_id}")
|
||||
```
|
||||
|
||||
**Create subscription:**
|
||||
```
|
||||
http(method="POST", url="https://{CHARGEBEE_SITE}.chargebee.com/api/v2/subscriptions", headers=[{"name": "Content-Type", "value": "application/x-www-form-urlencoded"}], body="customer[email][email protected]&plan_id=basic-monthly")
|
||||
```
|
||||
|
||||
**List customers:**
|
||||
```
|
||||
http(method="GET", url="https://{CHARGEBEE_SITE}.chargebee.com/api/v2/customers?limit=10")
|
||||
```
|
||||
|
||||
**List invoices:**
|
||||
```
|
||||
http(method="GET", url="https://{CHARGEBEE_SITE}.chargebee.com/api/v2/invoices?limit=10&sort_by[asc]=date")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses Basic auth with API key as username and empty password.
|
||||
- POST bodies are form-encoded with bracket notation: `customer[email]=...`.
|
||||
- Subscription states: `future`, `in_trial`, `active`, `non_renewing`, `paused`, `cancelled`.
|
||||
- Pagination: `offset` key in response; pass as `?offset=...` for next page.
|
||||
@@ -0,0 +1,63 @@
|
||||
---
|
||||
name: circle-ci
|
||||
version: "1.0.0"
|
||||
description: Circle CI API — CircleCI is a continuous integration and delivery (CI/CD) platform that automate
|
||||
activation:
|
||||
keywords:
|
||||
- "circle-ci"
|
||||
- "circle ci"
|
||||
- "devops"
|
||||
patterns:
|
||||
- "(?i)circle.?ci"
|
||||
tags:
|
||||
- "devops"
|
||||
- "ci-cd"
|
||||
- "deployment"
|
||||
- "dev-ops"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CIRCLE_CI_API_KEY]
|
||||
---
|
||||
|
||||
# Circle CI API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Circle-Token` header — **never construct auth headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://circleci.com/api/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**Get current user:**
|
||||
```
|
||||
http(method="GET", url="https://circleci.com/api/v2/me")
|
||||
```
|
||||
|
||||
**List pipelines:**
|
||||
```
|
||||
http(method="GET", url="https://circleci.com/api/v2/project/{project_slug}/pipeline?branch=main")
|
||||
```
|
||||
|
||||
**Get pipeline:**
|
||||
```
|
||||
http(method="GET", url="https://circleci.com/api/v2/pipeline/{pipeline_id}")
|
||||
```
|
||||
|
||||
**List workflows:**
|
||||
```
|
||||
http(method="GET", url="https://circleci.com/api/v2/pipeline/{pipeline_id}/workflow")
|
||||
```
|
||||
|
||||
**Trigger pipeline:**
|
||||
```
|
||||
http(method="POST", url="https://circleci.com/api/v2/project/{project_slug}/pipeline", body={"branch": "main","parameters": {}})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Project slug format: `gh/{org}/{repo}` or `bb/{org}/{repo}`.
|
||||
- Pipeline statuses: `created`, `errored`, `setup-pending`, `setup`, `pending`.
|
||||
- Workflow statuses: `success`, `running`, `not_run`, `failed`, `error`, `failing`, `on_hold`, `canceled`.
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
name: clerk
|
||||
version: "1.0.0"
|
||||
description: Clerk API — Clerk provides user authentication and user management solutions for modern web
|
||||
activation:
|
||||
keywords:
|
||||
- "clerk"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)clerk"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CLERK_API_KEY]
|
||||
---
|
||||
|
||||
# Clerk API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.clerk.com/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**List users:**
|
||||
```
|
||||
http(method="GET", url="https://api.clerk.com/v1/users?limit=10&order_by=-created_at")
|
||||
```
|
||||
|
||||
**Get user:**
|
||||
```
|
||||
http(method="GET", url="https://api.clerk.com/v1/users/{user_id}")
|
||||
```
|
||||
|
||||
**Create user:**
|
||||
```
|
||||
http(method="POST", url="https://api.clerk.com/v1/users", body={"email_address": ["[email protected]"],"first_name": "John","last_name": "Doe","password": "SecureP@ss1"})
|
||||
```
|
||||
|
||||
**Update user:**
|
||||
```
|
||||
http(method="PATCH", url="https://api.clerk.com/v1/users/{user_id}", body={"first_name": "Jane"})
|
||||
```
|
||||
|
||||
**Delete user:**
|
||||
```
|
||||
http(method="DELETE", url="https://api.clerk.com/v1/users/{user_id}")
|
||||
```
|
||||
|
||||
**List organizations:**
|
||||
```
|
||||
http(method="GET", url="https://api.clerk.com/v1/organizations?limit=10")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- User IDs start with `user_`.
|
||||
- Email addresses are arrays — users can have multiple.
|
||||
- Use `?query=` for fuzzy search across name/email.
|
||||
- Pagination: `limit` + `offset`.
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
name: click-house
|
||||
version: "1.0.0"
|
||||
description: ClickHouse API — ClickHouse is an ultra-fast, column-oriented database designed for real-time ana
|
||||
activation:
|
||||
keywords:
|
||||
- "click-house"
|
||||
- "clickhouse"
|
||||
- "analytics"
|
||||
patterns:
|
||||
- "(?i)click.?house"
|
||||
tags:
|
||||
- "analytics"
|
||||
- "data"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CLICK_HOUSE_API_KEY, CLICK_HOUSE_SECRET_KEY]
|
||||
---
|
||||
|
||||
# ClickHouse API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://{CLICKHOUSE_HOST}:8443`
|
||||
|
||||
## Actions
|
||||
|
||||
**Run query:**
|
||||
```
|
||||
http(method="POST", url="https://{CLICKHOUSE_HOST}:8443/?query=SELECT+1")
|
||||
```
|
||||
|
||||
**List tables:**
|
||||
```
|
||||
http(method="POST", url="https://{CLICKHOUSE_HOST}:8443/?query=SHOW+TABLES+FROM+default")
|
||||
```
|
||||
|
||||
**Insert data:**
|
||||
```
|
||||
http(method="POST", url="https://{CLICKHOUSE_HOST}:8443/?query=INSERT+INTO+table+FORMAT+JSONEachRow", body=[{"col1": "value1","col2": 42}])
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- ClickHouse uses HTTP interface on port 8443 (HTTPS) or 8123 (HTTP).
|
||||
- Pass SQL in `query` parameter or POST body.
|
||||
- Output formats: `JSON`, `JSONEachRow`, `CSV`, `TSV`.
|
||||
- Auth: Basic auth or `X-ClickHouse-User`/`X-ClickHouse-Key` headers.
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
name: click-send
|
||||
version: "1.0.0"
|
||||
description: ClickSend API — A cloud-based messaging and communication service that enables businesses to sen
|
||||
activation:
|
||||
keywords:
|
||||
- "click-send"
|
||||
- "clicksend"
|
||||
- "communication"
|
||||
patterns:
|
||||
- "(?i)click.?send"
|
||||
tags:
|
||||
- "messaging"
|
||||
- "communication"
|
||||
- "chat"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CLICK_SEND_USERNAME, CLICK_SEND_PASSWORD]
|
||||
---
|
||||
|
||||
# ClickSend API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://rest.clicksend.com/v3`
|
||||
|
||||
## Actions
|
||||
|
||||
**Send SMS:**
|
||||
```
|
||||
http(method="POST", url="https://rest.clicksend.com/v3/sms/send", body={"messages": [{"to": "+1234567890","body": "Hello!","source": "sdk"}]})
|
||||
```
|
||||
|
||||
**Get SMS history:**
|
||||
```
|
||||
http(method="GET", url="https://rest.clicksend.com/v3/sms/history?page=1&limit=10")
|
||||
```
|
||||
|
||||
**Send email:**
|
||||
```
|
||||
http(method="POST", url="https://rest.clicksend.com/v3/email/send", body={"to": [{"email": "[email protected]","name": "John"}],"from": {"email": "[email protected]"},"subject": "Hello","body": "<p>Content</p>"})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses Basic auth with username and API key.
|
||||
- SMS `to` must include country code (e.g., `+1234567890`).
|
||||
- Supports SMS, MMS, email, voice, fax, and postal mail.
|
||||
@@ -0,0 +1,83 @@
|
||||
---
|
||||
name: clickup
|
||||
version: "1.0.0"
|
||||
description: ClickUp API v2 — tasks, spaces, lists, comments, time tracking
|
||||
activation:
|
||||
keywords:
|
||||
- "clickup"
|
||||
- "clickup task"
|
||||
- "clickup space"
|
||||
exclude_keywords:
|
||||
- "jira"
|
||||
- "asana"
|
||||
patterns:
|
||||
- "(?i)clickup.*(task|space|list|folder)"
|
||||
- "(?i)(create|list|update).*clickup"
|
||||
tags:
|
||||
- "project-management"
|
||||
- "task-management"
|
||||
max_context_tokens: 1500
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CLICKUP_API_TOKEN]
|
||||
---
|
||||
|
||||
# ClickUp API v2
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.clickup.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.clickup.com/api/v2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List workspaces (teams):**
|
||||
```
|
||||
http(method="GET", url="https://api.clickup.com/api/v2/team")
|
||||
```
|
||||
|
||||
**List spaces:**
|
||||
```
|
||||
http(method="GET", url="https://api.clickup.com/api/v2/team/<team_id>/space")
|
||||
```
|
||||
|
||||
**List folders in space:**
|
||||
```
|
||||
http(method="GET", url="https://api.clickup.com/api/v2/space/<space_id>/folder")
|
||||
```
|
||||
|
||||
**List tasks in a list:**
|
||||
```
|
||||
http(method="GET", url="https://api.clickup.com/api/v2/list/<list_id>/task?page=0&subtasks=true&include_closed=false")
|
||||
```
|
||||
|
||||
**Get task:**
|
||||
```
|
||||
http(method="GET", url="https://api.clickup.com/api/v2/task/<task_id>")
|
||||
```
|
||||
|
||||
**Create task:**
|
||||
```
|
||||
http(method="POST", url="https://api.clickup.com/api/v2/list/<list_id>/task", body={"name": "Task name", "description": "Details", "status": "to do", "priority": 2, "due_date": 1775000000000, "assignees": [123456]})
|
||||
```
|
||||
|
||||
**Update task:**
|
||||
```
|
||||
http(method="PUT", url="https://api.clickup.com/api/v2/task/<task_id>", body={"status": "in progress", "priority": 1})
|
||||
```
|
||||
|
||||
**Add comment:**
|
||||
```
|
||||
http(method="POST", url="https://api.clickup.com/api/v2/task/<task_id>/comment", body={"comment_text": "My comment"})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Priority: 1=Urgent, 2=High, 3=Normal, 4=Low.
|
||||
- Due dates are Unix timestamps in **milliseconds**.
|
||||
- Status values are lowercase strings matching your workspace statuses.
|
||||
- Task IDs are alphanumeric strings like `"abc123"`.
|
||||
- Hierarchy: Team → Space → Folder → List → Task.
|
||||
- Pagination: `page` param (0-indexed). Returns empty array when no more.
|
||||
@@ -0,0 +1,59 @@
|
||||
---
|
||||
name: close
|
||||
version: "1.0.0"
|
||||
description: Close API — Close is a sales engagement CRM designed to help inside sales teams close more d
|
||||
activation:
|
||||
keywords:
|
||||
- "close"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)close"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Close API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.close.com/api/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**List leads:**
|
||||
```
|
||||
http(method="GET", url="https://api.close.com/api/v1/lead/?_limit=10")
|
||||
```
|
||||
|
||||
**Get lead:**
|
||||
```
|
||||
http(method="GET", url="https://api.close.com/api/v1/lead/{lead_id}/")
|
||||
```
|
||||
|
||||
**Create lead:**
|
||||
```
|
||||
http(method="POST", url="https://api.close.com/api/v1/lead/", body={"name": "Acme Corp","contacts": [{"name": "John Doe","emails": [{"email": "[email protected]","type": "office"}]}]})
|
||||
```
|
||||
|
||||
**Search leads:**
|
||||
```
|
||||
http(method="POST", url="https://api.close.com/api/v1/data/search/", body={"query": {"type": "and","queries": [{"type": "field_condition","field": {"field_name": "lead_name"},"condition": {"type": "text","mode": "full_words","value": "Acme"}}]},"results_limit": 10})
|
||||
```
|
||||
|
||||
**List activities:**
|
||||
```
|
||||
http(method="GET", url="https://api.close.com/api/v1/activity/?_limit=10")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses API key as Basic auth username (no password).
|
||||
- Lead IDs start with `lead_`.
|
||||
- Activities: `EmailThread`, `Call`, `SMS`, `Note`, `Meeting`.
|
||||
- Pagination: `_skip` and `_limit` params.
|
||||
@@ -0,0 +1,58 @@
|
||||
---
|
||||
name: cloudinary
|
||||
version: "1.0.0"
|
||||
description: Cloudinary API — Cloudinary is a cloud-based media management platform that enables developers an
|
||||
activation:
|
||||
keywords:
|
||||
- "cloudinary"
|
||||
- "media management"
|
||||
patterns:
|
||||
- "(?i)cloudinary"
|
||||
tags:
|
||||
- "tools"
|
||||
- "media-management"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CLOUDINARY_USERNAME, CLOUDINARY_PASSWORD, CLOUDINARY_CLOUD_NAME]
|
||||
---
|
||||
|
||||
# Cloudinary API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.cloudinary.com/v1_1/{CLOUDINARY_CLOUD_NAME}`
|
||||
|
||||
**Content-Type**: `application/x-www-form-urlencoded` for POST/PUT requests.
|
||||
|
||||
## Actions
|
||||
|
||||
**Upload image:**
|
||||
```
|
||||
http(method="POST", url="https://api.cloudinary.com/v1_1/{CLOUDINARY_CLOUD_NAME}/image/upload", headers=[{"name": "Content-Type", "value": "application/x-www-form-urlencoded"}], body="file=https://example.com/image.jpg&upload_preset=my_preset")
|
||||
```
|
||||
|
||||
**Get resource details:**
|
||||
```
|
||||
http(method="GET", url="https://api.cloudinary.com/v1_1/{CLOUDINARY_CLOUD_NAME}/resources/image/upload/{public_id}")
|
||||
```
|
||||
|
||||
**List resources:**
|
||||
```
|
||||
http(method="GET", url="https://api.cloudinary.com/v1_1/{CLOUDINARY_CLOUD_NAME}/resources/image?max_results=10")
|
||||
```
|
||||
|
||||
**Delete resource:**
|
||||
```
|
||||
http(method="DELETE", url="https://api.cloudinary.com/v1_1/{CLOUDINARY_CLOUD_NAME}/resources/image/upload?public_ids[]={public_id}")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Uses Basic auth with API key and secret.
|
||||
- Upload accepts URL, base64, or file.
|
||||
- Transformations via URL: `https://res.cloudinary.com/{cloud}/image/upload/w_300,h_200,c_fill/{public_id}`.
|
||||
- Upload presets define default transformations and folders.
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: clover
|
||||
version: "1.0.0"
|
||||
description: Clover API — Clover is a point-of-sale and business management system that helps businesses a
|
||||
activation:
|
||||
keywords:
|
||||
- "clover"
|
||||
- "pos"
|
||||
patterns:
|
||||
- "(?i)clover"
|
||||
tags:
|
||||
- "tools"
|
||||
- "POS"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Clover API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Clover is a point-of-sale and business management system that helps businesses accept payments, track sales, manage inventory, and run operations from one integrated platform.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: cockroach-labs
|
||||
version: "1.0.0"
|
||||
description: Cockroach Labs API — Cockroach Labs develops a distributed SQL database designed for cloud applicatio
|
||||
activation:
|
||||
keywords:
|
||||
- "cockroach-labs"
|
||||
- "cockroach labs"
|
||||
- "cloud database"
|
||||
patterns:
|
||||
- "(?i)cockroach.?labs"
|
||||
tags:
|
||||
- "tools"
|
||||
- "cloud-database"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [COCKROACH_LABS_API_KEY]
|
||||
---
|
||||
|
||||
# Cockroach Labs API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> Cockroach Labs develops a distributed SQL database designed for cloud applications, providing scalable, resilient, strongly consistent data storage with multi-region replication, automatic failover, a
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Bearer ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `COCKROACH_LABS_API_KEY` — API Keys
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
name: coda
|
||||
version: "1.0.0"
|
||||
description: Coda API — Coda is an all-in-one collaborative workspace that blends the flexibility of doc
|
||||
activation:
|
||||
keywords:
|
||||
- "coda"
|
||||
- "productivity"
|
||||
patterns:
|
||||
- "(?i)coda"
|
||||
tags:
|
||||
- "productivity"
|
||||
- "collaboration"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CODA_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Coda API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://coda.io/apis/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**List docs:**
|
||||
```
|
||||
http(method="GET", url="https://coda.io/apis/v1/docs?limit=10")
|
||||
```
|
||||
|
||||
**Get doc:**
|
||||
```
|
||||
http(method="GET", url="https://coda.io/apis/v1/docs/{doc_id}")
|
||||
```
|
||||
|
||||
**List tables:**
|
||||
```
|
||||
http(method="GET", url="https://coda.io/apis/v1/docs/{doc_id}/tables")
|
||||
```
|
||||
|
||||
**List rows:**
|
||||
```
|
||||
http(method="GET", url="https://coda.io/apis/v1/docs/{doc_id}/tables/{table_id}/rows?limit=20")
|
||||
```
|
||||
|
||||
**Insert row:**
|
||||
```
|
||||
http(method="POST", url="https://coda.io/apis/v1/docs/{doc_id}/tables/{table_id}/rows", body={"rows": [{"cells": [{"column": "Name","value": "John"},{"column": "Email","value": "[email protected]"}]}]})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Doc IDs are alphanumeric strings.
|
||||
- Tables can be referenced by name or ID.
|
||||
- Row values reference columns by name or ID.
|
||||
- Pagination: `pageToken` from response's `nextPageToken`.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: conductor
|
||||
version: "1.0.0"
|
||||
description: Conductor API — Conductor is an enterprise-scale website optimization and AI-powered intelligenc
|
||||
activation:
|
||||
keywords:
|
||||
- "conductor"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)conductor"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CONDUCTOR_API_KEY]
|
||||
---
|
||||
|
||||
# Conductor API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Conductor is an enterprise-scale website optimization and AI-powered intelligence platform that combines SEO, AI-generated content suggestions, and continuous site health monitoring—empowering marketi
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CONDUCTOR_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: contentstack-content-delivery
|
||||
version: "1.0.0"
|
||||
description: Contentstack Content Delivery API — Contentstack Content Delivery API is a high-performance
|
||||
activation:
|
||||
keywords:
|
||||
- "contentstack-content-delivery"
|
||||
- "contentstack content delivery"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)contentstack.?content.?delivery"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CONTENTSTACK_CONTENT_DELIVERY_BASE_URL, CONTENTSTACK_CONTENT_DELIVERY_STACK_API_KEY, CONTENTSTACK_CONTENT_DELIVERY_DELIVERY_TOKEN]
|
||||
---
|
||||
|
||||
# Contentstack Content Delivery API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `api_key` header — **never construct auth headers manually**.
|
||||
|
||||
> Contentstack Content Delivery API is a high-performance, read-only REST and GraphQL service that retrieves published content from your headless CMS via a global CDN—supporting efficient queries, cachi
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `api_key` header.
|
||||
Format: `api_key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CONTENTSTACK_CONTENT_DELIVERY_BASE_URL` — Base URL
|
||||
- `CONTENTSTACK_CONTENT_DELIVERY_STACK_API_KEY` — Stack API Key
|
||||
- `CONTENTSTACK_CONTENT_DELIVERY_DELIVERY_TOKEN` — Delivery Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: contentstack-content-management
|
||||
version: "1.0.0"
|
||||
description: Contentstack Content Management API — Contentstack’s Content Management API is a powerful
|
||||
activation:
|
||||
keywords:
|
||||
- "contentstack-content-management"
|
||||
- "contentstack content management"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)contentstack.?content.?management"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CONTENTSTACK_CONTENT_MANAGEMENT_STACK_API_KEY]
|
||||
---
|
||||
|
||||
# Contentstack Content Management API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Contentstack’s Content Management API is a powerful, API-first REST interface that enables developers to programmatically create, update, delete, and structure content—supporting secure token-based ac
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CONTENTSTACK_CONTENT_MANAGEMENT_STACK_API_KEY` — Stack API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: convex-deployment
|
||||
version: "1.0.0"
|
||||
description: Convex Deployment API — Convex Deployment enables developers to deploy backend functions
|
||||
activation:
|
||||
keywords:
|
||||
- "convex-deployment"
|
||||
- "convex deployment"
|
||||
- "tools"
|
||||
patterns:
|
||||
- "(?i)convex.?deployment"
|
||||
tags:
|
||||
- "tools"
|
||||
- "utility"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CONVEX_DEPLOYMENT_DEPLOY_KEY, CONVEX_DEPLOYMENT_BASE_URL]
|
||||
---
|
||||
|
||||
# Convex Deployment API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> Convex Deployment enables developers to deploy backend functions, database schema, indexes, and configuration for applications built on the Convex platform. It supports development, preview, and produ
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Convex ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CONVEX_DEPLOYMENT_DEPLOY_KEY` — API Key
|
||||
- `CONVEX_DEPLOYMENT_BASE_URL` — Deployment URL
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: convex-management
|
||||
version: "1.0.0"
|
||||
description: Convex Management API — Convex Management provides a developer console for managing applications built o
|
||||
activation:
|
||||
keywords:
|
||||
- "convex-management"
|
||||
- "convex management"
|
||||
- "baas"
|
||||
patterns:
|
||||
- "(?i)convex.?management"
|
||||
tags:
|
||||
- "tools"
|
||||
- "baas"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Convex Management API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Convex Management provides a developer console for managing applications built on the Convex backend platform, including database data, serverless functions, deployments, logs, and configuration, help
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: coresignal
|
||||
version: "1.0.0"
|
||||
description: Coresignal API — Coresignal provides large-scale public web data for investment, HR tech
|
||||
activation:
|
||||
keywords:
|
||||
- "coresignal"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)coresignal"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CORESIGNAL_API_KEY]
|
||||
---
|
||||
|
||||
# Coresignal API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `apikey` header — **never construct auth headers manually**.
|
||||
|
||||
> Coresignal provides large-scale public web data for investment, HR tech, and other industries. It offers datasets on companies, jobs, people, and more to power business insights and machine learning m
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `apikey` header.
|
||||
Format: `apikey: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CORESIGNAL_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: currents-news
|
||||
version: "1.0.0"
|
||||
description: Currents News API — Currents News API offers a real-time, RESTful news service that delivers global
|
||||
activation:
|
||||
keywords:
|
||||
- "currents-news"
|
||||
- "currents news"
|
||||
- "news"
|
||||
patterns:
|
||||
- "(?i)currents.?news"
|
||||
tags:
|
||||
- "news"
|
||||
- "media"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [CURRENTS_NEWS_API_KEY]
|
||||
---
|
||||
|
||||
# Currents News API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `apiKey` query parameter.
|
||||
|
||||
> Currents News API offers a real-time, RESTful news service that delivers global articles from 70+ countries in over 18 languages, supports keyword-based and SQL-style queries, and provides historical
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **query parameter** authentication via `apiKey`.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `CURRENTS_NEWS_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: data-for-seo
|
||||
version: "1.0.0"
|
||||
description: Data For SEO API — DataForSEO provides a comprehensive suite of RESTful APIs and data services that
|
||||
activation:
|
||||
keywords:
|
||||
- "data-for-seo"
|
||||
- "data for seo"
|
||||
- "seo"
|
||||
patterns:
|
||||
- "(?i)data.?for.?seo"
|
||||
tags:
|
||||
- "tools"
|
||||
- "seo"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DATA_FOR_SEO_BASE64_CREDENTIALS]
|
||||
---
|
||||
|
||||
# Data For SEO API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `Authorization` header — **never construct auth headers manually**.
|
||||
|
||||
> DataForSEO provides a comprehensive suite of RESTful APIs and data services that deliver search-engine results (SERP), keyword metrics, backlinks, app store info, site technical audits, and domain ana
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `Authorization` header.
|
||||
Format: `Authorization: Basic ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `DATA_FOR_SEO_BASE64_CREDENTIALS` — Basic Credential (Base64)
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: databox
|
||||
version: "1.0.0"
|
||||
description: Databox API — Databox is a business analytics platform that unifies metrics from multiple tool
|
||||
activation:
|
||||
keywords:
|
||||
- "databox"
|
||||
- "analytics"
|
||||
patterns:
|
||||
- "(?i)databox"
|
||||
tags:
|
||||
- "analytics"
|
||||
- "data"
|
||||
- ""
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DATABOX_API_KEY]
|
||||
---
|
||||
|
||||
# Databox API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `x-api-key` header — **never construct auth headers manually**.
|
||||
|
||||
> Databox is a business analytics platform that unifies metrics from multiple tools into customizable dashboards and alerts, helping teams track performance and make data-driven decisions in real time.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `x-api-key` header.
|
||||
Format: `x-api-key: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `DATABOX_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,85 @@
|
||||
---
|
||||
name: datadog
|
||||
version: "1.0.0"
|
||||
description: Datadog API — monitors, events, metrics, dashboards, incidents
|
||||
activation:
|
||||
keywords:
|
||||
- "datadog"
|
||||
- "monitoring"
|
||||
- "datadog alert"
|
||||
- "datadog monitor"
|
||||
exclude_keywords:
|
||||
- "sentry"
|
||||
- "grafana"
|
||||
- "new relic"
|
||||
patterns:
|
||||
- "(?i)datadog.*(monitor|alert|metric|dashboard|incident)"
|
||||
- "(?i)(create|list|mute).*monitor"
|
||||
tags:
|
||||
- "monitoring"
|
||||
- "observability"
|
||||
- "devops"
|
||||
max_context_tokens: 1500
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DATADOG_API_KEY, DATADOG_APP_KEY]
|
||||
---
|
||||
|
||||
# Datadog API
|
||||
|
||||
Use the `http` tool. Include both API and application keys as headers.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.datadoghq.com/api` (US1). Other sites: `api.us3.datadoghq.com`, `api.datadoghq.eu`, etc.
|
||||
|
||||
Required headers on every request:
|
||||
```
|
||||
headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}]
|
||||
```
|
||||
|
||||
## Actions
|
||||
|
||||
**List monitors:**
|
||||
```
|
||||
http(method="GET", url="https://api.datadoghq.com/api/v1/monitor?page=0&page_size=20", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}])
|
||||
```
|
||||
|
||||
**Get monitor:**
|
||||
```
|
||||
http(method="GET", url="https://api.datadoghq.com/api/v1/monitor/<monitor_id>", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}])
|
||||
```
|
||||
|
||||
**Mute monitor:**
|
||||
```
|
||||
http(method="POST", url="https://api.datadoghq.com/api/v1/monitor/<monitor_id>/mute", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}], body={"end": 1775000000})
|
||||
```
|
||||
|
||||
**Post event:**
|
||||
```
|
||||
http(method="POST", url="https://api.datadoghq.com/api/v1/events", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}], body={"title": "Deploy completed", "text": "Version 2.1.0 deployed to production", "alert_type": "info", "tags": ["env:production", "service:api"]})
|
||||
```
|
||||
|
||||
**Query metrics:**
|
||||
```
|
||||
http(method="GET", url="https://api.datadoghq.com/api/v1/query?from=1775000000&to=1775100000&query=avg:system.cpu.user{host:myhost}", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}])
|
||||
```
|
||||
|
||||
**List dashboards:**
|
||||
```
|
||||
http(method="GET", url="https://api.datadoghq.com/api/v1/dashboard/lists/manual", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}])
|
||||
```
|
||||
|
||||
**List incidents:**
|
||||
```
|
||||
http(method="GET", url="https://api.datadoghq.com/api/v2/incidents?page[size]=10", headers=[{"name": "DD-API-KEY", "value": "{DATADOG_API_KEY}"}, {"name": "DD-APPLICATION-KEY", "value": "{DATADOG_APP_KEY}"}])
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Monitor states: `OK`, `Alert`, `Warn`, `No Data`, `Unknown`.
|
||||
- Event alert types: `info`, `warning`, `error`, `success`.
|
||||
- Metric queries use Datadog query syntax: `avg:metric.name{tag:value}`.
|
||||
- Times are Unix timestamps (seconds).
|
||||
- `DD-API-KEY` alone suffices for posting events/metrics. Most reads need `DD-APPLICATION-KEY` too.
|
||||
@@ -0,0 +1,49 @@
|
||||
---
|
||||
name: deck-co
|
||||
version: "1.0.0"
|
||||
description: Deck.co API — Deck provides developer infrastructure for accessing credentialed user data from
|
||||
activation:
|
||||
keywords:
|
||||
- "deck-co"
|
||||
- "deck.co"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)deck.?co"
|
||||
tags:
|
||||
- "tools"
|
||||
- "ai"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DECK_CO_CLIENT_ID, DECK_CO_CLIENT_SECRET, DECK_CO_BASE_URL]
|
||||
---
|
||||
|
||||
# Deck.co API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `x-deck-client-id` header — **never construct auth headers manually**.
|
||||
|
||||
> Deck provides developer infrastructure for accessing credentialed user data from login‑gated websites as if there were an official API, enabling real‑time extraction, normalization, and write actions
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `x-deck-client-id` header.
|
||||
Format: `x-deck-client-id: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `DECK_CO_CLIENT_ID` — Client ID
|
||||
- `DECK_CO_CLIENT_SECRET` — Client Secret / API Key
|
||||
- `DECK_CO_BASE_URL` — Base URl
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: deep-seek
|
||||
version: "1.0.0"
|
||||
description: DeepSeek API — DeepSeek develops advanced large language models that deliver high-performance A
|
||||
activation:
|
||||
keywords:
|
||||
- "deep-seek"
|
||||
- "deepseek"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)deep.?seek"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DEEP_SEEK_API_KEY]
|
||||
---
|
||||
|
||||
# DeepSeek API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.deepseek.com`
|
||||
|
||||
## Actions
|
||||
|
||||
**Chat completion:**
|
||||
```
|
||||
http(method="POST", url="https://api.deepseek.com/chat/completions", body={"model": "deepseek-chat","messages": [{"role": "user","content": "Hello"}],"max_tokens": 1024})
|
||||
```
|
||||
|
||||
**List models:**
|
||||
```
|
||||
http(method="GET", url="https://api.deepseek.com/models")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- OpenAI-compatible API format.
|
||||
- Models: `deepseek-chat`, `deepseek-coder`, `deepseek-reasoner`.
|
||||
- Supports `stream: true` for streaming responses.
|
||||
- Temperature range: 0.0–2.0.
|
||||
@@ -0,0 +1,46 @@
|
||||
---
|
||||
name: deliveroo
|
||||
version: "1.0.0"
|
||||
description: Deliveroo API — Deliveroo operates a technology-driven online food delivery marketplace that con
|
||||
activation:
|
||||
keywords:
|
||||
- "deliveroo"
|
||||
- "food delivery"
|
||||
patterns:
|
||||
- "(?i)deliveroo"
|
||||
tags:
|
||||
- "tools"
|
||||
- "food-delivery"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DELIVEROO_CLIENT_ID, DELIVEROO_CLIENT_SECRET]
|
||||
---
|
||||
|
||||
# Deliveroo API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Deliveroo operates a technology-driven online food delivery marketplace that connects consumers with local restaurants, grocery and retail partners through its app, enabling on-demand ordering and rea
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `DELIVEROO_CLIENT_ID` — Client ID
|
||||
- `DELIVEROO_CLIENT_SECRET` — Client Secret
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,52 @@
|
||||
---
|
||||
name: diffbot
|
||||
version: "1.0.0"
|
||||
description: Diffbot API — Diffbot uses machine learning and computer vision to extract structured data fro
|
||||
activation:
|
||||
keywords:
|
||||
- "diffbot"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)diffbot"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DIFFBOT_API_KEY]
|
||||
---
|
||||
|
||||
# Diffbot API
|
||||
|
||||
Use the `http` tool. API key is automatically injected as `token` query parameter.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.diffbot.com/v3`
|
||||
|
||||
## Actions
|
||||
|
||||
**Analyze URL:**
|
||||
```
|
||||
http(method="GET", url="https://api.diffbot.com/v3/analyze?url=https://example.com/article&token={DIFFBOT_API_TOKEN}")
|
||||
```
|
||||
|
||||
**Extract article:**
|
||||
```
|
||||
http(method="GET", url="https://api.diffbot.com/v3/article?url=https://example.com/article&token={DIFFBOT_API_TOKEN}")
|
||||
```
|
||||
|
||||
**Extract product:**
|
||||
```
|
||||
http(method="GET", url="https://api.diffbot.com/v3/product?url=https://example.com/product&token={DIFFBOT_API_TOKEN}")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- `token` parameter is the API key.
|
||||
- Extraction types: `article`, `product`, `image`, `video`, `discussion`.
|
||||
- `/analyze` auto-detects the page type.
|
||||
- Add `&fields=` to select specific fields in response.
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
name: discord
|
||||
version: "1.0.0"
|
||||
description: Discord API — send messages, manage channels, guilds, reactions
|
||||
activation:
|
||||
keywords:
|
||||
- "discord"
|
||||
- "discord message"
|
||||
- "guild"
|
||||
- "discord channel"
|
||||
exclude_keywords:
|
||||
- "slack"
|
||||
- "teams"
|
||||
patterns:
|
||||
- "(?i)send.*discord"
|
||||
- "(?i)discord.*(message|channel|server|guild)"
|
||||
tags:
|
||||
- "messaging"
|
||||
- "communication"
|
||||
- "chat"
|
||||
max_context_tokens: 1500
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DISCORD_BOT_TOKEN]
|
||||
---
|
||||
|
||||
# Discord API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**. The system injects `Authorization: Bot {DISCORD_BOT_TOKEN}` for `discord.com` hosts.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://discord.com/api/v10`
|
||||
|
||||
## Actions
|
||||
|
||||
**Send message:**
|
||||
```
|
||||
http(method="POST", url="https://discord.com/api/v10/channels/<channel_id>/messages", body={"content": "Hello!"})
|
||||
```
|
||||
|
||||
**Send embed:**
|
||||
```
|
||||
http(method="POST", url="https://discord.com/api/v10/channels/<channel_id>/messages", body={"embeds": [{"title": "Title", "description": "Body", "color": 5814783}]})
|
||||
```
|
||||
|
||||
**Get channel messages:**
|
||||
```
|
||||
http(method="GET", url="https://discord.com/api/v10/channels/<channel_id>/messages?limit=50")
|
||||
```
|
||||
|
||||
**List guild channels:**
|
||||
```
|
||||
http(method="GET", url="https://discord.com/api/v10/guilds/<guild_id>/channels")
|
||||
```
|
||||
|
||||
**Get guild info:**
|
||||
```
|
||||
http(method="GET", url="https://discord.com/api/v10/guilds/<guild_id>")
|
||||
```
|
||||
|
||||
**Add reaction:**
|
||||
```
|
||||
http(method="PUT", url="https://discord.com/api/v10/channels/<channel_id>/messages/<message_id>/reactions/<emoji>/@me")
|
||||
```
|
||||
|
||||
**Create channel:**
|
||||
```
|
||||
http(method="POST", url="https://discord.com/api/v10/guilds/<guild_id>/channels", body={"name": "new-channel", "type": 0})
|
||||
```
|
||||
|
||||
**Get user:**
|
||||
```
|
||||
http(method="GET", url="https://discord.com/api/v10/users/@me")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Channel types: 0 = text, 2 = voice, 4 = category, 5 = announcement.
|
||||
- Embeds `color` is decimal (not hex). Convert: `0x58ACFF` → `5814783`.
|
||||
- Emoji in reactions: URL-encode unicode emoji (`%F0%9F%91%8D` for thumbsup) or use `name:id` for custom.
|
||||
- Rate limits: 50 requests/second. Check `X-RateLimit-Remaining` header.
|
||||
- Snowflake IDs are strings of digits (e.g., `"1234567890123456789"`).
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
name: dovetail
|
||||
version: "1.0.0"
|
||||
description: Dovetail API — Dovetail is an AI-native customer intelligence platform that centralises and syn
|
||||
activation:
|
||||
keywords:
|
||||
- "dovetail"
|
||||
- "cip"
|
||||
patterns:
|
||||
- "(?i)dovetail"
|
||||
tags:
|
||||
- "tools"
|
||||
- "cip"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DOVETAIL_API_TOKEN]
|
||||
---
|
||||
|
||||
# Dovetail API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Dovetail is an AI-native customer intelligence platform that centralises and synthesises feedback from interviews, support tickets, reviews and research data—helping teams uncover themes, drive produc
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `DOVETAIL_API_TOKEN` — API Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,82 @@
|
||||
---
|
||||
name: dropbox
|
||||
version: "1.0.0"
|
||||
description: Dropbox API v2 — files, folders, sharing, search
|
||||
activation:
|
||||
keywords:
|
||||
- "dropbox"
|
||||
- "dropbox file"
|
||||
exclude_keywords:
|
||||
- "google drive"
|
||||
- "box"
|
||||
- "onedrive"
|
||||
patterns:
|
||||
- "(?i)dropbox.*(file|folder|share|upload|download)"
|
||||
tags:
|
||||
- "file-storage"
|
||||
- "cloud-storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [DROPBOX_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Dropbox API v2
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.dropboxapi.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.dropboxapi.com/2`
|
||||
|
||||
## Actions
|
||||
|
||||
**List folder contents:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/list_folder", body={"path": "", "limit": 20})
|
||||
```
|
||||
Use `""` for root, `/path/to/folder` for subfolders.
|
||||
|
||||
**Search files:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/search_v2", body={"query": "report", "options": {"max_results": 20, "file_status": "active"}})
|
||||
```
|
||||
|
||||
**Get file metadata:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/get_metadata", body={"path": "/path/to/file.pdf"})
|
||||
```
|
||||
|
||||
**Create folder:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/create_folder_v2", body={"path": "/New Folder", "autorename": false})
|
||||
```
|
||||
|
||||
**Move file/folder:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/move_v2", body={"from_path": "/old/path.txt", "to_path": "/new/path.txt"})
|
||||
```
|
||||
|
||||
**Delete file/folder:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/files/delete_v2", body={"path": "/path/to/delete"})
|
||||
```
|
||||
|
||||
**Create shared link:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/sharing/create_shared_link_with_settings", body={"path": "/path/to/file.pdf", "settings": {"requested_visibility": "public"}})
|
||||
```
|
||||
|
||||
**Get account info:**
|
||||
```
|
||||
http(method="POST", url="https://api.dropboxapi.com/2/users/get_current_account")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Dropbox API v2 uses POST for everything (even reads) with JSON bodies.
|
||||
- Paths are lowercase, start with `/`. Root is empty string `""`.
|
||||
- `list_folder` returns `has_more` + `cursor`. Use `list_folder/continue` with `cursor` for pagination.
|
||||
- File downloads use `content.dropboxapi.com/2/files/download` with path in `Dropbox-API-Arg` header (not this API base).
|
||||
- Errors: `{"error_summary": "path/not_found/...", "error": {...}}`.
|
||||
@@ -0,0 +1,76 @@
|
||||
---
|
||||
name: elevenlabs
|
||||
version: "1.0.0"
|
||||
description: ElevenLabs API — text-to-speech, voices, voice cloning, audio generation
|
||||
activation:
|
||||
keywords:
|
||||
- "elevenlabs"
|
||||
- "text to speech"
|
||||
- "tts"
|
||||
- "voice"
|
||||
exclude_keywords:
|
||||
- "whisper"
|
||||
- "google tts"
|
||||
patterns:
|
||||
- "(?i)elevenlabs.*(voice|speech|audio|tts)"
|
||||
- "(?i)(generate|create|convert).*speech"
|
||||
- "(?i)text.to.speech"
|
||||
tags:
|
||||
- "ai"
|
||||
- "audio"
|
||||
- "tts"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [ELEVENLABS_API_KEY]
|
||||
---
|
||||
|
||||
# ElevenLabs API
|
||||
|
||||
Use the `http` tool. Include `xi-api-key` header. Audio responses should be saved to file.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.elevenlabs.io/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**Text to speech:**
|
||||
```
|
||||
http(method="POST", url="https://api.elevenlabs.io/v1/text-to-speech/<voice_id>", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}], body={"text": "Hello, how are you today?", "model_id": "eleven_multilingual_v2", "voice_settings": {"stability": 0.5, "similarity_boost": 0.75}}, save_to="/tmp/speech.mp3")
|
||||
```
|
||||
|
||||
**List voices:**
|
||||
```
|
||||
http(method="GET", url="https://api.elevenlabs.io/v1/voices", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Get voice:**
|
||||
```
|
||||
http(method="GET", url="https://api.elevenlabs.io/v1/voices/<voice_id>", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Get models:**
|
||||
```
|
||||
http(method="GET", url="https://api.elevenlabs.io/v1/models", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Get subscription info:**
|
||||
```
|
||||
http(method="GET", url="https://api.elevenlabs.io/v1/user/subscription", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}])
|
||||
```
|
||||
|
||||
**Get usage:**
|
||||
```
|
||||
http(method="GET", url="https://api.elevenlabs.io/v1/user", headers=[{"name": "xi-api-key", "value": "{ELEVENLABS_API_KEY}"}])
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- TTS returns raw audio bytes (mp3). Always use `save_to` to save the file.
|
||||
- Models: `eleven_multilingual_v2` (best quality), `eleven_turbo_v2_5` (low latency), `eleven_monolingual_v1`.
|
||||
- `stability` (0-1): lower = more expressive, higher = more consistent.
|
||||
- `similarity_boost` (0-1): higher = closer to original voice.
|
||||
- Popular premade voice IDs: check `GET /v1/voices` to list available options.
|
||||
- Character quota tracked per account. Check `character_count`/`character_limit` in user info.
|
||||
@@ -0,0 +1,64 @@
|
||||
---
|
||||
name: exa
|
||||
version: "1.0.0"
|
||||
description: Exa AI Search API — semantic search, neural search, content retrieval
|
||||
activation:
|
||||
keywords:
|
||||
- "exa"
|
||||
- "exa search"
|
||||
- "neural search"
|
||||
- "semantic search"
|
||||
exclude_keywords:
|
||||
- "google search"
|
||||
- "brave search"
|
||||
patterns:
|
||||
- "(?i)exa.*(search|find|content)"
|
||||
- "(?i)semantic search"
|
||||
tags:
|
||||
- "search"
|
||||
- "ai"
|
||||
max_context_tokens: 1000
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [EXA_API_KEY]
|
||||
---
|
||||
|
||||
# Exa Search API
|
||||
|
||||
Use the `http` tool. Include `x-api-key` header.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.exa.ai`
|
||||
|
||||
## Actions
|
||||
|
||||
**Search:**
|
||||
```
|
||||
http(method="POST", url="https://api.exa.ai/search", headers=[{"name": "x-api-key", "value": "{EXA_API_KEY}"}], body={"query": "best practices for RAG systems", "type": "neural", "numResults": 10, "useAutoprompt": true})
|
||||
```
|
||||
|
||||
**Search with content:**
|
||||
```
|
||||
http(method="POST", url="https://api.exa.ai/search", headers=[{"name": "x-api-key", "value": "{EXA_API_KEY}"}], body={"query": "recent advances in protein folding", "type": "neural", "numResults": 5, "contents": {"text": {"maxCharacters": 2000}, "highlights": true}})
|
||||
```
|
||||
|
||||
**Find similar pages:**
|
||||
```
|
||||
http(method="POST", url="https://api.exa.ai/findSimilar", headers=[{"name": "x-api-key", "value": "{EXA_API_KEY}"}], body={"url": "https://example.com/article", "numResults": 10, "contents": {"text": true}})
|
||||
```
|
||||
|
||||
**Get contents for URLs:**
|
||||
```
|
||||
http(method="POST", url="https://api.exa.ai/contents", headers=[{"name": "x-api-key", "value": "{EXA_API_KEY}"}], body={"ids": ["https://example.com/page1", "https://example.com/page2"], "text": {"maxCharacters": 5000}})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Search types: `neural` (semantic), `keyword` (traditional), `auto` (hybrid).
|
||||
- `useAutoprompt: true` lets Exa rewrite your query for better results.
|
||||
- `contents.text` can be `true` (full text) or `{"maxCharacters": N}`.
|
||||
- Domain filtering: `includeDomains: ["arxiv.org"]` or `excludeDomains: ["reddit.com"]`.
|
||||
- Date filtering: `startPublishedDate`, `endPublishedDate` (ISO 8601).
|
||||
- Results include `url`, `title`, `publishedDate`, `author`, `score`.
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
name: fathom
|
||||
version: "1.0.0"
|
||||
description: Fathom API — Fathom.ai is an AI-powered meeting assistant that automatically records
|
||||
activation:
|
||||
keywords:
|
||||
- "fathom"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)fathom"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
---
|
||||
|
||||
# Fathom API
|
||||
|
||||
Use the `http` tool. OAuth credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Fathom.ai is an AI-powered meeting assistant that automatically records, transcribes, and summarizes virtual meetings across platforms like Zoom, Google Meet, and Teams, extracting key points, decisio
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **OAuth 2.0**. The token is managed automatically — no manual auth setup required in API calls.
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,89 @@
|
||||
---
|
||||
name: figma
|
||||
version: "1.0.0"
|
||||
description: Figma API — files, components, comments, images, projects
|
||||
activation:
|
||||
keywords:
|
||||
- "figma"
|
||||
- "figma file"
|
||||
- "figma component"
|
||||
- "design"
|
||||
exclude_keywords:
|
||||
- "sketch"
|
||||
- "canva"
|
||||
patterns:
|
||||
- "(?i)figma.*(file|component|comment|image|project)"
|
||||
- "(?i)(export|inspect).*figma"
|
||||
tags:
|
||||
- "design"
|
||||
- "ui"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [FIGMA_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Figma API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected for `api.figma.com`.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.figma.com/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**Get file:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/files/<file_key>")
|
||||
```
|
||||
|
||||
**Get specific nodes:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/files/<file_key>/nodes?ids=<node_id1>,<node_id2>")
|
||||
```
|
||||
|
||||
**Export images:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/images/<file_key>?ids=<node_id>&format=png&scale=2")
|
||||
```
|
||||
|
||||
**List components:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/files/<file_key>/components")
|
||||
```
|
||||
|
||||
**List comments:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/files/<file_key>/comments")
|
||||
```
|
||||
|
||||
**Post comment:**
|
||||
```
|
||||
http(method="POST", url="https://api.figma.com/v1/files/<file_key>/comments", body={"message": "Looks good!", "client_meta": {"x": 100, "y": 200}})
|
||||
```
|
||||
|
||||
**List project files:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/projects/<project_id>/files")
|
||||
```
|
||||
|
||||
**List team projects:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/teams/<team_id>/projects")
|
||||
```
|
||||
|
||||
**Get file versions:**
|
||||
```
|
||||
http(method="GET", url="https://api.figma.com/v1/files/<file_key>/versions")
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- File key is from URL: `figma.com/file/<file_key>/File-Name`.
|
||||
- Node IDs use colon format: `"1:23"`. URL-encode as `1%3A23`.
|
||||
- Export formats: `jpg`, `png`, `svg`, `pdf`. Scale: 0.01 to 4.
|
||||
- Image export returns URLs (temporary, valid ~14 days).
|
||||
- Full file response can be very large — use `/nodes` endpoint for specific sections.
|
||||
- Rate limit: 30 requests/minute.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: fireberry
|
||||
version: "1.0.0"
|
||||
description: Fireberry API — A unified CRM platform designed to bring sales, marketing
|
||||
activation:
|
||||
keywords:
|
||||
- "fireberry"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)fireberry"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [FIREBERRY_ACCESS_TOKEN]
|
||||
---
|
||||
|
||||
# Fireberry API
|
||||
|
||||
Use the `http` tool. API key is automatically injected via `tokenid` header — **never construct auth headers manually**.
|
||||
|
||||
> A unified CRM platform designed to bring sales, marketing, and service data into one customizable hub, Fireberry offers businesses of all sizes AI-assisted automation, real-time insights, and flexible
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **API Key** authentication via the `tokenid` header.
|
||||
Format: `tokenid: ...`
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `FIREBERRY_ACCESS_TOKEN` — Access Token
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
name: firecrawl
|
||||
version: "1.0.0"
|
||||
description: Firecrawl API — Firecrawl is a website crawling and indexing tool designed to help developers an
|
||||
activation:
|
||||
keywords:
|
||||
- "firecrawl"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)firecrawl"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [FIRECRAWL_API_KEY]
|
||||
---
|
||||
|
||||
# Firecrawl API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
## Base URL
|
||||
|
||||
`https://api.firecrawl.dev/v1`
|
||||
|
||||
## Actions
|
||||
|
||||
**Scrape URL:**
|
||||
```
|
||||
http(method="POST", url="https://api.firecrawl.dev/v1/scrape", body={"url": "https://example.com","formats": ["markdown"]})
|
||||
```
|
||||
|
||||
**Crawl website:**
|
||||
```
|
||||
http(method="POST", url="https://api.firecrawl.dev/v1/crawl", body={"url": "https://example.com","limit": 10})
|
||||
```
|
||||
|
||||
**Get crawl status:**
|
||||
```
|
||||
http(method="GET", url="https://api.firecrawl.dev/v1/crawl/{crawl_id}")
|
||||
```
|
||||
|
||||
**Search:**
|
||||
```
|
||||
http(method="POST", url="https://api.firecrawl.dev/v1/search", body={"query": "AI news","limit": 5})
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- Formats: `markdown`, `html`, `rawHtml`, `links`, `screenshot`.
|
||||
- Crawl is async — poll status with GET.
|
||||
- `includePaths`/`excludePaths` filter crawled URLs (glob patterns).
|
||||
- `waitFor` (ms) waits for JS rendering.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
name: fireflies-ai
|
||||
version: "1.0.0"
|
||||
description: Fireflies.ai API — Fireflies.ai is an AI meeting assistant that transcribes, summarizes
|
||||
activation:
|
||||
keywords:
|
||||
- "fireflies-ai"
|
||||
- "fireflies.ai"
|
||||
- "ai"
|
||||
patterns:
|
||||
- "(?i)fireflies.?ai"
|
||||
tags:
|
||||
- "ai"
|
||||
- "machine-learning"
|
||||
- "storage"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [FIREFLIESAI_API_KEY]
|
||||
---
|
||||
|
||||
# Fireflies.ai API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Fireflies.ai is an AI meeting assistant that transcribes, summarizes, and analyzes conversations across video conferencing platforms to improve productivity and collaboration.
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `FIREFLIESAI_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
name: folk-app
|
||||
version: "1.0.0"
|
||||
description: Folk.app API — Folk is a simple, AI-powered CRM designed for service businesses
|
||||
activation:
|
||||
keywords:
|
||||
- "folk-app"
|
||||
- "folk.app"
|
||||
- "crm"
|
||||
patterns:
|
||||
- "(?i)folk.?app"
|
||||
tags:
|
||||
- "crm"
|
||||
- "sales"
|
||||
- "contacts"
|
||||
- "CRM"
|
||||
max_context_tokens: 1200
|
||||
metadata:
|
||||
openclaw:
|
||||
requires:
|
||||
env: [FOLK_APP_API_KEY]
|
||||
---
|
||||
|
||||
# Folk.app API
|
||||
|
||||
Use the `http` tool. Credentials are automatically injected — **never construct Authorization headers manually**.
|
||||
|
||||
> Folk is a simple, AI-powered CRM designed for service businesses. It features spreadsheet-like interface, automated contact management, Chrome extension for one-click imports, Gmail integration, and p
|
||||
|
||||
## Authentication
|
||||
|
||||
This integration uses **Bearer Token** authentication. The token is injected automatically into the `Authorization` header.
|
||||
|
||||
## Required Credentials
|
||||
|
||||
- `FOLK_APP_API_KEY` — API Key
|
||||
|
||||
## Usage
|
||||
|
||||
Use the `http` tool to call this API. Example:
|
||||
```
|
||||
http(method="GET", url="<api_base_url>/endpoint")
|
||||
```
|
||||
|
||||
## Common Mistakes
|
||||
|
||||
- Do NOT add Authorization headers — automatically injected by the credential system.
|
||||
- Always use HTTPS URLs.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user