Bissap mascot - a cute pink character with flowers

Bring Your Own Agent

Make any app
agent-ready.

Bissap is a tiny “agent door” you add to your backend. Users connect their own AI agents safely. You just open the door.

Shipping lane

The fastest way to make your app agent-ready.

Built for vibe coders, indie hackers, and devs who ship fast.

Let users connect their AI agents safely, without having to rebuild your backend.

Agent safetyLive
Scoped keys with intent gating
Cloud revocation broadcast with local cache
Zero rewrites: drop-in middleware

Think of Bissap as your app's agent bouncer.

Its job is to let your users' AI agents in, give them scoped access, and kick them out if they misbehave.

0min

Setup. Done. Ship it.

A few lines of code and your app speaks agent. If you are faster than that, use the remaining 14 minutes to Google what “bissap” is. You'll thank us later.

>If you take longer: it might be you, it might be us. No judgment.

>If you finish faster: congrats, you actually know what you're doing.

Security defaults

Scoped keys, revocable tokens, typed intents. We did our homework so your agents can't go rogue. Probably.

Their agent, your app

Your users already have agents. Let them plug in. You don't host models, pick providers, or pretend to be an AI company.

User Agent
Your App
Bissap
Done

Three boring building blocks.

That unlock the fun stuff.

Keys

Who is this agent?

Revocable, scoped API keys for each user's agent. Full audit trail. One click to cut off a rogue bot. Sleep well at night.

Intents

What can it do?

A menu of actions, not a free-for-all. Agents pick from what you allow. Typed, versioned, impossible to misuse.

Inbox

What happened?

Event notifications built for agents. Your app pushes updates, agents poll and acknowledge. No WebSockets. No drama.

MCP compatibilityComing soon

If you are wondering, Is Bissap an MCP?

Not exactly. MCP standardizes how agents talk to tools. Bissap gives your app a safe agent door by handling identity, scoped access, and instant revocation so agents can connect without breaking your backend.

It does not require MCP. Intents define what an agent is allowed to do inside your app. MCP defines how a model formats tool calls.

Different layer. You can use both, but you do not have to.

Already using an MCP?

We are building a connector so you can plug Bissap into your existing setup. Request beta access now and we will make sure you are the first to try it out.

MCP tooling formatBissap agent doorWorks together or solo

But why?

Your users already talk to AI agents.

Right now they choose: open your app, or ask their agent.

That’s happening whether you build for it or not.

Who knows, maybe your next app won’t even have a UI.

But we still love a good interface. Some things are worth clicking.

# Install Bissap in your project

$npm install @bissap/core

# Mount in your backend (3 lines)

$bissap init

Without rewriting your app, hiring an ML team, or figuring out what a “vector embedding” is.

Ready to open the agent door?

Get started in minutes. Bissap handles the plumbing so you can ship features.