How can we access semantic search through the API? search.json does not seem to have semantic (even though, I remember they did at some point?) discourse-ai/embeddings/semantic-search?q= is called after search.json, good results are correct when I open the URL including query I just did. But if I discourse-ai/embeddings/semantic-search?q=differentQuery directly the results do not make sense at all. What do I miss here?

You can do a pure embeddings search using: https://DOMAIN/discourse-ai/embeddings/semantic-search.json?hyde=false&q=.... That disables the hyde portion so it is rate limited a lot less aggressively. Additionally ideally use an api key for the call which relaxes a lot of the limits.

Thanks, this works! [image] Sam Saffron: Additionally ideally use an api key for the call which relaxes a lot of the limits. I whitelisted my IP’s from ratelimiting in app.yml, I think I read somewhere that this was also a solution to bypass ratelimits if I’m correct.

[image] MarcP: I whitelisted my IP’s from ratelimiting in app.yml, I think I read somewhere that this was also a solution to bypass ratelimits if I’m correct. Not really, search limits are generally implemented in the app, skipping hyde is critical here: app/controllers/discourse_ai/embeddings/embeddings_controller.rb ca800f7aa MAX_HYDE_SEARCHES_PER_MINUTE = 4 MAX_SEARCHES_PER_MINUTE = 100 You only get 4 hyde queries a minute (where we expand the search term for you), you get up to 100 non hyde ones (provided other rate limits are relaxed)

[image] Sam Saffron: skipping hyde is critical here I will pass this param for sure. My question was actually: passing API key is effectively the same as excluding an IP from ratelimits? Or did you mean hyde=false only works IF an API key is passed?

Got it, the app.yml flag I was talking about seems to lift nginx ratelimits (DISCOURSE_MAX_REQS_PER_IP_EXCEPTIONS) The topic below made it a bit more clear to me: [image] Available settings for global rate limits and throttling Self-Hosting Discourse ships with 3 different global rate limits that can be configured by site admins. Global per-ip rate limits These limits apply to every unique IP address that hits the Discourse application. (files that are served directly from the filesystem or the CDN are excluded) By default this rate limit is enabled, you may disable it or set it to a reporting mode. DISCOURSE_MAX_REQS_PER_IP_MODE : default block, this rate limit applies out of the box. (other options are warn, warn+block, and n…

Semantic Search API

Product Support

sam (Sam Saffron) December 17, 2024, 6:49am 6

both are unrelated. api has different knobs for rate limits, you can relax it more than other parts of the app in global settings

Topic		Replies	Views
API access to the embedding(s) for a post Feature completed	3	661	September 12, 2024
Discourse AI - AI search Site Management how-to , ai , ai-search	9	3861	July 2, 2025
Is it possible to make the default search Semantic search on the site? How much do these calls cost? Feature ai , ai-search	6	1533	September 8, 2023
Getting a lot of no results for semantic search Product Support ai , ai-search	20	880	March 13, 2025
Support for Vanilla Embedding Search Feature ai , ai-search	2	201	June 28, 2025

Semantic Search API

Related topics