Skip to content
For B2B SaaS

An AI agent for every customer, over that customer's own knowledge

You ship a B2B product, and each customer wants an assistant that knows their documents, tickets and notes. FoxNose gives every customer a separate space, a trust verdict on what goes into it, and a hosted MCP server for the agent.

Three problems, one backend

Isolation, trust and agent access together

Customer-facing agents fail in three places. Each one has a part of FoxNose built for it.

An agent works for one customer, Globex, with a short-lived token. Four cases, played in turn: it reads, searches, asks for another customer's ticket, and writes. Choose one to see what comes back.

How it fits together

One flow, five steps

From a customer signing up to an agent answering their questions.

  1. Model your customers as records

    Each customer is a record, and its articles, tickets, notes and files live under it. Your product reads one customer at a time by addressing that customer.

  2. Let customers upload

    Their users upload documents (see <a href="/product/files" class="text-gray-300 hover:text-white underline decoration-white/20 hover:decoration-white/40">Files</a>). Each file is scanned for malware, rendered to visible text and delivered with a verdict. The agent never receives the original file.

  3. Mint a token per user

    When a user opens the assistant, your backend signs a short-lived token for that user. The token is all the agent can see.

  4. Connect the agent

    Your agent connects to the MCP server with the token. It searches and reads that user's knowledge, and writes memory back only where you allow it.

  5. Review what looks wrong

    Suspicious uploads and agent notes wait in a queue in your dashboard. A reviewer releases or rejects them; nobody reads them meanwhile.

Your team, your app and the agent all work on the same customer records.

One knowledge base

Same records. Every side reaches them.

Your team and your app work with the records through the API. Your agents reach the same records through MCP or the SDKs. Each comes in with its own permissions, and everything written keeps a label of who wrote it.

Through the API

Your team
DashboardManagement API

Everything their role allows, across all customers

Your app
REST APITenant tokens

One signed-in customer's records, by its token

Activity on one copy of your records
  • Your teamedit customer → Customerssaved · trusted
  • Agent · SDKGET /tickets/ → Ticketsread
  • Your appGET /tickets/:key/ → Ticketsread
  • Agent · MCPcreate_record · note → Notessaved · untrusted
Agents over MCP
MCPTenant tokens

The customer it works for, plus shared articles

Agents in your code
Python SDKTypeScript SDKLangChain

Whatever its key or customer token allows

Your agents, through MCP and the SDKs

Different sets of collections for different jobs? Create more than one API over the same records.

Connect the agent

One config, one user's view

The agent needs a URL and a token. The tools it sees are built from that token, so it is told only about the collections it can reach.

mcp config
{
  "mcpServers": {
    "foxnose": {
      "type": "http",
      "url": "https://mcp.foxnose.net/_mcp",
      "headers": {
        "Authorization": "Bearer fxt_<token your backend signed for this user>"
      }
    }
  }
}

Mint a fresh token before the old one expires. Tokens last 15 minutes by default.

For connectors in chat products that cannot call your backend, FoxNose will run the OAuth flow and your backend will vouch for the user (soon). How tokens and OAuth work →

What teams build

Assistants that know one customer well

Support assistant

Answers from a customer's own help articles, tickets and uploaded contracts, and from no one else's.

Team assistant

Answers a customer's team from their own docs and notes, and keeps what it learns as memory in their space.

Claims and case handling

Works over the files attached to a case, with a verdict on each document.

Hiring and screening

Reads résumés that applicants upload, with hidden text reported rather than delivered.

Learn more

Comparing options? FoxNose vs a headless CMS · FoxNose vs a database backend

Build the agent your customers can trust

Start with one customer record and one collection. The same model carries you to every customer you add.