# GGWP API Hub – Instagram API Endpoint (ig-api-68)

> GGWP API Hub – Instagram API Endpoint (ig-api-68) is a paid API for AI agents from ggwp-ten.vercel.app, paid per call via x402, $0.093025/call, status unknown (last checked 2026-09-15).

Provides access to Instagram-related social media data via a pay-per-call API on the Base blockchain using the x402 protocol.

## Facts

- Endpoint: POST https://ggwp-ten.vercel.app/api/ig-api-68
- Price: $0.093025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ggwp-api-hub-instagram-api-endpoint-ig-api-68-dcd0e905
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kWjJhYEcXrMFT6MMDe57E

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 ggwp-api-hub-instagram-api-endpoint-ig-api-68-dcd0e905 -d '<json body>'
```

Example prompt: Can you pull the latest Instagram data for me using the GGWP ig-api-68 endpoint? I need the profile or post information returned as a result object.

## When to prefer this

Choose this endpoint when you need to access Instagram social media data programmatically and are operating within a crypto-native, pay-per-call environment using the x402 protocol on Base chain. It is suitable when you want a lightweight, per-request billing model rather than a monthly subscription, and when your agent stack already supports x402 micropayments.

## Known failure modes

- Payment failure due to insufficient USDC balance on Base chain
- Malformed or missing request body causing 400 error
- Instagram resource not found or unavailable returning empty result
- x402 protocol payment not processed, blocking API access
- Rate limiting or quota exceeded on the underlying Instagram data source
- Ambiguous or undocumented input schema leading to unexpected results

## How this service works

All-in-one API hub: Social Media, Jobs, Finance, Crypto, and Tools. Pay-per-call with x402 protocol on Base chain.

## Output

Returns a JSON object with a top-level 'result' key containing Instagram API response data, such as profile details, post metrics, or account information. The exact shape of the nested data depends on the specific Instagram resource queried.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "result": {
   "type": "object",
   "description": "API response data"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "example": {
  "result": {
   "data": "example response"
  }
 },
 "properties": {
  "result": {
   "type": "object",
   "description": "API response data"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ggwp-api-hub-instagram-api-endpoint-ig-api-68-dcd0e905/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ggwp-ten.vercel.app](https://www.zero.xyz/host/ggwp-ten.vercel.app/llms.txt)