# Sna4an Web Social API

> Sna4an Web Social API is a paid API for AI agents from sna4an-misc.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-19).

Proxies social and web data queries to RapidAPI sub-endpoints for social media insights and web data retrieval

## Facts

- Endpoint: POST https://sna4an-misc.vercel.app/api/web-social?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sna4an-web-social-api-1277984a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mZPYzyAtp7liwTEOmEDWF

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 sna4an-web-social-api-1277984a -d '<json body>'
```

Example prompt: Can you pull social profile data for the username 'techcrunch' using the web-social endpoint with path '/social-lookup' and the query param 'username=techcrunch'?

## When to prefer this

Use this endpoint when you need to access web or social data available through RapidAPI and want a single proxied interface with x402 micropayment billing at $0.08 per call, avoiding the need to manage RapidAPI credentials directly.

## Known failure modes

- Invalid or unsupported sub-endpoint path returns error or empty response
- Missing required query parameters causes downstream RapidAPI error
- Rate limiting or quota exhaustion on the underlying RapidAPI plan
- Network timeout if the proxied RapidAPI endpoint is slow
- Payment not processed results in 402 rejection before request reaches provider

## How this service works

News, AI, SEO, e-commerce, and utility APIs

## Output

A generic JSON object containing the response from the specified RapidAPI social/web sub-endpoint, with structure varying depending on the path and parameters used.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "path": {
   "type": "string",
   "description": "RapidAPI sub-endpoint path"
  },
  "params": {
   "type": "object",
   "description": "Query parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sna4an-web-social-api-1277984a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-misc.vercel.app](https://www.zero.xyz/host/sna4an-misc.vercel.app/llms.txt)