> For the complete documentation index, see [llms.txt](https://fair-indonesia.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fair-indonesia.gitbook.io/docs/developers/guides/vet-a-creator.md).

# Vet a Creator

Before you sign a creator, you want two questions answered: is their audience real, and is their content safe to put a brand next to. This guide covers both. First you run profile analytics to get the credibility score and a read on fake followers. Then you run a brand-safety screening that scans their posts for risky content. Every call uses the base URL and your raw token in the `Authorization` header (no `Bearer` prefix).

All paths below are relative to the base URL:

* Trial / staging: `https://stg.api.fair-indonesia.com/api/fairservice`
* Production: `https://api.fair-indonesia.com/api/fairservice`

## 1. Check audience quality with `POST /profile-analytics`

Start with `POST /profile-analytics`. Pass the creator's handle or URL and the platform ID. The response gives you the audience `credibility_score` (a higher score means a more authentic following), the share of `follower_types` such as `MASS_FOLLOWERS`, and the engagement metrics you can sanity-check against the follower count. A creator with a big follower number but a low credibility score and thin engagement is a red flag for bought followers.

```bash
curl -X POST https://stg.api.fair-indonesia.com/api/fairservice/profile-analytics \
  -H 'Authorization: <your_token>' \
  -H 'Content-Type: application/json' \
  -d '{
  "identifier": "username/handle/url",
  "work_platform_id": "9bb8913b-ddd9-430b-a66a-d74d846e6c66"
}'
```

The fields that matter most for vetting:

```json
{
  "profile": {
    "follower_count": 0,
    "engagement_rate": 0,
    "audience": {
      "credibility_score": 0,
      "follower_types": [ { "name": "MASS_FOLLOWERS", "value": 0 } ],
      "significant_followers_percentage": 0
    }
  }
}
```

Read `credibility_score` together with `follower_types` and `engagement_rate`. The combination tells you whether the reach you are paying for is genuine.

## 2. Submit a brand-safety screening with `POST /screening`

A clean audience does not mean clean content. Submit the creator's profile to `POST /screening` to scan their posts for brand-safety risks. You can attach a `flagging_criteria_id` to control which categories get flagged, and you can pass more than one profile in a single request. The call returns an `id` for the screening job.

```bash
curl -X POST https://stg.api.fair-indonesia.com/api/fairservice/screening \
  -H 'Authorization: <your_token>' \
  -H 'Content-Type: application/json' \
  -d '{
  "flagging_criteria_id": "0450d8a8-cab9-4eb2-a7ba-00e59a8d78ad",
  "social_media_profiles": [
    {
      "work_platform_id": "9bb8913b-ddd9-430b-a66a-d74d846e6c66",
      "profile_url": "https://www.instagram.com/franknthecity"
    }
  ]
}'
```

```json
{
  "id": "3a1b...",
  "status": "IN_PROGRESS"
}
```

## 3. Read the risk score with `GET /screening/{id}`

Take the `id` from step 2 and poll `GET /screening/{id}` until `status` is `SUCCESS`, then read the result. The `report_summary` gives you the overall `risk_rating` along with how many content items were analysed and how many were flagged.

```bash
curl -X GET https://stg.api.fair-indonesia.com/api/fairservice/screening/3a1b... \
  -H 'Authorization: <your_token>'
```

```json
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "status": "SUCCESS",
  "report_summary": {
    "risk_rating": "LOW",
    "total_content_count": 0,
    "flagged_content_count": 0,
    "url": null
  }
}
```

If you want the individual flagged posts rather than the summary, call `GET /screening/{id}/contents`, which returns each flagged item with its `category_risks` and matched keywords.

Between a strong credibility score and a low risk rating, you have the evidence to approve a creator with confidence.

## Related

* [Creator Search & Analytics](/docs/developers/api-reference/creator-search-analytics.md)
* [Social Background Check](/docs/developers/api-reference/social-background-check.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fair-indonesia.gitbook.io/docs/developers/guides/vet-a-creator.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.