Skip to content

Changelog

Each change to Starcovery that a customer or an agent can see, grouped by the UTC day it shipped, newest day first.

New Campaign opens the Search door

New Campaign and the first-run composer on /home open the same door as Search: paste your company website or describe who you want, and the search runs on /app with the creators whose reels fit. Hire These Creators starts the campaign with the ones you pick, so no empty campaign page is created from a first message any more. A campaign page with no creators yet carries the same door in its next-step panel, already adding to that campaign.

The changelog feed names each entry’s day

Each entry in the changelog feed names the UTC day it shipped as its category, such as "Oct 17, 2026", the same day /changelog groups it under, so a feed reader can group the entries by day. Entry ids stay as they were, so no entry shows again as new.

The campaign page leads with its next step

A campaign page now opens with one panel: which step the campaign is on, the step's line, and its one button, over a seven-segment strip under Find, Hire, and Pay Out. The seven-row Steps list, the Status card, and the Next step chip are gone, and the assistant pane no longer repeats the campaign's own next step as a to-do. The rail reads the proposal terms (pay, posting day, platform, disclosure), the money a funding step asks for, the brief, and the campaign's status, visibility, and creation day as rows. Edit Proposal sits beside the terms, and an empty Files section no longer carries a sentence.

One token endpoint in both discovery documents

/.well-known/openid-configuration now names the same token endpoint and grants as /.well-known/oauth-authorization-server: token_endpoint is https://www.starcovery.com/oauth2/token, and grant_types_supported adds urn:workos:agent-auth:grant-type:claim and urn:ietf:params:oauth:grant-type:jwt-bearer. It named /api/auth/oauth2/token with only authorization_code and refresh_token before. /api/auth/oauth2/token still answers authorization_code and refresh_token, so a client that read the old value keeps working.

private_key_jwt and DPoP at the advertised token endpoint

The token endpoint that /.well-known/oauth-authorization-server names, https://www.starcovery.com/oauth2/token, accepts a private_key_jwt client assertion whose aud is that URL. It answered 401 invalid_client before, and only the issuer or /api/auth/oauth2/token worked as aud there. A DPoP proof sent to /oauth2/token can name that URL as htu again; it answered 400 invalid_dpop_proof before. Assertions for the issuer or /api/auth/oauth2/token still work.

Platform and tier in any letter case

GET /api/search, the MCP search_creators tool, the campaign generate request, and the CLI --platform and --tier flags take a platform code or a follower tier in any letter case, as they take a country code, so platform=TT and --tier Nano+ search the same creators as tt and nano+. The search reads each value as its lowercase form, and the published schemas keep the list of platforms and tiers. A value outside those lists still answers 400 invalid_query with the same message.

Filter the campaign list by status

GET /api/campaigns takes a status query parameter, draft, active, or archived, and lists only the campaigns of the organization in that status. It ignored status before and listed every campaign. A status value outside those three answers 400 invalid_query. Without status the list still holds every campaign of the organization.

Campaign dates take any offset at midnight UTC

A campaign's creator posting date and declassifying date over REST and MCP take any RFC 3339 date-time that is the start of a UTC calendar day, such as 2026-12-01T00:00:00Z or 2026-11-30T19:00:00-05:00, and the server reads the day from that instant. A negative offset at midnight UTC was refused before. Any other instant, a local midnight such as 2026-12-01T00:00:00+09:00 among them, is still refused with 400 invalid_campaign_terms. The descriptions in /openapi.json and in each MCP tool now state the rule, and the 2026-10-07 entry on date-time fields shows 2026-12-01T00:00:00Z as its example.

Narrowed step names only the bounds a filter set

The Refined the search card's Narrowed step now lists only the follower bounds the narrowing set. After "only creators with under 50k followers" on a search of any follower size, the step reads "Up to 49,999 followers" and the creator count, with no "1,000+ followers" chip. Every search already holds only creators with at least 1,000 followers, so that floor was never a bound the narrowing set. The chip stays for a filter that sets a floor, such as "more than 10K followers".

A platform the search already covers adds nothing

A Thread message that asks only to add a platform the search already covers, and nothing else, such as "also TikTok creators" after a search on Instagram and TikTok, now runs no search and changes nothing: the reply says that the search already covers TikTok, and the creators on screen, the Search plan, and the count line stay as they are. Before, the assistant ran the same search again and described the difference between the two runs as creators it added and left out.

The CLI takes a campaign date as a YYYY-MM-DD day

The starcovery campaigns create and update commands take --creator-posting-date and --embargo-until as a YYYY-MM-DD calendar day in UTC, the shape the campaign stores, and send it as midnight UTC. An RFC 3339 date-time at midnight UTC still works. The help names the day form in place of <iso8601>, and a value in neither shape is refused as such before any request.

Country codes in either letter case

GET /api/search, the MCP search_creators tool, the campaign generate request, and the CLI --country flag take an ISO 3166-1 alpha-2 country code in either letter case, so --country US and country=US search the same creators as us. The search reads the code as its lowercase form, and the published schemas keep the list of codes. A code that names no country still answers 400 invalid_query, now with the message "Expected an ISO 3166-1 alpha-2 country code, such as us or id".

