Authorization header and we mint a token for you, serve that same request, and hand the token back in a response header.
Keyless is for trying things out. For anything you depend on, create an API key: the limits are higher and the budget is yours alone.
Your first call
-i matters. Your token is in the response headers:
Keep the token
Save it and send it as a normal Bearer token from then on. Every call that carries it reuses the same budget instead of minting again.What you get
Keyless also shares a pool with everyone else trying the API, so a busy day can run it out. An API key does not share.
Which endpoints work
generate, mutate, pipeline, explore, extract, annotate, narrate, evaluate, chart-knowledgejudge, suggestions, generate-workflow, feedback and all attachment endpoints need an API key.
Errors
None of the 4xx ones are worth retrying immediately. Wait, or switch to a key.

