Skip to main content

Introduction

For agent-led development, CreatorDB now supports skills based on our API that can be called by AI agents like Claude. This allows you to retrieve creator or sponsoring brand data from CreatorDB in a more interactive and dynamic way, using natural language prompts. In this guide, we’ll walk you through how to set up and use the CreatorDB skills with Claude Code, including examples of how to query the CreatorDB API for specific creator information or to build an outreach list of potential creator partners for a campaign. The diagram below shows how a natural-language prompt is routed to a skill and then to CreatorDB API endpoints. Flow diagram: a user prompt enters Claude Code, the matching CreatorDB skill is selected, the skill calls one or more CreatorDB API endpoints, and the response is returned to the user. Fig. 1: Workflow for calling CreatorDB API via CreatorDB skills.

Available CreatorDB skills

Skill descriptions and supported platforms

  • Subtitles are YouTube-only.
  • Sponsored-content detection covers YouTube and Instagram only. There is no /tiktok/sponsorship endpoint, and TikTok creators are not represented in the /sponsor/* endpoints.
  • Topics are YouTube-only. Niches are available for all three platforms.
  • The category and language fields are returned for YouTube content only. TikTok content-search responses also omit the sponsorship fields (isSponsored, partneredBrands) returned for YouTube and Instagram.
  • Rate-card estimates in /{platform}/profile are YouTube-only.

Skills and primary API endpoints they call

  • Supported platforms and primary endpoints are based on the current CreatorDB API version and may be updated as new features are added. Check the CreatorDB API documentation for the latest information on available endpoints and supported platforms.

System requirements

  • A valid CreatorDB API key. Contact sales@creatordb.app to obtain one.
  • A code editor or terminal installed on your device, for example Visual Studio Code.
  • A Claude account that is Pro tier or above that supports Claude Code. For details, see Claude Pricing Plans.
  • Claude Code installed and set up on your device. For details, see Claude Code Docs.

Installing CreatorDB skills

To use the CreatorDB API with Claude, you need to install the CreatorDB skills on to your device. Follow these steps:
1

Launch Claude Code.

a. Open your code editor or terminal.
b. Launch Claude Code by running the command claude.
c. Log in to your Claude account.
2

Install CreatorDB skills.

Follow the instructions for your operating system to add CreatorDB skills to your Claude Code:
Run the commands in the following instructions:
a. Create the user-level skills directory if it doesn’t exist:
b. Pull each skill from the CreatorDB document site.
c. Verify that every SKILL.md was downloaded with a non-zero size — a 0-byte file or a missing-file error means curl was blocked or the URL changed:
Each row should show a file size of several kilobytes. If any file is 0 bytes or missing, re-run step b.

API key handling

Always keep your API key confidential and do not share it publicly or hard-code it in any scripts that may be shared. If you believe your API key has been compromised, contact CreatorDB support at support@creatordb.app immediately to have it revoked and a new one issued.
When you run a query that requires calling the CreatorDB API, Claude Code will prompt you to enter your API key if you haven’t already provided it. Here’s how to handle your API key securely:
  1. When your Claude Code AI agent requests access to the CreatorDB API, you should ask it to create an environment variable for your API key. Never paste your API key into the chat session, as it will be stored in the system logs and chat history.
  2. Claude Code will store your API key securely in its environment variables for the duration of your session, so you won’t need to enter it again for subsequent queries.
  3. If you need to update or change your API key, you can do so by updating the environment variable in your terminal or code editor where Claude Code is running. Run the appropriate command for your operating system to set the YOUR_API_KEY environment variable to your new API key:

Verify installation of CreatorDB skills

After installing CreatorDB skills, follow the instructions below to check the skills have been installed successfully.
1

Restart Claude Code.

a. Exit Claude Code by pressing (Ctrl +C).
b. Relaunch Claude to rescan the skills directory.
2

Run smoke tests.

Responses below are illustrative reconstructions, not verbatim terminal output — exact wording, table layout, and credit numbers will vary across runs.
Run the following smoke-test prompts to verify CreatorDB skills are correctly installed:
a. Skill discovery: The following prompt proves Claude Code can find the skills without making an API call. Claude Code should return all CreatorDB skills with one-line descriptions.
b. End-to-end with zero credit cost: A prompt that confirms the API key flow works without spending credits. The test should route to the account skill and return your account balance snapshot.

Troubleshooting

If you encounter any issues while using the CreatorDB API with Claude Code or ChatGPT, here are some troubleshooting steps you can take:
  1. Check API credentials: Ensure that your API key is correctly set up in your environment variables and that you have the necessary permissions to access the endpoints you’re trying to use.
  2. Check for errors in the response: If you receive an error response from the API, review the error message for clues about what went wrong. Common issues include invalid parameters, rate limits, or missing data.
  3. Contact support: If you’re still having trouble, reach out to CreatorDB support for assistance. Provide them with details about the issue, including any error messages and the steps you’ve taken to troubleshoot.

Common errors and solutions

Cause: This may be caused by blocked curl, network proxy issues, wrong URL, or the .well-known path moved.

Fix: Pull each skill from the CreatorDB document site again. If the issue persists, check your network connectivity to the https://docs.creatordb.app and check the path returns content via the browser.
Cause: An invalid key response may be caused by typos, wrong API key, or the key was revoked.

Fix: You can contact sales@creatordb.app to verify the key is still active. Also try reconfiguring the env var (export YOUR_API_KEY=...).
Cause: The env var is not persisted.

Fix: Add export YOUR_API_KEY=... to ~/.zshrc or ~/.bashrc (macOS/Linux), or add to user env var (Windows).
Claude Code stores the key for the current session only if not exported.
Cause: Your prompt phrasing matches multiple skills descriptions.

Fix: Explicitly name the skill in the prompt. For example, “use the brand-sponsorship skill to…”, or rephrase to use the canonical trigger words from the skill description.
Cause: Your filter criteria might be too narrow, the niche or category doesn’t exist in CreatorDB’s supported list, or the location filter doesn’t match.

Fix: Relax your filter criteria or try a broader search and narrow down results. You can also ask Claude Code to list available filters (“show me what’s available”) before applying.
Cause: CreatorDB might not have the subtitles for that video yet, since it may take a few days for the system to obtain the subtitles.

Fix: Try getting the subtitles of an older video first, or try again a few days later.
Cause: The working directory isn’t writable, or Claude Code lacks the file-system permission.

Fix: Run Claude Code from a writable directory, for example your Desktop or project folder. Grant Claude Code disk access to your operating system’s settings.
Last modified on August 6, 2026