HomeBuild

Build with tools your agent operates.

Pages, forms, bookings, chat and optional meeting memory, through one tool registry, a REST API and an MCP connection.

Open the connection guideSee agent integrations
Pages, forms, bookings, chat and optional meeting memory, through one tool registry, a REST API and an MCP connection.
Where it shows up

Three ways to build on it.

I already have an agent

Connect an MCP client, read answers and receive follow up tasks.

I am building an app

Use API keys with specific scopes on your backend, and keep secrets on the server.

I need an internal agent

A hosted pilot reads authorized results and prepares drafts, with activation and credits.

Today

Every product you add is another API to learn.

A link tool, a form tool and a calendar tool, each with its own auth, its own errors and its own idea of permissions.

Without an agent, every time
Learn a new API per productevery product
Handle each one's authseparately
Map errors your agent can act onby hand
Limit what the agent may dorarely possible

Your agent ends up with too much access or not enough tools.

With your agent

One registry, three surfaces.

The same tools appear in MCP, the REST API and the in app agent, with strict inputs and errors that say what to do next.

  • Discovers only the tools its permissions allow
  • Gets a hint with every error, and the smallest scope that unlocks it
  • Asks the owner for an app or a permission in one request
  • Receives events and follow up jobs with receipts

“Connect to instanceof.ai and list what you can do here.”

Your agent is working

Connected over MCP with a scoped key

Found the installed apps

Listed the tools this key may use

Ready to workAsk the owner for more access when a task needs it.
Works together

Your agent, every product.

  1. Your agent
  2. Link page
  3. Form
  4. Booking
  5. Site chat
  6. Meeting

One connection reaches every installed product, within the scopes you grant.

You stay in control

Built for agents, governed by people.

Strict inputs

An unknown field is an error, never silently dropped.

Only a person installs

Agents request apps and permissions; owners approve them.

Compatibility is honest

It depends on the client's version and configuration. Read the guide before connecting.

Questions

What people ask before starting.

Where is the documentation?

In the developer guide, llms.txt for agents, and an OpenAPI description of every endpoint.

Does MCP start my agent?

No. MCP connects tools to an agent that is running. It does not start one.

Can I use it from a backend?

Yes, with scoped API keys kept on the server.

Keep exploring
Bring the AI agent you already trust.

Connect OpenClaw, Claude Code, Codex, Grok or another compatible agent to the customer journey. Keep the model you chose and control what it can do in instanceof.ai.

You say what you need. Your agent builds it. You approve.

Pages, forms, chat and bookings in one account, operated by the agent you already use or by one we host. Everything starts as a draft and nothing goes live without you.

A customer message is not a permission.

Someone may try to talk your agent into revealing information or doing something you did not allow. Access limits do what instructions alone cannot.

Give your agent real tools.

Read the guide and connect in minutes.

Open the connection guide