# What people build on PostLake

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

- [AI agents](https://postlake.dev/use-cases/ai-agents.md): The case PostLake was built for. An agent that can write a post but cannot publish it is only half an agent.
- [SaaS products](https://postlake.dev/use-cases/saas-products.md): Your users want to publish from inside your app. You do not want to spend a quarter building that.
- [Marketing agencies](https://postlake.dev/use-cases/marketing-agencies.md): Many clients, many accounts, one integration, and no seat licences.
- [Content repurposing](https://postlake.dev/use-cases/content-repurposing.md): One idea, nine places, without nine copies of the same code.
- [AI content tools](https://postlake.dev/use-cases/ai-content-generators.md): You have solved the writing. Publishing is the other half, and it is more tedious than it looks.
- [E-commerce](https://postlake.dev/use-cases/e-commerce.md): Your catalogue already knows what launched. Your social accounts should not need telling separately.
- [Newsrooms and publishers](https://postlake.dev/use-cases/newsrooms-publishers.md): The story is live. It should already be on every network, not queued behind somebody's afternoon.
- [Social media tools](https://postlake.dev/use-cases/social-media-tools.md): If you are building the product, you should not also be building nine platform integrations underneath it.