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.
Isolation, trust and agent access together
Customer-facing agents fail in three places. Each one has a part of FoxNose built for it.
Every customer in their own space
Customers and their users get separate spaces in one knowledge base. A token from your backend keeps an agent inside one user's data.
A verdict on what customers upload
Files and agent writes are labelled, checked and given a verdict before another agent reads them.
Agents that read and write on their own
A hosted MCP server on every API, with the same permissions as your app. No tool server to build.
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.
One flow, five steps
From a customer signing up to an agent answering their questions.
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.
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.
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.
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.
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.
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
Everything their role allows, across all customers
One signed-in customer's records, by its token
- Your teamedit customer → CustomersCustomerssaved · trusted
- Agent · SDKGET /tickets/ → TicketsTicketsread
- Your appGET /tickets/:key/ → TicketsTicketsread
- Agent · MCPcreate_record · note → NotesNotessaved · untrusted
The customer it works for, plus shared articles
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.
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.
{
"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 →
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.
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.