A wrong method on a REST path answers 405 with Allow

A REST path called with a method it does not take, such as GET on /api/search/enrich, answers 405 method_not_allowed with an Allow header that names the methods the path takes. It answered 404 not_found before, as if the path did not exist. A path the API does not have still answers 404. llms.txt names the method of the REST search and shortlist enrich endpoints it lists.

The assistant reads the order of the results

The assistant on /app reads the creators in the order the page shows them, in the view and sort you picked. Ask "which creator comes first?" or "who is third in the table?" and it names that creator. To save creators by their place to a List or add them to a campaign, such as "add the first three to a List", it names them and asks you to select them first, because it saves and adds only the creators you select.

The assistant counts creators as the results show them

The assistant on /app counts and names creators the way the results show them. A creator whose Instagram and TikTok profiles link to each other fills one row, and the assistant now counts that creator once, names both handles, and reads the figures of the profile with more followers, so its "50 creators found" on the Refined the search card matches the count line under the brief. Asking for "only the best 10" keeps ten rows.

One row per handle in the Handles pane

The Handles pane in Settings lists each handle once, with the state of its latest claim. Renewing a lapsed handle starts a new claim that reads In review until the Starcovery team approves it, and a claim restarted after a rejection replaces the Rejected row.

A claim never moves between organizations. When another organization's claim on a handle expired, starting a claim on that handle opens a new claim and leaves the other organization's claim in its Handles pane as Expired.

A takedown of a handle revokes its claim at once. A signed hire on that handle can still be paid: the hire counts toward your payout setup in place of the handle. Starting a claim on a handle a takedown covers now says so, instead of asking you to check the spelling, and REST answers 410 with the error taken_down.

The Search plan keeps every filter and narrowing

A Thread on /app keeps its search as one set of facts: the words that describe the creators, the platform, the country, the follower tier, what it leaves out, and each narrowing on average views, engagement, verified accounts, or the best-fit few. The Search plan card shows a row for each narrowing, and its Brief row holds only the words that describe the creators, so "only Instagram creators" after "also TikTok creators" reads Instagram beside a brief that names no platform. Removing a chip, switching the platform, replacing the follower tier, or asking for more creators like these keeps every other filter and narrowing, so "more creators like these" after "only those above 100K average views" adds only creators at 100K average views and above. Recent lists two Threads of the same brief with different filters as two searches.

A follow-up that narrows and searches at once no longer says it will only narrow

When a Thread follow-up asks for a follower tier the creators on screen cannot hold, and the assistant tries to narrow them and runs the new search in the same step, the Refined the search card shows no line above it. Before, that line could say it would narrow the creators on screen and spend one use, while the turn ran a new search and spent a second use. The reply below the Search plan card still says that a new search ran.

A follow-up that runs a new search for a follower tier no longer first says it will narrow

When a Thread follow-up asks for a follower tier the creators on screen cannot hold, such as "only creators with over 1M followers" after "only creators with under 10k followers", the line above the Refined the search card is the one written for that new search, never one that says it will narrow the creators on screen. Before, that line could say it would narrow the creators on screen and spend one use, while the reply below the Search plan card said a new search ran instead.

A first brief costs the same from any page

A first brief sent from the assistant on Home or another page now runs the same way as on /app. Its results start loading while Starcovery reads the brief's platform, country, and follower size, and it costs the same: 1 use for the turn plus 1 search, or 2 searches when the brief names a platform, country, or follower size. Usage History lists it the same way too. A first message that asks for something besides finding creators, such as a campaign or a payout, still goes to the assistant.

One set of contact labels across results and campaigns

Contact chips say one thing everywhere. Email on file means Starcovery holds an address you have not revealed; on a campaign page an address the creator published reads Published email and one found by web research Researched email. A creator with no address reads No email on file in the Table, the Creators cards, the Map, and on the campaign page alike, and Export CSV and the CLI write the same words.

Report a vulnerability and earn a reward

Security and Bug Bounty explains how to report a security vulnerability and the rules of the Starcovery bug bounty program. An eligible report pays $25 to $500 in cash through Stripe, or $100 to $5,000 in Starcovery credit, by severity. The footer links the page under Legal.

Search creators in every country

The country filter covers every country, not only the ten it covered before. A brief that names where the creators are based, such as "Indonesian creators" or "creators in Mexico", sets that country, and a Thread message that asks for a new search in any country runs the search with that country. On /app, the Country button beside the filter chips opens a list of every country with its flag. Typing finds a country by its name, its code, or another name it goes by, and forgives a typo, so "korea" finds Korea, "uk" finds the United Kingdom, and "indo" finds Indonesia. Choosing a country sets the filter and reloads the results, as removing a chip does. GET /api/search, the MCP search_creators tool, and the CLI --country flag take any lowercase ISO 3166-1 alpha-2 code, such as id or mx.

One way to say a creator has no view count

A creator with no view count now reads "No view count" everywhere their views would show: the Table, the Creators cards, the Map point and its inspector, the Reels caption, and the header of a creator page. The views of a creator found on both Instagram and TikTok belong to each profile, so a reel shows the views of the profile it plays from. The Table and Export CSV share one set of columns: the CSV lists the same columns in the same order, so its first column is now named Creator instead of Name, with Followers and Average views as plain digits, and the Table names each handle in its Handles column.

