canonical: https://jentic.com/apis/getphyllo.com/phyllo

# Getphyllo Phyllo Creator Economy API

The Phyllo Creator Economy API retrieves a connected creator's identity, audience demographics, published content, comments, and income across social and commerce platforms through one unified interface. Your app creates a user, issues an SDK token so the creator links their accounts, and then reads normalized profile, engagement, and payout data back from each linked work platform. Income is split into social and commerce transactions and payouts, and webhooks notify your systems when fresh data arrives.

## For AI agents

Retrieve a creator's linked social and commerce accounts, profile and audience data, published content, and income transactions and payouts through Phyllo's unified creator-data API.

## Scope

Does not post content, run ad campaigns, or send creator payments. Use for retrieving connected creators' social and commerce data only.

## Capabilities

- Create a user and issue an SDK token so a creator can link their platform accounts
- Read connected account status and update its monitoring settings
- Retrieve creator profiles and audience demographics across linked work platforms
- List published content, content groups, and comments for a connected creator
- Pull social and commerce income transactions and payouts for a creator
- Register webhooks to receive updates when creator data refreshes

## Use cases

### Agent-Driven Creator Onboarding

An AI agent connected through Jentic onboards a creator by creating a Phyllo user, issuing an SDK token for account linking, and then reading back the connected accounts and profile once the creator authorizes. Because Phyllo normalizes data across YouTube, Instagram, TikTok, and other work platforms, the agent handles one schema instead of a different integration per platform.

Example prompt: Create a Phyllo user, generate an SDK token, then list the connected accounts and retrieve the creator profile

### Influencer Audience and Engagement Analysis

Marketing tools analyzing an influencer pull audience demographics, published content, and comments for a connected account. Phyllo returns audience breakdowns and content items filtered by account, so an agent assembles a creator's reach and engagement picture without scraping each platform directly.

Example prompt: Retrieve audience demographics and the latest content items for a connected account and summarize engagement

### Creator Income Reconciliation

Platforms paying creators reconcile earnings by pulling social income transactions and payouts alongside commerce income transactions. Phyllo separates social and commerce income and exposes individual transactions and payouts, so a finance agent reconciles what a creator earned against what was paid out.

Example prompt: Retrieve social income transactions and payouts for a creator and match each payout to its transactions

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/users` | Create a user to represent a creator |
| POST | `/v1/sdk-tokens` | Issue an SDK token for account linking |
| GET | `/v1/accounts` | List connected creator accounts |
| GET | `/v1/profiles` | Retrieve creator profiles |
| GET | `/v1/audience` | Retrieve audience demographics |
| GET | `/v1/social/income/transactions` | Retrieve social income transactions |

## Key resources

- **Users and SDK tokens** — Create users and issue SDK tokens so creators can link their platform accounts
- **Accounts and work platforms** — List connected accounts, inspect status, update monitoring, and browse supported work platforms
- **Profiles and audience** — Retrieve creator profiles and audience demographics across linked platforms
- **Content and comments** — List published content items, content groups, and comments for a connected creator
- **Income** — Retrieve social and commerce income transactions and payouts for a creator
- **Webhooks** — Register and manage webhooks for data-refresh notifications

## 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:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 75 / 100
- **View full report:** https://jentic.com/apis/getphyllo.com/phyllo/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 Phyllo by hand means handling its basic auth with a CLIENT_ID and CLIENT_SECRET, running the SDK-token flow so creators link accounts, and tracking refresh webhooks yourself. Through Jentic you install once, import Phyllo from the API Directory, store the credentials once, and your agent calls the creator-data operations.
- **Permission scoping:** Phyllo carries read operations for profiles, audience, content, and income alongside write operations that create users, update account monitoring, and manage webhooks. You choose the operations your agent may call, so a rule can keep it to the read operations and leave user creation or webhook deletion out unless you add them.
- **Credential handling:** Your Phyllo CLIENT_ID and CLIENT_SECRET are held by your own Jentic One instance, encrypted, and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve creator audience demographics' or 'pull social income payouts', and Jentic returns the matching Phyllo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **People Data Labs API** — People Data Labs enriches person and company records, versus Phyllo's focus on connected creators' social and income data.
- **FullContact API** — FullContact resolves identities and appends social profiles from an email or phone, where Phyllo reads data from accounts a creator links directly.
- **Apify API** — Apify scrapes public web and social pages, complementing Phyllo's authorized first-party creator data.

## FAQ

### What authentication does the Phyllo Creator Economy API use?

The API uses HTTP basic authentication, sending your CLIENT_ID as the username and CLIENT_SECRET as the password, per its OpenAPI spec. Through Jentic those credentials are held by your own Jentic One instance and attached to each request at execution time, so they never appear in your agent's prompt or logs.

### Can I retrieve creator income data with the Phyllo Creator Economy API?

Yes. Phyllo exposes social income transactions and payouts and separate commerce income transactions for a connected creator. Your agent lists transactions and payouts and reads individual records by id, so it can reconcile what a creator earned against what was paid out.

### What are the rate limits for the Phyllo Creator Economy API?

The OpenAPI spec does not specify rate limits. Check the Phyllo documentation at https://docs.getphyllo.com/ for current limits before running high-volume data pulls.

### Is there a Phyllo MCP server?

You do not need an MCP server to give your agent the Phyllo Creator Economy API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the creator-data operations on demand without loading an extra server's tool definitions into its context.

### Can I limit what my agent is allowed to do with the Phyllo Creator Economy API?

Yes. Write a rule that allows only the read operations your agent needs, such as retrieving profiles, audience, and income, so it cannot create users, update account monitoring, or delete webhooks. You choose the operations it may call, and every call it makes is logged.

### How do I pull creator data through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Phyllo Creator Economy API from the Jentic directory and search by intent such as 'retrieve creator audience demographics'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.