How we use Pollinations

Every AI image and every AI video clip in this product is generated by Pollinations. This page documents the exact calls, so you can see what runs on your key before you connect one.

1. Connecting your account (OAuth 2.0 + PKCE)

The connect page at /connect-pollinations sends you to Pollinations to authorize. Nothing is generated until you have done this.

GET https://enter.pollinations.ai/authorize
  ?response_type=code
  &client_id=pk_q6YUCviov402CcQs
  &redirect_uri=https://automatedvideoapp.com/connect-pollinations
  &scope=usage
  &state=<random>
  &code_challenge=<S256 of verifier>
  &code_challenge_method=S256

The redirect_uri is a fixed constant, not derived from the current URL — the page is served at both /connect-pollinations and /connect-pollinations.html, and deriving it meant sending a value that did not match the one registered on the App Key.

Pollinations returns to that URL with ?code=. The code is exchanged server-side, so the client secret and the resulting key never touch the browser:

POST https://enter.pollinations.ai/api/oauth/token
Content-Type: application/x-www-form-urlencoded

grant_type=authorization_code
&code=<code>
&client_id=pk_q6YUCviov402CcQs
&redirect_uri=https://automatedvideoapp.com/connect-pollinations
&code_verifier=<verifier>

You can also skip OAuth and paste a secret sk_ App Key. Publishable pk_ keys are rejected with an explanation — a pk_ key cannot authenticate generation, and silently accepting one would produce an app that appears to work while every render quietly falls back to stock footage.

2. Generating stills

GET https://image.pollinations.ai/prompt/{prompt}

Live example. The image below is not stored on this site. Your browser is fetching it from the Pollinations image endpoint right now — open your network tab and you will see the request:

A still generated live by the Pollinations image endpoint
image.pollinations.ai/prompt/A bright modern office, soft natural light, cinematic photograph?width=960&height=540&nologo=true&seed=42 — the same endpoint every scene in every video uses, called here without a key so you can see it work.

Inside the app the same request carries your App Key and the scene's own prompt:

GET https://image.pollinations.ai/prompt/<url-encoded prompt>
  ?width=1920&height=1080&nologo=true&seed=<n>&model=<model>
Authorization: Bearer <your App Key>

Rendered larger than the output frame so the Ken Burns crop still lands on a crisp 720p. One request per scene that needs an AI still.

3. Generating video clips

GET https://video.pollinations.ai/prompt/{prompt}
GET https://video.pollinations.ai/prompt/<url-encoded prompt>
  ?width=1280&height=720&seed=<n>&model=nova-reel
Authorization: Bearer <your App Key>

Used by the hybrid and full AI video modes. Each clip is seeded from that scene's own still, so the motion matches the picture the scene already had. Requests fall back down a model ladder rather than failing the render outright.

4. Whose Pollen gets spent

HeaderWhen
Authorization: Bearer <sk_ key>Bring-your-own-Pollen — your key, your ceiling, your bill.
X-Pollinations-ReferrerSent when the +25% developer earnings option is enabled.

Free Quest Pollen is consumed first. Video calls ask the API to stay on Quest unless paid spend has been explicitly allowed, so a scheduled series cannot quietly run up a bill.

Revoke any time. Manage or delete the key at enter.pollinations.ai/keys. Disconnecting in the app deletes our stored copy immediately.

5. What we never do

Connect your Pollinations account →