A failed MCP thread turn is a tool error

The MCP thread_turn tool marks a turn that ends with status failed as a tool error (isError). The result text still holds the turn as JSON, with its error and the threadId for the next turn. Before, a failed turn was returned as a successful result.

Dates show their year and deadlines their time

Every date in the app shows its year, so Oct 3 of two years no longer reads the same on Lists, Usage, Billing, and a creator page. A deadline shows its time: Code expires and Verified until in Settings > Handles read like the invitation Expires, such as Oct 15, 2026, 11:59 PM UTC. An amount of money reads with its cents everywhere, so a payout, a pay per creator, and a balance show $300.00 on every page and in the CLI.

A place where creators do not sell sets no country

A place that names where creators do not sell no longer sets the Country of a first brief. "skincare creators not selling products in Korea" now always reads Country Anywhere with no country chip, the same as an audience place such as "for a US audience". To search for creators who live in Korea, write "skincare creators in Korea not selling products".

Creator page posts say when a post has no view count

A post under Recent posts on a creator page with no view count reads "Views No view count", the words the Table, the Creators cards, and the Map on /app use. It used to show the Views label with no figure beside it, so the likes after it read as the post's views.

A later narrowing keeps the narrowed country on the Search plan card

After a Thread follow-up narrows the results on screen to a home country outside the ten, such as "only creators based in Mexico", a later follow-up that narrows them again without naming a country, such as "only those above 100K average views", adds a Search plan card whose Country still reads that country. Before, that card read "Anywhere".

Use Starcovery in ChatGPT

/ai has a ChatGPT card. On a ChatGPT Business, Enterprise, or Edu plan, add Starcovery as a custom MCP server, sign in to Starcovery, and pick Starcovery in a chat to find creators from a brief.

The ChatGPT guide has the steps, with a screenshot of each.

Reasons for a payout below the contract payment

A payout Starcovery pays below the contract payment now carries the reason for the difference. The hired organization reads it on Hired On and Payouts, and the hiring organization under the creator on the campaign page, on the campaign's funding page, and as the shortfall reason of each hire in the REST and MCP campaign reads.

Starcovery records no paid payout below the contract payment without a reason, and still pays no more than the contract payment.

A proposal to a taken-down handle cannot be accepted

On the Hired On tab of Starcovery Proposals, Accept on a proposal to a handle a takedown covers is refused with a message, and Decline still records. Before, the acceptance was recorded although no hire can sign a taken-down creator.

Funding leaves out a taken-down creator

The funding quote on a campaign, and the funding request it sends, leave out a creator whose handle a takedown covers. Before, the quote counted that creator's acceptance although no hire can sign a taken-down creator, so the money for that creator could only come back as a refund.

Save Proposal with no change saves nothing

Save Proposal with no change opens the campaign page and saves nothing. Before, it marked the campaign as updated, which moved it up the campaign lists and made a proposal form open in another tab refuse its next save as out of date.

Assistant answers view questions for every creator on screen

A Thread question about the average views or the engagement on views of the creators on screen, such as "name the three creators with the highest engagement on views", now answers from every creator on screen when the message asks only that question or also narrows with a filter. Before, the assistant answered from the five best-fit creators alone and could miss higher figures the Table shows.

Adding a platform updates the Search plan brief

A Thread message that adds the other platform, such as "also add more creators on TikTok", now writes both platforms into the Search plan Brief when the added platform's search finds creators. Before, the Brief named only TikTok beside Platform Instagram and TikTok, although the results hold both.

A blank search brief names the visible-character rule

GET /api/search, the MCP search_creators and save_list tools, and the CLI search refuse an empty or whitespace-only brief with "Expected a value with a visible character". Such a brief was refused before with "Expected a value with a length of at least 1".

The Search plan card names a country a follow-up narrowed to

A Thread follow-up that narrows the results on screen to a home country outside the ten, such as "only creators based in Mexico", adds a Search plan card whose Country reads that country, as the turn's "Narrowed the results on screen" step does. Before, the card read "Anywhere". The country gets no chip, and a later search does not keep it.

Platform refinements narrow the results on screen

A Thread message that narrows the results to one platform, such as "only TikTok creators", after a search on Instagram and TikTok now narrows the creators on screen with no new search and spends one use. Before, the assistant sometimes ran a new search on that platform, which replaced the results and spent another use.

A nationality before a niche keeps Country beside an audience phrase

A brief that puts a nationality before a niche of one or two words and also names an audience of the same country, such as "Korean food creators for a Korean audience", sets the Country filter to that country, as "Korean creators for a Korean audience" already did. Before, the audience phrase cleared Country to Anywhere.

Hire These Creators adds to the campaign of the same brief

On /app, Hire These Creators adds the selected creators to the campaign that an earlier press on the same brief and filters created, from any thread, instead of creating a new numbered campaign. A brief or filters that differ still create a new campaign, and a campaign that takes no more creators starts a new one.

Follower ceilings read as a count

