# Gapup Content Audience Profile

> Gapup Content Audience Profile is a paid API for AI agents from mcp.gapup.io, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-18).

Returns demographics, interests, and segment fit for a media work or franchise to support marketing and audience acquisition targeting

## Facts

- Endpoint: POST https://mcp.gapup.io/api/v1/call/content_audience_profile?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gapup-content-audience-profile-65aa6802
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__NGlCxALiP4JCX9W_sAoL

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 gapup-content-audience-profile-65aa6802 -d '<json body>'
```

Example prompt: Pull the audience targeting profile for the work with ID 'tt0816692' — I need the demographics, interests, and segment fit so I can set up our acquisition campaign.

## When to prefer this

Use this endpoint when you need structured audience demographics, interests, and segment fit data for a specific media work or franchise from the Gapup enriched content catalog. Prefer it over general social listening tools when you need pre-computed, catalog-matched audience profiles ready for marketing activation. Best suited for campaign planning, acquisition targeting, and segment matching in entertainment and media contexts.

## Known failure modes

- Invalid or unknown entity_id returns an error or empty profile
- Unsupported entity_type value (not 'franchise' or 'work') causes a validation error
- Async mode returns a job_id that must be polled; polling before completion returns incomplete data
- Payment failure via x402 protocol prevents call execution
- Network timeout on synchronous calls for large or complex entities — use async=true to avoid

## How this service works

Audience targeting profile for a work, returns demographics, interests and segment fit for marketing and acquisition

## Output

Returns a structured audience profile including demographic breakdowns (age, gender, geography), interest categories, and marketing segment fit scores for the requested media work or franchise, enabling precise ad targeting and acquisition planning.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "async": {
   "type": "boolean",
   "description": "If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client timeouts."
  },
  "entity_id": {
   "type": "string",
   "description": "Entity id from content_catalog"
  },
  "entity_type": {
   "enum": [
    "franchise",
    "work"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gapup-content-audience-profile-65aa6802/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.gapup.io](https://www.zero.xyz/host/mcp.gapup.io/llms.txt)