Skip to content

API tokens · spec demo

A key you can mint, that opens nothing

Five scopes, one label, and a deterministic string: the same inputs always produce the same mto_demo_ key, so it can be screenshotted, pasted into a demo and still be obviously not a credential. What a real key needs — storage, hashing at rest, quotas, revocation — is listed on the page rather than implied by a green checkmark.

demo · no billing attached

This page mints text; it does not issue credentials

No payment processor is wired into this build. Nothing here can charge a card, store a receipt or email an invoice — every paid surface below is a working demo of the flow, and the prices are this site's own plan copy.

What is actually licensed →

1 · Name the token

The label changes the string but is not stored anywhere — this page keeps nothing.

2 · Pick scopes

3 · The string it would hand you

mto_demo_1qknpss1i14vqu

4 · The request it would make

GET /v1/components?kind=animated&limit=20
Authorization: Bearer mto_demo_1qknpss1i14vqu
X-Motif-Scopes: read:components

Nothing answers that request. The mto_demo_ prefix is deliberate: this token is deterministic from its label and scopes, so the same inputs always produce the same string, and a screenshot of it cannot be mistaken for a live credential. A real implementation needs key storage, hashing at rest, rate limits and a revocation list — an API design, not a page.

What the endpoint would return

The Studio already prints a spec preview of the theme endpoint's JSON shape, marked not implemented. This page stops at the credential, and links there rather than inventing a second, different response shape.

Theme API preview →

Scope reference

  • read:componentsList and fetch the 289 catalog entries.
  • read:promptsPrompt bodies plus their run logs.
  • read:themesFetch token kits saved by the account.
  • write:themesCreate or replace a kit. The only write scope offered.
  • read:runsPer-model fidelity and build-error history.

Only one write scope is offered on purpose. A token that can publish content the editorial gates have not seen is a different kind of product, and this section is not going to imply it exists.