A follower filter that sets only a ceiling now names that ceiling. After "under 50k followers", the Search plan Followers row and the composer chip read "Up to 49,999 followers", the same bound the Refined the search card shows, in place of "Up to Micro 1K to 50K". Tier filters with a floor and a ceiling keep their names, such as "Micro 10K to 50K".

Campaign dates stop 5 years ahead

Save Proposal, the REST campaign endpoints, the MCP campaign tools, and the CLI refuse a creator posting date or a declassifying date more than 5 years after today in UTC. The terms form shows the refusal under the field, and the API answers 400 invalid_campaign_terms with the message. Earlier, a date in year 9999 saved.

A nationality before a niche sets Country

A brief that puts the nationality of one of the ten search countries before a niche, such as "Indian food creators on Instagram", sets the Country filter to that country on every run, as "Indian creators" and "Korean food creators" already did. Before, some runs read "Indian food" as a cuisine and left Country on Anywhere.

Hired on shows the paid amount

The Paid column of the Hired on table on /proposals names the recorded payout amount beside the paid date, as "Paid $200 Oct 12, 2026, UTC". Payment stays the contract compensation, so a payout below the compensation no longer reads as the full payment.

Submitting a shoutout post confirms it

Submit Post in the Shoutout settings now shows a Post submitted line with the post link and its status after a submission is accepted, and a screen reader announces it. Before, the link field emptied and a row joined Your submitted posts with no line that stated the result.

The Table view lists every evidence line

The Evidence column of the Table view on /app now lists every evidence line of a creator, one under the other. Before, the column showed only the first line, while the Creators view and Export CSV showed all of them.

Payouts shows amounts in the same format as Hired On

The Paid to date card and the Amount column of the Transfers table on /payouts drop the cents of a whole-dollar amount, as the Hired on table on /proposals does, so a $500 payout reads "$500" on both pages in place of "$500.00".

The reply reports the exclusion a search ran

When a Thread search runs a Brief that leaves a kind of creator out, such as "coffee creators on TikTok in the UK, excluding brand accounts" after a platform switch, the assistant reply now says the new search left that kind out. Before, the reply sometimes said the exclusion was not run on the new results, though the search had run it.

The CLI refuses a blank --thread value

The starcovery thread command with an empty or blank --thread value, such as one from an unset shell variable, prints "missing value for --thread" and exits 1 before any request. It used to open a new Thread and send the message there. Leaving out --thread still opens a new Thread.

The Reveal Contact dialog stays open while the reveal runs

On a creator page, the Reveal Contact dialog stays open while the reveal runs: Esc, a press outside the dialog, Close, and Cancel do nothing until it answers, so the dialog shows the answer, the revealed address, a refusal, or the failure line, before it closes.

CLI error and warning colors follow standard error

The starcovery CLI colors its error and warning lines when standard error is a terminal, and writes them without color codes when standard error goes to a file or a pipe. It decided from standard output before, so a search piped to jq showed errors uncolored, and a run that sent standard error to a log file wrote color codes into the log.

Hand-pick reply addresses are checked before Send

The hand-pick row under the search results of a Thread on /app refuses a reply address longer than 254 characters in the Email field, with "Enter a full email address, such as name@company.com." Such an address passed the field before, and Send failed with "The request did not send. Send it again." on every attempt.

API key names need a visible character

POST /api/keys and the MCP create_api_key tool refuse a key name made only of invisible characters, such as zero-width spaces, with "Expected a value with a visible character". Such a name was accepted before and showed as a blank label in the Settings key table.

Workspace pages show flat sections with smaller corners

Home, Campaigns, Usage, Payouts, Proposals, Settings, the Activity panel, and creator pages show their sections flat under each heading, with hairlines between rows, in place of filled and bordered cards. Corners are 4px across these pages, menus, and notices, and the marketing pages use the same corners.

A platform switch updates the Search plan brief

A Thread message that switches to the other platform, such as "only Instagram creators" after a TikTok search, now runs a new search whose Search plan Brief names the new platform. Before, the Brief sometimes kept the old platform, such as "fitness creators on TikTok in the United States" beside Platform Instagram.

Export CSV includes niche, evidence, and signal

Export CSV in the selection bar menu on /app adds Niche, Evidence, and Signal columns after Contact, with the values the Table shows for each selected creator. Evidence joins every evidence line with " | ". A column is empty for a creator Starcovery has not read yet, and the export is free.

More Options names an invalid declassifying date

On the proposal form, Done, Close, and Escape in More Options keep the dialog open while the Declassifying date is a day that is not on the calendar, such as 02/30/2027, and "Please enter a valid value. The field is incomplete or has an invalid date." shows under the field.

A reply to more creators says how many it added

A Thread message such as "more creators like these" now gets a reply that states how many creators the new search added to the results on screen. When the Thread already shows 100 creators and the new search finds the same ones, the reply says that no new creators were added. Before, the reply said that the results now show more creators while the same 100 stayed on screen.

A follower tier outside the results no longer leaves a trailing "with" in the brief

The new search that a Thread message for a follower tier outside the results runs drops the word that introduced the follower phrase together with the phrase. "Fitness creators on TikTok in the United States with under 50K followers" followed by "only macro creators" now gives the brief "fitness creators on TikTok in the United States". Before, the brief sometimes kept a trailing "with", and the Search plan card and the Searched line showed it.

