Overview
By Starcovery. Updated .
What Starcovery does, the entry point of its web app, REST API, MCP server, and CLI, and where each part of the Starcovery docs lives.
Starcovery runs a creator campaign from a brief: find Instagram and TikTok creators, hire them, cross-post, measure, and pay out. Search ranks creators for the brief and shows sample videos.
Agents call search, campaigns, and credits over HTTP, Model Context Protocol (MCP), or the CLI. Humans use the same product from the web.
Find your way
- Get started: the Quickstart runs a first search with no account, and Authentication covers the credential each interface takes.
- Find creators: Write a creator brief, then find creators who post about a topic, on TikTok in one country, or in one follower tier, check their audience and engagement, find their email address, and share a shortlist.
- Run campaigns: Run a creator campaign, choose the pay per creator, and pay creators.
- Connect an agent: Add creator search to an AI agent over MCP, in ChatGPT, or in Microsoft 365 Copilot.
- Reference: the API reference, Search, Campaigns, the CLI, API versioning, and Report feedback.
- Billing: Pay for API calls without a subscription covers credits, the free daily uses, and what each action costs.
Entry points for each surface
Each surface has one entry point.
| Surface | Entry point |
|---|---|
| Web | www.starcovery.com |
| REST API | GET https://www.starcovery.com/api/search?q=coffee |
| MCP (Streamable HTTP) | https://www.starcovery.com/api/mcp |
| CLI | npx starcovery search searchCreators --q coffee |
Search spend
Search spend depends on the caller.
- Unsigned callers need no credential and get 100 uses per UTC day per IP.
- Identified callers get 200 uses per UTC day per user, and the members of one organization share at most 200 between them. Past either limit, they spend prepaid credits.
- The uses refill at midnight UTC.
- A search through the API is one use, and a thread turn is one use plus one for each new search and each exclusion it runs, so a new search typed on the website is two.
Each identified use past either limit spends one prepaid credit. See Pay for API calls without a subscription.
Machine discovery
Agents find Starcovery's machine surfaces through these documents and conventions.
- OpenAPI 3.1 for REST: openapi.json
- RFC 9727 API catalog:
https://www.starcovery.com/.well-known/api-catalog - Agent instruction file: llms.txt
- MCP server card:
https://www.starcovery.com/api/mcp/server-card - Agent skills index:
https://www.starcovery.com/.well-known/agent-skills/index.json - Protected resource metadata:
https://www.starcovery.com/.well-known/oauth-protected-resource - Authorization server metadata:
https://www.starcovery.com/.well-known/oauth-authorization-server - Markdown for any Starcovery marketing page: append
.mdto the URL, or sendAccept: text/markdown - JSON envelope for any Starcovery marketing page: append
.jsonto the URL. The response is{ "markdown": "...", "path": "/<page>", "source": "https://www.starcovery.com/<page>" }. The.jsonsuffix rule excludes/openapi.json, which returns the OpenAPI document. - HTML responses set an
x-agent-hintresponse header that points agents at the.mdand.jsonpage variants and the/agentsand/openapi.jsondiscovery endpoints.