# SociaVault Threads Profile Lookup

> SociaVault Threads Profile Lookup 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-13).

Fetches a Threads user's profile data by handle via the SociaVault social data proxy, paid per call with x402.

## Facts

- Endpoint: GET https://social.gedx402.com/v1/sociavault/threads/profile
- Price: $0.014/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sociavault-threads-profile-lookup-6ad8e14c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OQeEYCGSYSvDw_2vikLEf

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 sociavault-threads-profile-lookup-6ad8e14c
```

Example prompt: Can you pull up the Threads profile for the handle @zuck using SociaVault?

## When to prefer this

Use this endpoint when you need to fetch a single Threads user's profile data programmatically and are comfortable with per-call micropayment via x402. Prefer this over scraping or manual lookup when you need structured profile JSON returned reliably. Best suited for agents that already handle x402 payment flows.

## Known failure modes

- Handle not found — returns success: false or empty data object
- Invalid or missing handle parameter — malformed request error
- x402 payment failure — endpoint returns 402 Payment Required if payment is not properly attached
- Rate limiting or upstream SociaVault unavailability — service error response
- Private or suspended account — data may be empty or restricted

## How this service works

SociaVault social data ingest — profile, posts, transcript, and full API proxy. One x402 payment per outcome.

## Output

A JSON object with a 'data' field containing the Threads user's profile information (bio, follower counts, display name, etc.), a 'success' boolean, and a 'provider' field confirming SociaVault as the data source.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "handle": {
   "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/sociavault-threads-profile-lookup-6ad8e14c/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)