A reply no longer disowns the country of its search

A Thread reply no longer says that the results are not limited to a country when the search runs with that country. After a Brazil search with a follower tier, a message such as "only mid creators" runs a new search that keeps Brazil, and its reply matches the Search plan and the Brazil chip. The "not limited to that country" sentence stays for a new search in a country outside the ten.

Reels category labels stay inside the card

On the Reels view of /app, a creator card whose category label is wider than the card, such as "Japanese Language Lessons" on a 390 px screen, ends the label with an ellipsis inside the card instead of running past the card edge.

Adding creators in a Thread keeps the ones on screen

A Thread message that asks for more creators, such as "also add more creators in Mexico who make coffee content", keeps the creators on screen in the combined results. A new search that fills the 100-creator limit no longer pushes them out: when the two sets together pass 100 creators, each keeps an equal share of its best fit creators, and the list still reads best fit first.

A follower count above the results always runs a new search

A Thread message such as "only creators with more than 10K followers" over Nano 1K to 10K results now always runs a new search for Micro+ 10K+. Before, the same message sometimes answered that the results could not be narrowed by follower count and ran no search. The same holds for every follower tier that shares no follower count with the tier of the Search plan.

A reply after a search outside the ten countries matches the Search plan

After a Thread search for a country outside the ten, such as "run a new search for coffee creators in Mexico", a later reply about those results, such as the reply to "not brand accounts", no longer says that the results are in that country. The Search plan card reads Country "Anywhere" for that search, and the reply now agrees with it. A follow-up such as "only creators based in Mexico" still narrows the results on screen by home country.

Save Proposal refuses a form that is out of date

Save Proposal on a form that was open while the campaign changed in another tab or session saves nothing and shows "This campaign changed since you opened this page. Reload the page to see the saved values, then make your change again." Before, the save replaced the contract, the disclosure statement, the declassifying date, and the visibility saved in between.

Published searches drop creators below 1,000 followers

A published search, its Markdown rendition, and the Searches list on a creator page leave out a creator with fewer than 1,000 followers. The follower count is read when the page loads, so a creator who falls below 1,000 followers leaves every published search at once.

List captions do not repeat the country

The caption under Creators on a List page, and the title of a search in the command palette, no longer repeat a platform or country that the brief already names. The follower tier always shows. A List saved from "coffee brewing creators in the United States" with the Country filter set to United States used to read "coffee brewing creators in the United States, United States".

Email on file counts every stored post

The Email on file mark on search results on /app now counts an address in the caption of any post Starcovery stores for the creator, as the campaign page does. It used to read only the captions of the posts that matched your brief, so a creator whose address sat in another post had no mark in search while the campaign page showed one.

A long first message runs as a search

A first message on /app of about 240 to 2,000 characters that describes the creators to find, such as a paragraph about your product and your buyers, now runs as a search. Starcovery writes one brief of at most 200 characters from it, shortening the niche and audience wording before the country, platform, and creator size, and cuts the reply at 400 characters, where before the Thread ended in The reply did not finish. with no results and no use spent.

A follower tier outside the results keeps the earlier brief words

The new search that a Thread message for a follower tier outside the results runs, such as "only micro creators" over Mid 50K to 250K results, keeps the words of the earlier brief and drops only the words that name its follower count or tier. "UK based coffee creators around 100k followers on Instagram" becomes "UK based coffee creators on Instagram" with the Micro 10K to 50K tier. The Search plan card and the page heading show that brief.

A new search outside the ten countries keeps the place

A Thread message that asks for a new search in a country outside the ten, such as "run a new search for coffee creators in Mexico", runs one search with the place in the brief and no country. The reply says that the results are not limited to that country and that a follow-up such as "only creators based in Mexico" narrows the results on screen by home country. It no longer declines, filters a worldwide search to that country, or offers that country as a search country. The search spends up to one more use.

A follower tier outside the results runs a new search

A Thread message that names a follower tier that shares no follower count with the tier of the Search plan, such as "only micro creators" over Mid 50K to 250K results, runs a new search for that tier and keeps the brief, platform, and country. The reply states the new search before it runs and no longer says that it will narrow the results. The new search spends up to one more use.

Sort the Table view from its column headers

Pressing the Followers, Engagement on views, or Average views column header in the Table view of /app sorts the results by that column, highest first, as choosing it under Sort results does. An arrow marks the column the table is sorted by.

A narrowing message by home country runs no new search

A Thread message that narrows with "only" and names a home country, such as "only Instagram creators based in the UK" over a Brazil search with no platform, narrows the creators on screen for one use and runs no new search. The earlier brief stays, and the Search plan shows the named platform and country. It no longer sometimes replaces the earlier brief with a new search that costs up to two uses. The list is empty when none of the creators on screen lives there, and the reply says so. A message without narrowing words, such as "creators in the UK", still runs a new search, and so does a message that switches to the other platform of a search that has one.

More creators like these keeps the Thread brief

A message in a Thread that asks for more creators like the ones on screen, such as "more creators like these", keeps the brief the Thread already holds. The Search plan card and the page heading show that brief again, where they showed a rewritten one.

