> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/hugging-face/spaces-semantic-search>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/hugging-face/spaces-semantic-search.mdx>

---

# Hugging Face Semantic Space Search API

Describe what you need in plain words and get the Spaces that fit, ranked best first.

`GET /v1/hugging-face/spaces/semantic-search` takes a required `query` written in plain words and returns `results`, the Spaces ranked by how well they match. Narrow the list with `category` and `sdk` (`gradio`, `streamlit`, `docker` or `static`).

Each result is a repository summary with `id`, `url`, `author`, `sdk`, `spaceStage`, `likes`, `downloads`, `tags` and `trendingScore`. This is not keyword search over ids; it matches the meaning of the description.

## Request

- **Endpoint:** `GET /v1/hugging-face/spaces/semantic-search`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by description
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/hugging-face/spaces/semantic-search/get)
- **Platform page:** [/platforms/hugging-face](https://www.socialfetch.dev/platforms/hugging-face)

## FAQ

### How is this different from the Spaces search endpoint?

The Spaces search endpoint matches ids, tags and card text. This one ranks by how well a Space matches the meaning of your description.

### Can I restrict the SDK?

Yes. sdk accepts gradio, streamlit, docker or static. category narrows it further.

### Why are the scores not returned?

The results are already in ranked order. The endpoint returns the repositories, not the similarity scores.

### How much does a semantic search cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.