# QuantaFlow x402 API Gateway – Rapid Instagram Data

> QuantaFlow x402 API Gateway – Rapid Instagram Data is a paid API for AI agents from quanta-roan.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Proxies requests to a rapid Instagram data upstream service via x402 micropayment protocol, returning Instagram profile, post, or social data.

## Facts

- Endpoint: POST https://quanta-roan.vercel.app/api/service/rapid-instagram-data19?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapid-instagram-data-badf5371
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6YNGd-YRmK7-12W8qJRva

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 quantaflow-x402-api-gateway-rapid-instagram-data-badf5371 -d '<json body>'
```

Example prompt: Fetch the public profile data for the Instagram account 'natgeo' — I need their follower count, bio, and recent post count.

## When to prefer this

Choose this endpoint when you need programmatic access to public Instagram data (profiles, posts, engagement metrics) and are operating in a web3/x402 micropayment context where per-call USDC billing is acceptable. Prefer this over manual scraping or OAuth-based Instagram APIs when you need lightweight, pay-per-use access without API key management.

## Known failure modes

- Payment failure: x402 payment not accepted or insufficient USDC balance results in 402 response
- Invalid path: unrecognized Instagram API path returns upstream error or 404
- Rate limiting: upstream rapid Instagram API rate limit exceeded returns 429
- Instagram account not found: queried username or post ID does not exist returns null or error object
- Malformed query: missing or invalid query parameters forwarded to upstream cause 400-level errors

## How this service works

Every request, a quantum of value. x402 protocol-based payment endpoint for web3/DeFi tools.

## Output

The upstream Instagram API response body passed through as-is after successful x402 micropayment, typically containing JSON with profile data, post metadata, engagement metrics, follower counts, bios, or media URLs depending on the path queried.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Optional JSON body forwarded to POST requests."
  },
  "path": {
   "type": "string",
   "description": "Path below the selected upstream origin."
  },
  "query": {
   "type": "object"
  },
  "method": {
   "enum": [
    "GET",
    "POST"
   ],
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "description": "The upstream response body and content type are passed through after successful payment."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quantaflow-x402-api-gateway-rapid-instagram-data-badf5371/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quanta-roan.vercel.app](https://www.zero.xyz/host/quanta-roan.vercel.app/llms.txt)