The Map view keeps its axis values in sight

The Map view on /app shows its axis values along the bottom and left edges of the frame, where they follow the pan and zoom. They used to sit on the center lines, where the bubbles covered them.

More Options says who reads a private campaign

In More Options on the proposal form, Private for 1 Credit reads "Only your organization opens the campaign. Creators you send it to read its name, pay, and terms in their proposal." A private campaign's name, pay, and posting date show on the Proposals and Hired on rows of the creators who receive its proposal.

Shoutout posts must match where you posted

Submit Post in the Shoutout settings checks the link against Where you posted. A link on instagram.com needs Instagram, a link on tiktok.com needs TikTok, and a link on any other site needs Blog post. A link under another choice is refused with a line on the field, and the refusal does not count toward the 10 posts allowed in 24 hours.

Reels tiles show average views

A Reels tile on /app names the creator's average views, such as "Instagram, 26,471 average views", the figure the Creators cards, Table, Map, the creator page, and the "average views" filter use. It used to name the play count of the one reel on the tile as "views". A creator with no view data shows the platform alone.

Transfers reads Not paid for an unpaid payout

The Paid column of the Transfers table on /payouts reads "Not paid" for a payout with no paid date, as the Hired on table on /proposals does, in place of an empty cell.

More Options closes on a past declassifying date

On the proposal form, Done, Close, and Escape close More Options while the Declassifying date holds a day before today in UTC. Save Proposal reopens More Options with "Set the campaign details declassifying date to today or a later day in UTC." under the field and sends nothing. A date that is not on the calendar still keeps the dialog open.

Compare Starcovery with Collabstr, GRIN, Heepsy, and Influencity

/vs adds comparison pages for Collabstr, GRIN, Heepsy, and Influencity. Each page compares the two tools row by row, quotes the competitor's published prices with the day they were read, and lists when each one wins.

A guide to creator pay by follower tier

The creator pay guide answers what to pay a creator by follower tier. It lists the follower range of each tier, shows where to read the going rate, and gives the steps to run one campaign per tier from search to payout, with the cost of each step.

Hear the Private hint in Edit campaign

In Edit campaign, a screen reader reads the hint under the Private switch when the switch takes focus. The hint states what Private costs or, on a private campaign, who can open it.

More Options refuses a past declassifying date

On the proposal form, a Declassifying date you change to a day before today in UTC shows "Set the campaign details declassifying date to today or a later day in UTC." under the field, and More Options stays open until you fix it, before Save Proposal sends anything.

Structured data on every page

Every page carries JSON-LD structured data that names Starcovery as an organization and a website, with a search action that opens a brief on /app.

/pricing adds the app and one offer per credit pack. Each page with a FAQ adds its questions, each page under /docs adds an article, and each creator page that search engines index adds a profile with the creator's handle, platform, and follower count, and the country when the page shows one.

The proposal form refuses a past posting date

On the proposal form, a Creator posting date you enter before today in UTC shows "Set the creator posting date to today or a later day in UTC." under the field before Save Proposal sends anything, and What the creator sees reads "No date set" for it.

A guide to writing a creator brief

Write a creator brief shows how to describe the creators you want, which words set the platform, home country, and follower size filters, how a Thread on /app refines the results, and what each step costs. It has four example briefs with the filters each one sets.

Alternatives pages for Modash and HypeAuditor

/alternatives/modash and /alternatives/hypeauditor list the other tools that find creators, with the price each one publishes, the platforms it covers, the case it fits, and the day the prices were read. Each page links its source pages and the matching comparison under /vs.

The footer Compare column links both pages, llms.txt lists them, and each page has a Markdown form for agents.

Every documentation page in llms.txt and llms-full.txt

llms.txt lists every page of the documentation sidebar in sidebar order, the about, contact, and pricing pages, and the sitemap index at /sitemap.xml. A guide added to the documentation joins the list when it ships.

/llms-full.txt holds the documentation home page and every sidebar page except the API reference in one Markdown file served as plain text, each page followed by its URL.

Every published search on one page

/search links every published search by its question, such as "How to find fashion influencers", most searched first. The footer links it as Creator Searches, and the page has a Markdown and a JSON form for agents.

Each published search page takes its question as its title and heading. A creator page lists, under Searches, up to 10 published searches whose results hold the creator.

The proposal preview names an empty post or label

On the proposal form, What the creator sees reads "Not set" in the Post row while What they post is empty, and in the Label row while Disclosure statement is empty, as the Pay and Posts on rows do.

Date-time fields take one format over REST and MCP

Every date-time field of the REST and MCP contracts, the declassifying date and the creator posting date of a campaign among them, takes an RFC 3339 date-time with seconds, such as 2026-12-01T00:00:00Z. A space in place of T, an offset without a colon, a time without seconds, and second 60 are refused by the server and by the published schema alike. The published schema in /openapi.json and in each MCP tool carries a pattern beside the date-time format. A date that does not exist, such as February 30, is refused by the server.

Avatar initials count words joined by any whitespace

The initials in an avatar take one letter from each word of a name when the words are joined by a tab, a no-break space, or an ideographic space, as they already did for a plain space. A two-word name joined by a no-break space showed one letter and now shows two.

