# Vector Namespace Semantic Search

> Vector Namespace Semantic Search is a paid API for AI agents from pearl-valium-stickers-upc.trycloudflare.com, paid per call via x402, $0.01/call, status down (last checked 2026-11-04).

Embeds a query using the same model used at index time and returns ranked semantic search hits with scores, text, and metadata from a private vector collection.

## Facts

- Endpoint: POST https://pearl-valium-stickers-upc.trycloudflare.com/v1/search?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vector-namespace-semantic-search-5e7ea315
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e5BQmfStJL4agXKWHxCch

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vector-namespace-semantic-search-5e7ea315 -d '<json body>'
```

Example prompt: Search my 'product-docs' namespace for anything relevant to 'how do I reset a user password' and return the top 5 hits with their scores and matched text.

## When to prefer this

Choose this endpoint when you have already indexed documents into a private vector namespace on this service and need to perform semantic similarity search without sending data to a third-party cloud. Prefer it over generic vector DBs (Pinecone, Weaviate) when privacy is a concern since everything runs locally on the operator's hardware. It pairs naturally with the sibling index endpoint on the same host.

## Known failure modes

- Namespace not found — collection was never indexed or wrong name provided
- Query embedding fails if the model is unavailable or overloaded on the local GPU
- Empty results if the namespace has no documents or the query has no semantic overlap
- Malformed input schema causes a 4xx error if 'hits' array or query text is missing
- Slow response or timeout if the RTX 5090 is busy with a concurrent heavy task
- Payment failure via x402 if USDC balance is insufficient or wallet is misconfigured

## How this service works

Search a namespace you indexed: the query is embedded on the same model and matched against your collection. Returns hits with score, text and metadata, plus latency.

## Output

Returns an array of ranked hits, each containing a relevance/similarity score (cosine), the matched document text, and associated metadata. Also includes query latency in milliseconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hits": {
   "type": "array"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vector-namespace-semantic-search-5e7ea315/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pearl-valium-stickers-upc.trycloudflare.com](https://www.zero.xyz/host/pearl-valium-stickers-upc.trycloudflare.com/llms.txt)