Product

Agentic SaaS: How LinksOnLink Is Built for AI Agents

Dilusha Gonagala
#agentic-saas#mcp#ai-agents#muse#creator-commerce
Muse's small headphone-wearing agent exploring creator pages and digital products beside the LinksOnLink logo

A lot of software still makes you open a dashboard to do a simple job. I want LinksOnLink to work when a creator says, “Put my new guide on my page,” or when a customer asks, “Where can I buy it?”

That’s what I mean by agentic SaaS. Give agents access to real product functions with permission. Creators choose what to make public, and buyers decide whether to pay.

We’re building LinksOnLink in that direction. We’ve also submitted it for review as a connector on Meta’s Muse Connector Platform.

What agentic SaaS looks like for a creator

Say you’re launching a guide. You ask your assistant:

Create a short link for my new guide, add it to my creator page, and show me how last week’s links performed.

LinksOnLink already has a live Model Context Protocol (MCP) server. Authenticated assistants can use it to work with links, creator pages, collections, and analytics. Developers can use our API to build their own workflows. The agent uses the same product functions that power LinksOnLink.

Now picture someone looking for your work:

Find Dilusha’s Kubernetes guide. What does it cost, and where can I get it?

Our MCP server has read-only tools for finding public creator pages, their links, and the digital products listed on them. It can return a product’s details and the page where someone can get it. Password-protected, age-restricted, disabled, and inactive content is excluded. Connecting to the MCP server still requires authentication.

This gives a creator’s page another job. Alongside helping human visitors, it gives a connected assistant a way to find the work the creator has chosen to make public.

Why we’re applying to Muse

Meta says the Muse Connector Platform will let people reach services by asking Muse for what they need. Connectors go through review and testing before they can appear in Muse’s directory.

Stripe announced that Muse uses its Link wallet for agent purchases. Stripe says US consumers must approve the total for each purchase in chat. I like that boundary. Let the agent help you shop; you decide whether to pay.

I want creators to keep control of their pages, links, and products in LinksOnLink while Muse helps people find that work. That’s the best of both worlds we’re working toward. We’ve submitted our Muse connector application and are working on the integration. The application is awaiting review; LinksOnLink is not yet an approved Muse connector.

Can an agent buy a product yet?

Creators can sell digital downloads on LinksOnLink through their connected Stripe accounts. Buyers visit the creator’s page and use the existing Stripe checkout. Our MCP tools can show a product’s public details and where to find it. They cannot start a purchase or subscribe someone to a creator.

Stripe’s Link wallet integration with Muse does not turn LinksOnLink checkout into an in-chat purchase. If we add a purchase action for agents, we’ll need Muse’s technical requirements. The buyer must be shown the product and total and confirm the purchase. The order must still reach our existing delivery flow.

Making your work easier to find

Name your public page so someone can recognize it. Make link titles say where they go. Give each product a title and description that say what it contains. “Kubernetes Deployment Guide” is more useful than “New thing.”

That helps people and search engines today. It also gives a connected assistant something useful to find. You can build your creator page on LinksOnLink now. I’ll share more about Muse when we have an integration to show.

← Back to Blog