A guide to find a creator's email address

Find a creator's email address shows where Starcovery marks a creator with an email address on file, how to reveal the address on the web and over the API, what to do when Starcovery has no address, and what each step costs, with a published search page as a live example.

Names from long briefs end on a whole word

A campaign name, campaign goal, or List name made from a long brief ends on a whole word when the brief separates its words with line breaks, tabs, or no-break spaces, and keeps a last word that fits exactly. The cut no longer splits a flag or a combined emoji such as a family.

The API description declares the quota headers

/openapi.json declares the RateLimit, RateLimit-Limit, RateLimit-Policy, RateLimit-Remaining, and RateLimit-Reset response headers on every response of an operation that sends them, a 401 excepted: the search and brief parse operations and every operation that accepts an API key. It also declares Retry-After on the search 402 that answers a used daily grant.

An author and an updated date on every page and guide

Every marketing page and every guide in the docs names Starcovery as its author and shows the day the page last changed. The page sitemap sends the same day as each page's last modified date.

A published search counts one creator in the singular

The Markdown rendition of a published search, /app.md?q=<term>, reads "1 creator" for one creator, and a count of 1,000 or more carries a thousands separator.

OAuth client registration refuses a name with no visible character

Registering an OAuth client at /oauth2/register with a client_name that has no visible character, such as one made only of zero-width characters, answers 400 invalid_client_metadata. Creating or updating a client already refused an empty name, and now refuses a name with no visible character on the same grounds.

Find micro creators for a skincare launch

The skincare launch guide shows how to find creators with 10,000 to 49,999 followers for a skincare launch: the brief, the filter chips, the fit score, the shortlist, the proposal, and the price of each step. It links published skincare searches as a live example.

Long briefs that start with invisible characters make campaigns

A long brief that starts with invisible characters, such as zero-width spaces or blank lines of braille blanks, makes a campaign, a campaign goal, or a List name from its first visible character. Such a brief used to fail with a server error.

Required fields refuse a value that looks empty

A required text field now shows "Enter more than spaces." for a value with no visible character, such as one zero-width space. Fields that accepted such a value before now refuse it, and the campaign Name and Goal fields, which showed "Enter a value.", show the same line. On the first-run composer at /home, a draft of such characters keeps the suggestion buttons visible and Send shows the same line.

Password fields keep their earlier check.

A recorded payout waits on the creator post

A campaign whose funded creator has a payout on record and no live post shows Creators post as its next step, waiting on that creator, on the campaign page, Home, /campaigns, and the assistant's to-dos. Starcovery pays them waits on Starcovery only once the creator's post is on record, because Starcovery pays a creator after the post goes live.

Reopen an archived campaign to fund it

An archived campaign takes no funding request. The funding page, the API, MCP fund_campaign, and the CLI answer archived, as the campaign page and the assistant already did.

Reopen Campaign in the Campaign actions menu of an archived campaign reopens it. A campaign whose proposals were sent returns to its open steps, so you can request funding for the creators who accepted; any other campaign returns to draft. Over the API, MCP, and the CLI, set the status to active to reopen a sent campaign.

The Country filter keeps the creators apart from the audience

A brief that names a city where the creators are keeps that city's country in the Country filter when it also names an audience in the same country, such as "pet influencers in Seattle for a US audience". A brief that names where the audience comes from, such as "creators with fans from the UK", or a market it targets, such as "beauty creators targeting Korea", leaves the Country filter at Anywhere.

A guide to finding creators by topic

The guide Find creators who post about a topic shows how to write a topic as a brief on /app, why the rank comes from the videos a creator posts and not the bio, a published search for home espresso tutorials, and what each step costs.

Tell us what led you here

After sign-up, a new account sees one optional question before the page it was going to: what it asked an AI assistant or a search engine that led it to Starcovery. Continue saves the answer, and Skip goes on without one. Each organization keeps its first answer.

An account created while it connects an AI assistant over OAuth continues the authorization without the question.

Starcovery in the Official MCP Registry

The Official MCP Registry lists Starcovery as com.starcovery/mcp, with the MCP address https://www.starcovery.com/api/mcp. The entry matches /server.json.

The funding limit refusal names a path that works

A funding request whose total passes the $21,474,836.47 limit now says the limit is for one funding request and asks you to write to team@starcovery.com about the campaign. It no longer tells you to remove creators or lower the compensation, which a campaign refuses once its proposals are sent. The web, REST, MCP, and the CLI show the same text.

An unpaid invoice shows in To-dos

The To-dos card in the assistant pane shows a campaign invoice your organization has not paid while a funded creator has not posted yet, and the assistant's idle nudge on the campaign page names that invoice to an owner or admin.

The agent docs open as a web page in a browser

/agents opens as a web page with headings and links when a browser visits it. Agents get the same document as Markdown from /agents.md or by sending Accept: text/markdown.

A request that asks for neither Markdown nor plain text, such as curl with its default Accept header, gets the web page.

Read a usage chart day with the keyboard

On the Analytics view of /usage, the arrow keys on a focused chart move its card heading and headline to the day the hover card shows and that day's total, as the mouse does. When focus leaves the chart, the heading returns to the chart title and the window total.

