> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/pillar>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/pillar.mdx>

---

# Pillar API. Creator pages as JSON.

Read a public Pillar page by its handle: the creator's identity and socials, then every link, product, offer, video and embed the page shows, plus the brand collaborations in an open media kit.

- Links + offers + media kit
- Page order kept
- 1 credit per request

Social Fetch exposes one route under `/v1/pillar`. `GET /v1/pillar/profiles/{handle}` returns one public Pillar page, the page at `pillar.io/{handle}`. Send the handle as it appears in the page address, for example `angelstrife`; a leading `@`, the page URL or the media kit URL also works.

`data.profile` carries the identity: `handle`, `displayName`, `bio`, `tagline`, `location`, `avatarUrl`, `bannerImageUrl`, `verified`, `createdAt` and the creator `id`. `data.socials` holds the social and contact icons. `data.links` uses the same link shape as the Linktree, Lnk.Bio and Komi routes, plus a `description` line and the `group` heading each link sits under.

The page's blocks stay in order in `data.sections`. Featured products are in `data.products` (title, URL, price, currency, image, brand, rating), the creator's own offers in `data.offers` (digital products, courses, booked sessions and personal requests, with price, sale price and currency), and videos and embeds in their own lists. `data.mediaKit` gives the media kit URL and, when the creator does not ask visitors for an email or passcode first, the brand collaborations it lists.

Every response uses the `{ data, meta }` envelope. A handle with no page comes back as HTTP 200 with `data.lookupStatus` set to `not_found`.

## What you can get

- Creator identity: display name, bio line, tagline, location, avatar, banner image, verified flag and page creation date.
- Social and contact icons with a normalized platform slug, in the shared link-in-bio shape.
- Links with title, description, URL, thumbnail and position, plus the group heading each one sits under.
- Featured products with price, currency, image, brand and review rating.
- Offers the creator sells on the page: digital products, courses, booked sessions and personal requests, with price, sale price and currency.
- The public media kit: its URL, whether it is gated, and the brand collaborations an open kit lists.

## Pillar endpoints

| Endpoint | Request | Credits | Docs |
| --- | --- | --- | --- |
| Page | GET /v1/pillar/profiles/{handle} | 1 credit Failed requests are free | [docs](https://www.socialfetch.dev/docs/api/v1/pillar/profiles/handle/get) |

## How to start

1. **Create an API key.** Sign up at Social Fetch and copy a key (`sfk_…`). New accounts get 100 free credits.
2. **Call the page route.** Send `GET /v1/pillar/profiles/angelstrife` with `x-api-key`. The handle is the path after `pillar.io/`.
3. **Branch on lookupStatus.** Check `data.lookupStatus` before storing a row, then read the lists you need. `data.sections` gives the page layout if you want to rebuild it in order.

## Pricing

The Pillar route charges one credit per completed request, found or not found. `meta.creditsCharged` on every response is the billing source of truth. New accounts start with 100 free credits.

## Compared with the official API

Pillar has no public API for reading another creator's page. Social Fetch returns the public page as typed JSON, in the same link-in-bio shape as its Linktree, Lnk.Bio, Komi and Stan Store routes, with Pillar's products, offers, videos and media kit added.

## FAQ

### Is there a Pillar API for creator pages?

Yes. GET /v1/pillar/profiles/{handle} returns a public Pillar page as JSON. Authenticate with your Social Fetch API key in x-api-key.

### What handle do I send?

The path after pillar.io/, for example angelstrife. Letters, numbers, dots, underscores and hyphens, up to 64 characters. Case does not matter; the response gives the page's own case. A leading @, the page URL or the media kit URL is accepted.

### What is in the media kit part?

data.mediaKit has the kit's URL and a gated flag. When the creator does not ask visitors for an email or a passcode first, it lists the brand collaborations with brand name, site, logo, project name and description. A gated kit returns its URL and an empty list.

### What are offers?

Things the creator sells on the page itself: digital products, courses, booked sessions and personal requests. Each has a kind, title, short description, price, sale price when there is one, currency and image.

### Are hidden blocks or click counts included?

No. Blocks the creator has hidden are left out, as the page leaves them out, and click and view counts are never returned.

### How does a missing page look?

HTTP 200 with data.lookupStatus not_found, data.profile and data.mediaKit null, and every list empty. Branch on lookupStatus, not on the HTTP status.

### How much does the Pillar API cost?

One credit per completed request, found or not found. Check meta.creditsCharged on every response. New accounts get 100 free credits.

### Can I use the Pillar route from agents or MCP?

Yes. The route is a typed MCP tool and is reachable through Ask (POST /v1/ask) in plain English. Use the typed route for production jobs.

## Related

- [Pillar Page API](https://www.socialfetch.dev/platforms/pillar/profiles-handle): A creator page with its links, offers and media kit (`GET /v1/pillar/profiles/{handle}`).
- [Komi API](https://www.socialfetch.dev/platforms/komi): The same link-in-bio shape for Komi creator pages.
- [Ask in plain English](https://www.socialfetch.dev/ask): Route a natural-language Pillar question to the matching operation.
- [Hosted MCP](https://www.socialfetch.dev/mcp): Call the Pillar tool from Cursor or Claude with the same credit metering as REST.
