API reference

Developer docs

One authenticated request returns the current cultural block for a topic as JSON. Wire it into your agent's system prompt or fetch it fresh on each call.

Authentication

Every request needs a secret key in the Authorization header as a bearer token. Create and manage keys from your dashboard. Keys look like geist_sk_live_… — keep them server-side.

Query trends

POST /v1/trends/query — body { query, category, week? }.

Request

curl https://geist-api.cluster.myalt.shop/v1/trends/query \
  -H "Authorization: Bearer $GEIST_KEY" \
  -H "content-type: application/json" \
  -d '{ "query": "top 10 fashion trends this week", "category": "fashion" }'

200 · application/json

{
  "query": "top 10 fashion trends this week",
  "category": "fashion",
  "week": "2026-05-11-W20",
  "trends": [
    { "name": "Wide-leg denim", "description": "...", "images": [ ... ] }
  ],
  "noSignal": false
}

Endpoints

Method	Path	Description
POST	/v1/trends/query	Run a cultural-trends query for a category/week
POST	/v1/trends/brand-query	Brand-aware query from a brand URL (Pro+)
GET	/v1/trends/usage	Current billing-period usage
GET	/v1/plans	Available plans and limits

Full interactive reference (OpenAPI/Swagger) is served at geist-api.cluster.myalt.shop/docs.