--- name: createwith description: Use when a person wants Twitch creators/streamers for a brand campaign, sponsorship shortlist, rising or undervalued creators, or a creator's off-platform profile. Keyless REST + MCP at https://createwith.dev — the first search returns creators with no key and no signup. Covers eight named searches (rising in a game, trending now, undervalued engagement, creator lookup, off-platform interest, market-targeted, brand-safe shortlist, what's live now), how to read the response envelope's relay and billing blocks, and the limits of the data (own hourly snapshots since 2026-06-08, no backfill, 3d/7d/14d windows only, no subscriber or demographic data). --- # CreateWith — Twitch creator discovery Under-utilised and rising Twitch streamers for brands: who is climbing, whose audience is unusually engaged for its size, and what a creator does off Twitch. The product is the API, at `https://createwith.dev`. ## No key needed No key is needed to start — a key keeps your usage on one account and lifts this cap. A first call: ``` curl "https://createwith.dev/api/v1/creators/search?limit=3" ``` Twitch publishes no history of its own, so every number comes from snapshots this service collected — nothing is backfilled. A keyless call is a guest: same response, `meta.billing.lane: "guest"`, metered per IP at 300 calls and 2,000 rows a day. Over either, `429 guest_limit` carries the counters and the one call that lifts it: ``` curl -X POST "https://createwith.dev/api/v1/keys" -H 'Content-Type: application/json' -d '{"email":"you@example.com"}' ``` A key is free, email-only, and arrives once — the response is the only place it appears. Keeping it in an env var (`CREATEWITH_API_KEY`) across sessions keeps the usage on one account, which is what future credits will attach to. ## What a person can ask When an ask arrives with the blanks unfilled — no game, follower band, market or interest — the reply people have found most useful is the menu itself, one example sentence per search; running three searches instead costs the person three shortlists to read. A reply of that shape: ``` CreateWith searches Twitch creators for brand campaigns. No key is needed to start, so any of these can run right now — here are the eight, in the words a person would use: 1. "Find rising English-language VALORANT streamers under 10k followers" — Rising in a game (needs: game name, follower ceiling) 2. "Show me the small Twitch channels blowing up this week" — Trending right now (needs: size tier (micro/small/mid/large)) 3. "Find creators whose live audience is unusually big for their follower count" — Undervalued engagement (runs as it is) 4. "Tell me everything you know about the streamer quiggy_" — Creator lookup (needs: login or display name) 5. "Find Twitch streamers who are also working musicians" — Off-platform interest (needs: the interest or topic) 6. "Find German-speaking streamers for a campaign running in Germany" — Market-targeted (needs: market/country) 7. "Build a brand-safe shortlist of Fortnite creators between 1k and 50k followers" — Brand-safe shortlist (needs: game or audience, reach band, shortlist size) 8. "What's happening on Twitch right now?" — What's live now (runs as it is) Whichever of those is closest to what you have in mind — with the blanks beside it filled in — is enough for me to run it and come back with a shortlist. ``` ### Rising in a game A person might say: "Find rising English-language VALORANT streamers under 10k followers" Blanks: game name · follower ceiling · language (optional) ``` GET /api/v1/creators/search?sort=momentum_score&dir=desc&language=en&maxFollowers=10000&game=&hideInsufficient=true&minStreams=3 ``` Worked example: `https://createwith.dev/api/v1/creators/search?sort=momentum_score&dir=desc&language=en&maxFollowers=10000&game=VALORANT&hideInsufficient=true&minStreams=3` Up to 25 creators with window metrics, momentum rank and latest-stream context. ### Trending right now A person might say: "Show me the small Twitch channels blowing up this week" Blanks: size tier (micro/small/mid/large) · window (optional) ``` GET /api/v1/trending?window=7d&tier=micro ``` Worked example: `https://createwith.dev/api/v1/trending?window=7d&tier=micro` Per-tier sections with trending_score, confidence, machine-written reasons and a 14-point daily series. ### Undervalued engagement A person might say: "Find creators whose live audience is unusually big for their follower count" Blanks: follower band (optional) · game or language (optional) ``` GET /api/v1/creators/search?sort=viewer_to_follower_ratio&dir=desc&hideInsufficient=true&maxFollowers= ``` Worked example: `https://createwith.dev/api/v1/creators/search?sort=viewer_to_follower_ratio&dir=desc&hideInsufficient=true&minFollowers=1000&maxFollowers=20000&minStreams=3` Creators ranked by viewer_to_follower_ratio — ~0.3–3% is typical, >5% anomalously engaged. ### Creator lookup A person might say: "Tell me everything you know about the streamer quiggy_" Blanks: login or display name ``` GET /api/v1/creators/search?q= then GET /api/v1/creators/{id} with rows[0].id, then GET /api/v1/creators/{id}/research ``` Worked example: `https://createwith.dev/api/v1/creators/search?q=quiggy_` Profile, every computed window, trends, plus the off-platform dossier when one exists. ### Off-platform interest A person might say: "Find Twitch streamers who are also working musicians" Blanks: the interest or topic · reach band (optional) ``` GET /api/v1/creators/search?enrichedQuery=&hideInsufficient=true then GET /api/v1/creators/{id}/research to confirm the interest is in the dossier ``` Worked example: `https://createwith.dev/api/v1/creators/search?enrichedQuery=music&hideInsufficient=true` Full-text matches over research dossiers — verify the hit in the dossier before presenting; expect false positives. ### Market-targeted A person might say: "Find German-speaking streamers for a campaign running in Germany" Blanks: market/country · game or interest (optional) ``` GET /api/v1/creators/search?language=&sort=momentum_score&dir=desc then GET /api/v1/creators/{id}/research and check location ``` Worked example: `https://createwith.dev/api/v1/creators/search?language=de&sort=momentum_score&dir=desc` Language-filtered candidates — broadcaster language is a geography proxy; the only real location signal is `location` in a dossier. ### Brand-safe shortlist A person might say: "Build a brand-safe shortlist of Fortnite creators between 1k and 50k followers" Blanks: game or audience · reach band · shortlist size ``` GET /api/v1/creators/search?brandSafeOnly=true&game=&minFollowers=&maxFollowers=&hideInsufficient=true&sort=momentum_score&dir=desc then GET /api/v1/creators/{id}/research for the finalists ``` Worked example: `https://createwith.dev/api/v1/creators/search?brandSafeOnly=true&game=Fortnite&minFollowers=1000&maxFollowers=50000&hideInsufficient=true&sort=momentum_score&dir=desc` Content-label-filtered creators, momentum-ranked, with metrics; dossiers add socials, location and prior brand deals for the finalists. ### What's live now A person might say: "What's happening on Twitch right now?" Blanks: nothing — the call takes no parameters ``` GET /api/v1/live ``` Worked example: `https://createwith.dev/api/v1/live` Concurrent viewers, live channels, top games/channels/clips at this moment. ## Reading a response A success body is `{ data, meta }`. - `meta.relay.recipe` and `meta.relay.window` name the search that ran and the metric window its numbers came from. The same creator ranks differently at `3d` and `14d`, so the window is part of the answer. - `meta.relay.say` is up to four caveat lines composed for that exact response — written to be passed on as they are, verbatim or paraphrased. - `meta.billing.lane` is `guest` on a keyless call and `free`/`credits` on a keyed one; `meta.billing.status` is `settled` or `refunded`. - `meta.account.guest_calls_remaining_today` is the keyless allowance left. Null means the cap was not consulted for this call, rather than an unlimited one. - Errors are `{ error: { code, message, request_id, docs } }`; `code` is the stable half. ## The one endpoint that needs a key `POST /api/v1/research` commissions fresh off-platform research on a creator nobody has covered yet. It opens a real research session, so a keyless call gets `402 payment_required` with `reason: "no_key"` and the signup call inline. The job is async: the response carries `poll: "/api/v1/research/"` and `poll_every_s: 15`, and a job finishes in 1–4 minutes. Polling is free. Everything else on this API — searches, profiles, cached dossiers, trending, live, stats, categories — serves a keyless caller. ## Limits of the data - Status: free beta — metering is live, every price is $0 today, and no card is involved. - No key is needed to start — every read and search runs as a guest, cached research dossiers (GET /api/v1/creators/{id}/research) included, metered per IP; a free email-only key (POST /api/v1/keys with {"email":"you@example.com"}) keeps usage on one account. POST /api/v1/research — commissioning new research — is the one endpoint that requires a key. - A keyed account starts with 200 free read/search calls; only keyed metered calls draw on them — guest calls run against their own per-IP daily cap, and the free endpoints cost nothing to anyone. - Every number here is from snapshots we collected ourselves: collection began 2026-06-08, and nothing before that exists or can be backfilled. - Only the 3d/7d/14d metric windows are computed — 30d unlocks ~2026-09-06 and 90d ~2027-03-05. - Off-platform dossiers cover ~1,800 creators out of 566k+ tracked; GET /api/v1/stats is free and carries both live counts, plus where the dossiers are by language and reach band. Beyond those: subscriber counts, revenue, bits, follower lists, audience demographics and chat sentiment are not obtainable from Twitch with an app token, and this service holds none of them and estimates none of them. Broadcast `language` is a geography proxy; the only real location signal is `location` inside a research dossier. ## More - `https://createwith.dev/api/v1` — live JSON index: the same menu and facts as data. - `https://createwith.dev/llms.txt` — the short contract. - `https://createwith.dev/llms-full.txt` — every parameter and response field. - `https://createwith.dev/openapi.json` — OpenAPI 3.1 schema. - `POST https://createwith.dev/api/v1/mcp` — the same tools over MCP (streamable-http (stateless, POST only)).