# For tool builders

> Markdown version of https://postlake.dev/use-cases/social-media-tools . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

If you are building the product, you should not also be building nine platform integrations underneath it.

## The problem

Every social tool starts by rebuilding the same plumbing: OAuth per network, media rules per network, analytics shapes per network, and a review queue for each. Months go into the layer none of your users will ever see.

## What PostLake does about it

### The plumbing, done

Publishing, scheduling, media, analytics, comments and engagement across every major network, in one shape.

### Your brand on the screen

Bring your own platform keys and the connection screen is yours, not ours. Your users never see a third party.

### Usage pricing that resells

You are charged per post, so your own pricing can sit on top without a per-seat floor you have to absorb.

### A capability registry to build a UI from

Every limit, media rule and option is queryable, so your composer can be generated from it rather than hardcoded and left to rot.

## How it fits together

Build against the API, supply your own platform credentials for white-label, and drive your UI from the capability endpoint.

## Common questions

**Can I white-label the connection screen?**

Yes. Supply your own platform app credentials and users authorise against your brand rather than ours.

**How do I keep my composer in step with platform rules?**

Read the capability endpoint. It returns every limit, media rule and per-network option, so your UI follows platform changes instead of being patched after them.

**Is the pricing resellable?**

It is usage-based per post with no seat licences, so your own pricing sits on top without a fixed floor to absorb.