Find TikTok creators in a country

The TikTok creators by country guide shows how to find TikTok creators based in one country for a product launch: the countries the filter covers, the brief, the filter chips, the result cards, the List and the campaign, and the price of each step. It links a published search as a live example.

An About page with key facts and common questions

/about lists what Starcovery does, one section per service, how it differs from Modash and HypeAuditor, who uses it, and how a campaign runs. A Key facts list names the company, its headquarters state, the offering, the price, the contract terms, the support address, and the X account, and common questions follow.

llms.txt and /about.md carry the same key facts.

More creators on each creator page

Each creator page ends with a More creators card. It lists up to 12 creators on the same platform and in the same country with the nearest follower counts, up to six with more followers and up to six with fewer, and each name links to that creator's page.

Instagram and TikTok engagement benchmarks

/reports/engagement-benchmarks lists the median engagement rate and the median views per post on Instagram and TikTok, by follower tier and by creator country, from public profiles in the Starcovery catalog. Its method names the profiles and posts it counts and the date range of those posts.

The footer links Engagement Benchmarks under Company, and the page has a Markdown form.

A guide to pay creators and handle disclosure

Pay creators and handle disclosure lists each Starcovery Payouts step from proposal to payout, what each step costs, how a creator gets paid, and where each creator reads the disclosure statement you set on the campaign.

A guide to run a creator campaign without an agency

Run a creator campaign without an agency lists each step from brief to payout, who takes each step, and what each step costs, with a published search page as a live example.

A changelog with an Atom feed

The changelog lists each change to Starcovery that a customer or an agent can see, newest first, with the day it shipped. Feed readers subscribe to /changelog.xml, and llms.txt points agents to both.

Use Starcovery in Microsoft 365 Copilot

/ai has a Microsoft 365 Copilot card. A Microsoft 365 admin downloads the Starcovery agent from /agents/microsoft-365-copilot.zip, registers it with the Microsoft 365 Agents Toolkit, and uploads it in the admin center. Each person signs in to Starcovery when Copilot asks.

The Microsoft 365 Copilot guide has the steps.

A cap of 25 waiting handle claims

An organization holds at most 25 handle claims waiting at once. A claim waits while it is in review, or while its renewal code is open after its verification lapsed. Past the cap, the Handles pane in Settings asks you to start another claim once one is approved, rejected, or expires, and REST answers 429 with a retry-after until the earliest waiting claim expires.

Over REST, verifying a rejected, revoked, or expired claim answers with the claim and its status.

Every credit pack in one table

/pricing lists every credit pack in one table, with its price, base credits, bonus credits, and uses, and a Buy link on each row. The Markdown form of the page has the same columns.

Set up an AI assistant from one page

/ai lists the AI assistants that connect to Starcovery over MCP: Claude, Claude Code, and Cursor. Each card names where the MCP address goes and links to its steps in the MCP guide. The header and the footer link AI.

The page also lists when an assistant should recommend Starcovery and when it should not. llms.txt carries the same lines.

Connect Codex over MCP

The MCP guide has a Codex section. Adding Starcovery with codex mcp add signs in through OAuth, and a Settings API key works through an environment variable instead.

Compare creator search tools on one page

/vs lists every comparison page in one table: the tool, who it fits, its published price with the day it was read, two pros, two cons, and when to pick it over Starcovery. Each row links to the full comparison.

MCP tool hints and the Claude connector steps

Over MCP, the tool list marks list_api_keys as read-only, and every tool carries its title in its annotations too.

The MCP guide and the MCP pane of Settings follow the current Claude Desktop custom connector dialog: Customize, then Connectors, then Add custom connector.

Ask for creators picked by hand

A row under the search results of a Thread on /app offers to pick creators by hand. Send mails the brief to Starcovery, which picks creators for it and replies by email within 2 days, free.

A visitor without an account types the address for the reply. Dismiss hides the row in that browser.

Rename a List

Rename List in the List actions menu of a List page gives the List a new name. The command palette finds the List by that name.

A page for each published search

Each published search has its own page under /search/, with the brief as the title, its creators as result cards, and Run This Search, which runs the brief on /app.

The search sitemap lists these pages, and each page has a Markdown and a JSON form for agents.

Answer proposals, name the platforms, and see live posts

An organization that holds a verified handle answers each proposal sent to that handle with Accept or Decline in the Hired On view of /proposals.

A proposal names the platforms its one payment covers: Instagram, TikTok, or both.

The campaign page lists each live post of a hire with its views, its likes and comments, and Open Post.

A creator page shows Hire for a creator with 1,000 or more followers. Hire starts a campaign with that creator.

See which creators have an email on file

Search results on /app mark each creator profile that has an email address on file, on the Creators cards, in the Contact column of the Table, and in the Map inspector, for visitors too. After your organization reveals a profile, its mark reads Email revealed.

The exported CSV has the same Contact column.

See whether each creator is in a payout country

The Send Proposal confirmation and the creator tiles on a campaign page mark each creator Payout country, Not a payout country, or Country unknown, from the country on the creator's profile.

A payout goes to the country of the creator's payout account, which can differ from the profile country, so the mark warns and does not block the send.

By Starcovery. Updated .