A Common Lisp job talks to Trends API with one POST to https://api.trendsapi.ai/api, a Bearer key, and a JSON body that names a mode. There is no official Common Lisp library. Dexador owns the HTTP client. Yason parses JSON. The first decode reads the envelope, then a second decode reads the body string. Pulled on 2026-11-12, Google Search for common lisp programming scored 13.0 for the week of 2026-11-07, versus 0.0. common lisp language scored 11.0 versus 0.0. Bare common lisp scored 12.0, down 14.29% from 14.0, the opposite 7D sign from the programming phrase. lisp programming scored 32.0 versus 24.0, 19 points above the Common Lisp phrase. sbcl scored 30.0 versus 22.0. YouTube for common lisp programming scored 0.0 versus 0.0. Do not copy lisp programming Search 32.0 onto a Common Lisp adoption alert that only watches the phrase token at 13.0. The same helper that stores those rows also pulls a live Google Trends board. A rank-13 name whose weekly Search still printed 7.0 while daily Search printed 100 is documented in Byron Donalds live rank versus weekly Search.
How does a Common Lisp client call Trends API?
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_growth","source":"google search","keyword":"common lisp programming","percent_growth":["7D","30D","3M","12M"]}
(ql:quickload '(:dexador :yason))
(defun trends-growth ()
(let* ((key (uiop:getenv "TRENDSAPI_API_KEY"))
(payload "{\"mode\":\"get_growth\",\"source\":\"google search\",\"keyword\":\"common lisp programming\",\"percent_growth\":[\"7D\",\"30D\",\"3M\",\"12M\"]}")
(envelope (yason:parse
(dex:post "https://api.trendsapi.ai/api"
:headers (list (cons "Authorization"
(format nil "Bearer ~A" key))
(cons "Content-Type"
"application/json"))
:content payload)))
(body (gethash "body" envelope)))
(yason:parse body)))
ql:quickload pulls Dexador and Yason. dex:post owns the HTTP client. The first yason:parse reads statusCode and body. gethash on "body" prints the inner string. A second yason:parse on that string is required before reading recent_value. uiop:getenv reads the Bearer key. The collections ship outside this API:
https://github.com/fukamachi/dexador
https://github.com/phmarek/yason
https://www.quicklisp.org
https://www.sbcl.org
Dexador and Yason are client libraries. They are not Trends API sources. There is no Quicklisp download-count source on this API. ql:quickload talks to the Quicklisp dist. That registry is not a Trends source.
The response envelope is {"statusCode": int, "body": string}. body is a JSON string and must be parsed a second time before reading recent_value. A Racket client that does the same double parse with http-sendrecv is on Racket Trends API. A Nix flake that does the same double parse with curl and jq is on Nix Trends API.
What did get_growth return for Common Lisp language tokens?
get_growth for common lisp programming on google search tips on 2026-11-07. Store the exact strings. common lisp language is a different series. lisp programming closed 19 points above programming. Bare common lisp printed the opposite 7D sign.
| Keyword | Period | Recent date | Recent | Baseline date | Baseline | Growth |
|---|---|---|---|---|---|---|
| common lisp programming | 7D | 2026-11-07 | 13.0 | 2026-10-31 | 0.0 | vs 0.0 |
| common lisp programming | 14D | 2026-11-07 | 13.0 | 2026-10-24 | 0.0 | vs 0.0 |
| common lisp programming | 30D | 2026-11-07 | 13.0 | 2026-10-10 | 0.0 | vs 0.0 |
| common lisp programming | 3M | 2026-11-07 | 13.0 | 2026-08-08 | 72.0 | -81.94% |
| common lisp programming | 12M | 2026-11-07 | 13.0 | 2025-11-08 | 0.0 | vs 0.0 |
| common lisp programming | YTD | 2026-11-07 | 13.0 | 2026-01-03 | 0.0 | vs 0.0 |
| common lisp language | 7D | 2026-11-07 | 11.0 | 2026-10-31 | 0.0 | vs 0.0 |
| common lisp language | 14D | 2026-11-07 | 11.0 | 2026-10-24 | 0.0 | vs 0.0 |
| common lisp language | 30D | 2026-11-07 | 11.0 | 2026-10-10 | 0.0 | vs 0.0 |
| common lisp language | 3M | 2026-11-07 | 11.0 | 2026-08-08 | 55.0 | -80.0% |
| common lisp language | 12M | 2026-11-07 | 11.0 | 2025-11-08 | 0.0 | vs 0.0 |
| common lisp language | YTD | 2026-11-07 | 11.0 | 2026-01-03 | 0.0 | vs 0.0 |
| common lisp | 7D | 2026-11-07 | 12.0 | 2026-10-31 | 14.0 | -14.29% |
| common lisp | 14D | 2026-11-07 | 12.0 | 2026-10-24 | 14.0 | -14.29% |
| common lisp | 30D | 2026-11-07 | 12.0 | 2026-10-10 | 20.0 | -40.0% |
| common lisp | 3M | 2026-11-07 | 12.0 | 2026-08-08 | 50.0 | -76.0% |
| common lisp | 12M | 2026-11-07 | 12.0 | 2025-11-08 | 25.0 | -52.0% |
| common lisp | YTD | 2026-11-07 | 12.0 | 2026-01-03 | 17.0 | -29.41% |
| lisp programming | 7D | 2026-11-07 | 32.0 | 2026-10-31 | 24.0 | +33.33% |
| lisp programming | 12M | 2026-11-07 | 32.0 | 2025-11-08 | 65.0 | -50.77% |
| sbcl | 7D | 2026-11-07 | 30.0 | 2026-10-31 | 22.0 | +36.36% |
| sbcl | 12M | 2026-11-07 | 30.0 | 2025-11-08 | 25.0 | +20.0% |
| quicklisp | 7D | 2026-11-07 | 15.0 | 2026-10-31 | 6.0 | +150.0% |
| lisp language | 7D | 2026-11-07 | 35.0 | 2026-10-31 | 31.0 | +12.9% |
| lisp | 7D | 2026-11-07 | 41.0 | 2026-10-31 | 39.0 | +5.13% |
get_time_series for common lisp programming on Google Search closed at 13.0 on 2026-11-07, matching get_growth 13.0. Adjacent weeks: 0.0 on 2026-10-31, 0.0 on 2026-10-24, 0.0 on 2026-10-17, 0.0 on 2026-10-10. Peak in this pull is 100.0 on 2025-07-05. Next highest points are 80.0 on 2024-05-04, 72.0 on 2026-08-08, and 67.0 on 2023-03-04 and 2026-06-20. Tip 13.0 is not that July 2025 high. The payload printed growth 999999 on 7D, 14D, 30D, 12M, and YTD because those baselines were 0.0. Report 13.0 versus 0.0. 3M printed 13.0 versus 72.0 (-81.94%). Same Saturday tip, opposite story depending on the window. The payload marked data_quality low. Store the 13.0.
common lisp language closed at 11.0 versus 0.0. Same 7D sign as programming, same 3M sign: language printed 11.0 versus 55.0 (-80.0%) while programming printed 13.0 versus 72.0 (-81.94%). Peak in the language series is 100.0 on 2025-12-27, then 72.0 on 2026-06-06, then 71.0 on 2026-05-30, then 70.0 on 2026-04-04. Matching Saturday tips are not matching series. Do not copy programming 13.0 onto language 7D versus 0.0.
Bare common lisp closed at 12.0, down 14.29% from 14.0. Adjacent weeks: 14.0 on 2026-10-31, 14.0 on 2026-10-24, 11.0 on 2026-10-17, 20.0 on 2026-10-10. Peak in this pull is 100.0 on 2026-05-16, then 98.0 on 2026-07-04, then 97.0 on 2026-06-06, then 83.0 on 2026-09-12. Tip 12.0 is not that May 2026 high. 12M printed 12.0 versus 25.0 (-52.0%). Opposite 7D sign from programming versus 0.0. Do not copy bare 12.0 onto programming 13.0.
lisp programming closed at 32.0, up 33.33% from 24.0. Adjacent weeks: 24.0 on 2026-10-31, 30.0 on 2026-10-24, 30.0 on 2026-10-17, 45.0 on 2026-10-10. Peak in this pull is 100.0 on 2026-02-21, then 99.0 on 2022-12-10, then 94.0 on 2026-03-28, then 93.0 on 2026-05-16. 12M printed 32.0 versus 65.0 (-50.77%). The family phrase sat 19 points above common lisp programming 13.0. Do not copy lisp programming 32.0 onto Common Lisp 13.0.
sbcl closed at 30.0, up 36.36% from 22.0. Adjacent weeks: 22.0 on 2026-10-31, 18.0 on 2026-10-24, 21.0 on 2026-10-17, 26.0 on 2026-10-10. Peak in this pull is 100.0 on 2026-09-05, then 82.0 on 2026-08-15, then 67.0 on 2026-08-08. 12M printed 30.0 versus 25.0 (+20.0%), the opposite 12M sign from programming versus 0.0. YTD printed 30.0 versus 18.0 (+66.67%). sbcl 30.0 sat 17 points above common lisp programming 13.0. Do not copy sbcl 30.0 onto programming 13.0.
quicklisp closed at 15.0, up 150.0% from 6.0. The payload marked data_quality low. Peak in this pull is 100.0 on 2026-08-01, then 98.0 on 2024-02-24, then 95.0 on 2026-06-06. 14D, 30D, 3M, 12M, and YTD printed versus 0.0. Report 15.0 versus 0.0. There is no Quicklisp source on this API. Search 15.0 is not package-download volume.
lisp language closed at 35.0 versus 31.0 (+12.9%). Bare lisp closed at 41.0 versus 39.0 (+5.13%). That four-character string mixes the language family, the speech word, and other uses. Do not treat Search 41.0 as Common Lisp language adoption.
Neighbor tools on the same pull, same source, same 7D window, same 2026-11-07 tip:
| Keyword | 7D recent | 7D baseline | 7D growth | 12M recent | 12M baseline | 12M growth |
|---|---|---|---|---|---|---|
| common lisp programming | 13.0 | 0.0 | vs 0.0 | 13.0 | 0.0 | vs 0.0 |
| lisp programming | 32.0 | 24.0 | +33.33% | 32.0 | 65.0 | -50.77% |
| sbcl | 30.0 | 22.0 | +36.36% | 30.0 | 25.0 | +20.0% |
| haskell programming | 30.0 | 25.0 | +20.0% | 30.0 | 64.0 | -53.12% |
| ocaml programming | 27.0 | 21.0 | +28.57% | 27.0 | 68.0 | -60.29% |
| racket programming | 20.0 | 53.0 | -62.26% | 20.0 | 73.0 | -72.6% |
| clojure programming | 17.0 | 13.0 | +30.77% | 17.0 | 0.0 | vs 0.0 |
| scheme programming | 7.0 | 4.0 | +75.0% | 7.0 | 32.0 | -78.12% |
lisp programming 32.0 sat 2 points above haskell programming 30.0 and 19 points above common lisp programming 13.0. sbcl 30.0 matched haskell programming 30.0 in close, not in 12M sign. racket programming printed -62.26% on 7D while scheme programming printed +75.0%. Bare scheme scored 50.0 versus 52.0. That is the generic word, not the language neighbor. Do not copy scheme 50.0 onto scheme programming 7.0. Do not copy haskell programming 30.0 onto common lisp programming 13.0. High-volume php in this session tipped on 2026-11-07 at 25.0 versus 38.0 with estimated volume 556,000. That is the same Saturday tip as the Lisp keywords, not the older 2026-10-31 tip that still held people-keywords. Store the session pull and the exact recent_date per keyword. A Haskell Trends API helper stores a language neighbor on the same 7D window. A Clojure Trends API helper stores clojure programming.
What did YouTube, News, and Wikipedia return?
YouTube for common lisp programming printed 0.0 versus 0.0 on every window. Keyword Google News for the programming phrase printed zeros on 7D. Wikipedia titles resolve on their own. Compare Wikipedia on volume.
YouTube for common lisp programming tipped 0.0 on 2026-11-07 versus 0.0, matching get_time_series 0.0, while Search sat at 13.0. The payload marked data_quality low. Store the 0.0. YouTube 0.0 is not Search 13.0. Peak in the YouTube series is 100.0 on 2026-07-04, then 75.0 on 2023-03-18, then 48.0 on 2022-03-19. On 2025-07-05 Search printed 100.0 while YouTube printed 0.0. On 2026-07-04 Search printed 0.0 while YouTube printed 100.0. Those are opposite weeks. Do not treat the YouTube floor as language adoption while Search sits at 13.0 after a 100.0 close in July 2025.
YouTube for common lisp language closed at 0.0 versus 0.0 on 7D and 12M, also data_quality low. Store the zeros. Language YouTube 0.0 is not programming Search 13.0.
YouTube for lisp programming closed at 24.0 versus 5.0 on 7D (+380.0%). 12M was 24.0 versus 51.0 (-52.94%). lisp programming YouTube 24.0 is not programming YouTube 0.0. Do not copy lisp programming YouTube 24.0 onto common lisp programming Search 13.0.
YouTube for common lisp closed at 13.0 versus 7.0 on 7D (+85.71%). 12M printed versus 0.0. Report 13.0 versus 0.0. Bare Common Lisp YouTube 13.0 is not programming YouTube 0.0.
YouTube for sbcl closed at 52.0 versus 20.0 on 7D (+160.0%), data_quality low. 12M printed versus 0.0. Report 52.0 versus 0.0. sbcl YouTube 52.0 is not sbcl Search 30.0. Do not copy sbcl YouTube 52.0 onto programming YouTube 0.0.
Keyword Google News for common lisp programming printed 0.0 versus 0.0 on 7D, with data_quality low. 12M was 0.0 versus 100.0 (-100.0%). Store the zeros. Keyword Google News for common lisp printed 0.0 versus 0.0 on 7D and 12M, also data_quality low. Do not fill News from Search 13.0. Keyword News and the Google News Top News board are different feeds. Mode docs sit at https://trendsapi.ai/docs.
Wikipedia for title Common Lisp resolved. October 2026 scored 34.0 with 4,827 pageviews versus September 67.7 with 5,802 (volume -16.8%). 7D and 14D collapsed (collapsed_range: recent and baseline resolved to the same monthly point). 3M was 34.0 / 4,827 versus July 20.5 / 4,434 (volume +8.86%). 12M was 34.0 / 4,827 versus October 2025 29.8 / 4,705 (volume +2.59%). YTD was 34.0 / 4,827 versus December 2025 56.9 / 5,488 (volume -12.04%). Peak in this pull is 100.0 / 6,737 in December 2022, then 99.6 / 6,725 in December 2021, then 95.1 / 6,595 in October 2022. Parenthetical title Lisp (programming language) resolved to a different page. October scored 0.0 with 19,386 pageviews versus September 35.0 with 25,712. 3M was 0.0 / 19,386 versus July 43.5 / 27,253 (volume -28.87%). 12M was 0.0 / 19,386 versus October 2025 25.9 / 24,063 (volume -19.44%). Peak in that series is 100.0 / 37,456 in November 2022. Score 0.0 with 19,386 views is the finding. Compare on volume. The family page is about 4.0 times the Common Lisp dialect volume. Short title Lisp resolved to a third page. October scored 3.3 with 6,672 pageviews versus July 1.8 / 6,154. Title Steel Bank Common Lisp resolved. October scored 5.5 with 587 pageviews versus September 4.1 with 547. 3M was 5.5 / 587 versus July 17.2 / 926 (volume -36.61%). Peak in that pull is 100.0 / 3,318 in January 2024. Do not join 19,386 family views onto Search 13.0. Do not treat short-title Lisp at 6,672 views as the dialect page. The Common Lisp title is the page to store for the dialect. Wikipedia source docs sit at https://trendsapi.ai/trends/wikipedia-trends.
There is no Quicklisp source on this API. npm covers npmjs. python covers PyPI. A Common Lisp watchlist that wants package downloads has no third source to join onto Search 13.0.
How does a watchlist store live boards next to weekly scores?
get_top_trends has no keyword. Pair the live Google Trends board with get_growth on the exact board string. Live rank, 1-day rank_change, and 7-day rank_change are three feeds. The rank snapshot can stamp at the same second as the mover snapshot, or days earlier than Wikipedia Trending.
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_top_trends","type":"Google Trends","limit":25}
On 2026-11-04T07:01:36Z the live Google Trends board ranked byron donalds at 13, with no row on the 1-day mover list. Wikipedia Trending, YouTube Trending, and Google News Top News stamped 2026-11-12T09:01:39Z, eight days later. Weekly Search for byron donalds scored 7.0 versus 6.0 on the 2026-10-31 tip. Daily Search printed 100 on 2026-11-04, then 1 on 2026-11-11. YouTube scored 100.0 versus 21.0 on the 2026-11-07 tip. Wikipedia Trending omitted the title on the current stamp. The helper that stores those rows is the blog in this batch: Byron Donalds live rank versus weekly Search. Do not copy that daily 100 onto common lisp programming 13.0. Board-shape notes for Google Trends live feeds sit at https://trendsapi.ai/trends/google-trends.
Free tier is 100 successful 200s per month. Only 200 responses count against quota. Five language tokens plus one live board is 6 calls. A Monday run that also pulls YouTube and Wikipedia for the programming phrase is 8 calls. Four weeks is 32 calls and still fits the free cap. Starter is 5,000, Pro 25,000, Business 100,000.
Envelope checklist
POSThttps://api.trendsapi.ai/apiwithAuthorization: Bearer <api_key>.- Parse the transport JSON, then parse the
bodystring a second time. - Store
common lisp,common lisp programming,common lisp language,lisp programming,lisp language,sbcl, andquicklispas separate series. - Compare Wikipedia
Common Lispon volume at 4,827 October views, not family-titleLisp (programming language)at 19,386, and not short-titleLispat 6,672. - Pair
get_top_trendsrank with bothrank_changewindows andget_growthon the exact board string. Store each keyword'srecent_date.