canonical: https://jentic.com/apis/permutive.com/permutive

# Permutive Audience API

Permutive API for audience segmentation, cohort management, event tracking, identity resolution, contextual signals, and taxonomy management.

## For AI agents

Manage permutive.com resources and operations programmatically.

## Scope

Provides access to permutive.com resources and operations as documented in the OpenAPI specification.

## Capabilities

- Access and manage permutive.com resources
- Integrate permutive.com functionality into workflows
- Automate permutive.com operations

## Use cases

### permutive.com Integration

Integrate Permutive Audience API into your application or workflow to automate operations and access resources programmatically.

Example prompt: Use the Permutive Audience API to perform operations against permutive.com resources.

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 76 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 33 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/permutive.com/permutive/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Permutive by hand means setting the X-API-Key header or k query key, choosing between the api.permutive.app and api.permutive.com hosts, and threading cohort, import, and segment ids through your calls yourself. Through Jentic you install once, import the Permutive Audience API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Permutive puts the resource id in the URL path (`/cohorts-api/v2/cohorts/{cohortId}`, `/audience-api/v1/imports/{importId}/segments/{segmentId}`), so a rule can pin your agent to one cohort or import. You choose the operations it may call, so writing events or identifying users is included only if you add it and reads can stand alone.
- **Credential handling:** Your Permutive API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read a cohort definition' or 'submit audience events', and Jentic returns the matching Permutive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## FAQ

### What authentication does the Permutive Audience API use?

The Permutive Audience API uses apiKey authentication. Through Jentic, credentials are stored encrypted and injected at execution time so they never enter the agent's context.

### How many endpoints does the Permutive Audience API have?

The Permutive Audience API exposes 12 endpoints across its surface area.

### Can I limit what my agent is allowed to do with the Permutive Audience API?

Yes. Because you run Jentic One yourself, you decide which Permutive operations your agent may call and which credentials it may use, so you can allow read-only access to cohort definitions while excluding operations that write events or identify users. Permutive carries the resource id in the URL path, such as the cohort id in `/cohorts-api/v2/cohorts/{cohortId}` or the import and segment ids in `/audience-api/v1/imports/{importId}/segments/{segmentId}`, so your rules can pin the agent to a single cohort or import. Write and identity operations are included only if you add them, and reads can stand on their own.