# QuantaFlow x402 API Gateway - Instagram Rapid Endpoint

> QuantaFlow x402 API Gateway - Instagram Rapid Endpoint 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-12).

Proxies requests to a rapid Instagram-related upstream API via x402 micropayment protocol, charging $0.01 USDC per call.

## Facts

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

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-instagram-rapid-endpoint-798daff0 -d '<json body>'
```

Example prompt: Use the QuantaFlow x402 rapid-instagram gateway to fetch the public profile data for Instagram user 'natgeo' — send a GET-style request to the /users path with the username as a query parameter.

## When to prefer this

Choose this endpoint when you need to access Instagram data through a pay-per-call model using x402/USDC micropayments rather than a traditional subscription API key. It is suitable for low-volume, on-demand Instagram data lookups where you want crypto-native billing and do not want to manage a RapidAPI subscription. Avoid if you need high-volume batch Instagram data or guaranteed SLA.

## Known failure modes

- Payment failure: insufficient USDC balance or wallet not connected causes 402 Payment Required response
- Upstream API error: the Instagram rapid API returns a 4xx or 5xx which is passed through
- Invalid path: requesting a non-existent Instagram API path returns an error from upstream
- Rate limiting: upstream rapid API rate limits may trigger even after payment succeeds
- Malformed query object: improperly structured query parameters may cause upstream rejection

## How this service works

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

## Output

The raw response body and content type as returned by the upstream Instagram rapid API, passed through transparently after the x402 micropayment of $0.01 USDC is processed. The agent receives whatever JSON or data the upstream Instagram service returns for the requested path and parameters.

## 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-instagram-rapid-endpoint-798daff0/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)