# GEDX402 Social – SociaVault Threads User Search

> GEDX402 Social – SociaVault Threads User Search is a paid API for AI agents from social.gedx402.com, paid per call via x402, $0.014/call, status unknown (last checked 2026-09-15).

Search for Threads users by query string via the SociaVault social data proxy, paid per call via x402 micropayment.

## Facts

- Endpoint: GET https://social.gedx402.com/v1/sociavault/threads/search-users
- Price: $0.014/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gedx402-social-sociavault-threads-user-search-66b1c700
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jqo8sjWq_IoIxkj6lhobE

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 gedx402-social-sociavault-threads-user-search-66b1c700
```

Example prompt: Can you search Threads for users matching 'coffee roasters' and show me the profiles that come up?

## When to prefer this

Use this endpoint when you need to search for Threads users by name, keyword, or topic and want pay-per-call micropayment access without a subscription. Prefer this over direct Threads API access when you lack platform credentials or need a lightweight proxy approach with x402 payment.

## Known failure modes

- Empty or missing query returns no results or validation error
- Query too broad returns generic or low-quality results
- Payment failure via x402 results in 402 response blocking access
- SociaVault upstream unavailable causes proxy error
- Rate limiting if too many calls made in succession
- Invalid query characters may cause malformed request error

## How this service works

SociaVault API proxy — threads-search-users. Query/body matches https://docs.sociavault.com/api-reference/openapi.json. GET/POST per route; x402 per call. $0.014 USDC per request.

## Output

A JSON response with a data object containing matching Threads user profiles or accounts that fit the search query, along with a success flag and provider attribution from SociaVault.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "success": true,
  "provider": "sociavault"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gedx402-social-sociavault-threads-user-search-66b1c700/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from social.gedx402.com](https://www.zero.xyz/host/social.gedx402.com/llms.txt)
