# sna4an-mega-v3 /api/ig39

> sna4an-mega-v3 /api/ig39 is a paid API for AI agents from sna4an-mega-v7.vercel.app, paid per call via x402, $0.24/call, status unknown (last checked 2026-11-02).

Unknown endpoint within a large multi-domain API hub covering social media, finance, sports, AI, and e-commerce

## Facts

- Endpoint: POST https://sna4an-mega-v7.vercel.app/api/ig39?utm_source=zero.xyz
- Price: $0.24/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sna4an-mega-v3-api-ig39-37df6aac
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5mv4KtBGa8xMdUfleS_wR

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-mega-v3-api-ig39-37df6aac -d '<json body>'
```

Example prompt: Call endpoint ig39 on the sna4an-mega-v3 API hub and return whatever data it provides.

## When to prefer this

This endpoint should generally NOT be preferred due to its extremely low crawl quality score, opaque path, empty input schema, and lack of any documented output. It may be appropriate only if you already know from out-of-band documentation what ig39 specifically does within this hub and have no alternative source.

## Known failure modes

- No input schema defined so any required parameters are unknown and calls may fail silently
- Opaque endpoint path (ig39) with no documentation means unpredictable response structure
- Payment required at $0.24 USDC per call with no guarantee of useful output
- Endpoint may be auto-generated stub with no real backing logic
- Server may return 402 or 500 with no descriptive error message

## How this service works

Mega API hub - 118 endpoints covering social media, finance, sports, AI, e-commerce, and more

## Output

Unknown — the endpoint schema provides no input parameters and no documented output structure; the response format and content are entirely opaque based on available metadata.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sna4an-mega-v3-api-ig39-37df6aac/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from sna4an-mega-v7.vercel.app](https://www.zero.xyz/host/sna4an-mega-v7.vercel.app/llms.txt)
