# Fume, AI agents for investment funds
# https://www.fume.finance

> Fume delivers and manages AI agents for fund administrators, fund managers,
> and family offices. Built and operated by FumeX AG (Locarno, Switzerland).
> The agents take over the manual back-office work in fund operations
> (compliance, document processing, NAV workflows, risk monitoring, investor
> communication) so the same team can serve more funds and more AUM.
> Separately, FumeX operates a fund tokenization platform: free fund
> tokenization (ERC-6909 shares on EVM chains), instant stablecoin
> settlement (OmniClear), a public directory of tokenized funds (Fund
> Registry), and an interactive Fund Builder that matches managers with
> legal/admin/custody/audit providers. The two lines are independent: you
> can hire the agents without tokenizing anything, and tokenize a fund
> without using the agents.

## What Fume actually does

- **Delivers and manages AI agents for fund operations** (the core offering):
  agents that monitor compliance, read documents, run NAV workflows, watch
  risk, and draft investor reports. Fume finds a manual process, builds and
  deploys an agent, and manages it while it runs the task on its own. Agents
  plug into existing fund admin, custody, and trading systems; private
  on-prem deployments with open-source models are available.
- **Tokenizes fund shares** (separate product line) using the ERC-6909
  standard on Ethereum, Arbitrum, Base, and selected EVM chains. The
  tokenization is free; revenue comes from protocol fees on flows. Every
  action (tokenize, mint, whitelist, run NAV, distribute) is an API call and
  the cap table is machine-readable.
- **Settles subscriptions and redemptions in stablecoins** through OmniClear:
  same-block clearing, multi-currency in / multi-currency out.
- **Runs the Tokenized Fund Registry**: a public, verifiable list of
  tokenized funds with onchain proofs.
- **Matches founders with the right service providers** through Fund Builder,
  a guided questionnaire that produces a tailored stack of legal, fund admin,
  custody, exchange/broker, audit, and AIFM partners.

## Key pages

- [Homepage](https://www.fume.finance/): Product overview and main entry point
- [Solutions](https://www.fume.finance/solutions): AI agent patterns, what Fume builds for fund administrators, managers, and family offices
- [Fund Builder](https://www.fume.finance/fund-builder): Interactive tool to assemble a complete fund stack, answer a short questionnaire, get matched with legal, admin, custody, exchange, audit (or AIFM) providers
- [Partner Directory](https://www.fume.finance/fund-builder/providers): Browse and compare every fund service provider in the Fume catalog, request introductions
- [Tokenization Engine](https://www.fume.finance/tokenization-engine): Free fund tokenization, with full onchain administration on the paid Fume Platform plan ($179/month), fully callable via API
- [For Asset Managers](https://www.fume.finance/tokenization-engine/for-asset-managers): How asset managers use Fume, secondary liquidity, live cap tables, programmable share classes
- [For Fund Administrators](https://www.fume.finance/tokenization-engine/for-fund-administrators): How fund administrators use Fume, automated reconciliation, onchain audit trail
- [Free Tokenization](https://www.fume.finance/tokenize-free): Tokenize an existing fund's shares for free, get listed on the Registry
- [OmniClear](https://www.fume.finance/omniclear): Stablecoin settlement infrastructure for funds, accept any currency, settle any way
- [Tokenized Fund Registry](https://www.fume.finance/registry): Public, open registry of tokenized investment funds with onchain verification
- [Registry list view](https://www.fume.finance/registry/list): Full table view of all listed funds with strategy, AUM, jurisdiction, chain
- [AI Agents for Funds](https://www.fume.finance/ai-agent-funds): AI agents delivered and managed for fund operations: NAV lifecycle automation, compliance, document processing, risk, investor communication
- [AI Agents for Fund Operations: The Complete Guide](https://www.fume.finance/resources/blog/ai-agents-for-fund-operations): What AI agents are, what they take over across the fund lifecycle, what FINMA and ESMA expect, and how funds deploy them
- [Automating NAV Calculation with AI Agents](https://www.fume.finance/resources/blog/automating-nav-calculation-with-ai-agents): How agents automate statement collection, transaction structuring, and NAV input loading around the existing NAV engine
- [AI Agents for Fund Administrators](https://www.fume.finance/resources/blog/ai-agents-for-fund-administrators): Adoption guide for administrators, which processes to automate first, shadow-to-production path, vendor questions
- [AI Agents vs. Chatbots vs. RPA in Fund Administration](https://www.fume.finance/resources/blog/ai-agents-vs-chatbots-vs-rpa-fund-administration): What each tool category does, where each one breaks, and which job belongs to which tool
- [Best AI Agents for Funds](https://www.fume.finance/resources/blog/best-ai-agents-for-funds): Ranked view of the agents worth deploying first, by hours removed per process
- [3 Ways to Increase Fund Administration Efficiency with AI](https://www.fume.finance/resources/blog/increase-fund-administration-efficiency-with-ai): Broker data extraction, NAV production into the existing accounting platform, and routine counterparty communication
- [AI Adoption Is Not AI Automation: What Actually Speeds Up Fund Operations](https://www.fume.finance/resources/blog/ai-adoption-vs-automation-fund-operations): Why chatbot rollouts do not shorten the NAV cycle, where agents already match a human operator, what to report instead of adoption
- [About](https://www.fume.finance/resources/about): Team, company, and origin story
- [Blog](https://www.fume.finance/resources/blog): Articles on AI agents for funds, fund tokenization, NAV automation, legal structures, regulation, and onchain finance
- [Contact](https://www.fume.finance/resources/contact-us): Direct contact form
- [Book a call](https://www.fume.finance/resources/book-a-call): Calendar booking for demo / consultation
- [Documentation](https://www.fume.finance/docs): Product documentation across AI agents, the Tokenization Engine, and OmniClear
- [Whitepaper](https://www.fume.finance/docs/tokenization/whitepaper/fume-intro): Tokenization Engine overview, technical design, use cases, legal considerations, FAQ

## Documentation and machine-readable content

- [Full content (markdown)](https://www.fume.finance/llms-full.txt): All documentation, blog posts, and marketing pages concatenated into a single markdown file for LLM ingestion
- [Docs overview](https://www.fume.finance/docs): What Fume builds, with links into every docs section
- [AI Agents docs](https://www.fume.finance/docs/ai-agents): Managed AI agents for funds. Engagement model, agent catalog, private/local deployments
- [OmniClear docs](https://www.fume.finance/docs/omniclear): Stablecoin settlement flow and supported fund structures
- [Tokenization Platform docs](https://www.fume.finance/docs/tokenization): Tokenization Engine section overview, linking whitepaper and user guides
- [Whitepaper](https://www.fume.finance/docs/tokenization/whitepaper): Tokenization Engine overview, technical design, use cases, legal considerations, FAQ
- [User guides](https://www.fume.finance/docs/tokenization/user-guides): Walkthroughs for fund setup, connecting wallets, NAV calculation, inflows/outflows, reports
- [Developer docs](https://www.fume.finance/docs/developers): The Fume developer surface — public REST API, OpenAPI spec, markdown negotiation, machine-readable indexes
- [Fume API reference](https://www.fume.finance/docs/developers/api-reference): Every endpoint, its parameters, and a curl example for each
- [API versioning and deprecation policy](https://www.fume.finance/docs/developers/versioning): What is versioned, what counts as a breaking change, and the 90-day Deprecation/Sunset notice
- [Agent access to Fume](https://www.fume.finance/docs/developers/agent-access): How an agent reads this site — markdown negotiation, bulk ingestion, structured data, 404 recovery
- [Security](https://www.fume.finance/docs/company/security): Cross-product security overview and data handling
- [About Fume](https://www.fume.finance/docs/company/about-fume): Company background

Three section-scoped indexes narrow this file to one part of the site:
[/docs/llms.txt](https://www.fume.finance/docs/llms.txt) lists every
documentation page with its raw-markdown URL,
[/resources/blog/llms.txt](https://www.fume.finance/resources/blog/llms.txt)
lists every article grouped by topic cluster, and
[/api/llms.txt](https://www.fume.finance/api/llms.txt) lists the callable
surface — every API operation, both MCP servers, and the documents describing
how to reach them.

Each documentation page is also available as raw markdown at
`/llms.mdx/docs/<group>/<slug>/content.md`. Each marketing page has a raw
markdown version at `/llms.mdx/marketing/<slug>/content.md`. Both can also be
fetched from the canonical URL with `Accept: text/markdown`, or by appending
`.md` to it (`/omniclear.md`, `/docs/developers/api-reference.md`, `/index.md`
for the homepage). Every page that has a markdown twin advertises it in a
`Link: <...>; rel="alternate"; type="text/markdown"` response header and in a
`<link rel="alternate">` tag. Appending `?mode=agent` to any of those URLs
returns the same markdown, for when you are handed a link and have no request
headers to set.

## MCP servers

Two Streamable HTTP MCP servers, both public, read-only, and unauthenticated.
Connect with any MCP client; no OAuth, no API key.

- [Product MCP server](https://www.fume.finance/mcp): Tools over the tokenized fund registry, the fund service provider directory, and Fume's own pricing
- [Documentation MCP server](https://www.fume.finance/mcp/docs): Tools that search and read the /docs content
- [Product server card](https://www.fume.finance/.well-known/mcp/server-card.json): Name, version, transport, and the full tool list before you connect. Mirrored at `/mcp/server-card`, beside the server, and at the root `/server.json` a registry submission points at
- [Documentation server card](https://www.fume.finance/.well-known/mcp/docs/server-card.json): The same, for the docs server. Mirrored at `/mcp/docs/server-card`
- [MCP server index](https://www.fume.finance/.well-known/mcp.json): Both servers in one document, with every tool and its parameter schema, in the shape a client mounts them from
- [AI catalog](https://www.fume.finance/.well-known/ai-catalog.json): Domain-level index of every machine-readable surface listed here
- [API catalog (RFC 9727)](https://www.fume.finance/.well-known/api-catalog): The public REST endpoints, linked to their OpenAPI description

## Natural-language query (NLWeb)

- [Ask endpoint](https://www.fume.finance/ask?query=how+does+Fume+calculate+NAV): Microsoft's NLWeb protocol over the /docs corpus. `GET` or `POST` with a `query` argument; also accepts `site`, `prev`, `decontextualized_query`, `query_id`, `mode` and `streaming`

Results come back as NLWeb result objects — canonical URL, name, relevance
score, description and a schema.org `schema_object` for each page. Add
`streaming=true` (or `Accept: text/event-stream`, or `Prefer: streaming`) for
the same answer as Server-Sent Events, with `start`, `result` and `complete`
frames. `mode` is accepted but always answered as `list`: this endpoint ranks
and returns pages, and runs no model over them.

## Agent-to-agent (A2A)

- [Agent card](https://www.fume.finance/.well-known/agent-card.json): What the agent is, which skill it serves, and the transport to open. The location A2A fixes, so a peer agent finds it without being told
- [A2A endpoint](https://www.fume.finance/a2a): JSON-RPC 2.0. `message/send` takes a question as text parts and returns an agent message: the ranked pages as prose, and the same hits again as a data part

One skill, `search-fume-docs`, over the same /docs corpus the ask endpoint and
the documentation MCP server read. Answers are messages, not tasks — the search
finishes inside the request, so there is nothing to poll; `tasks/*` and
`message/stream` are refused with A2A's `UnsupportedOperation` rather than a
"method not found" that would read as a typo. No authentication. `GET /a2a`
returns the endpoint's own facts plus a ready-to-send example call.

## Structured data feeds (Schema Feeds)

- [Schema map](https://www.fume.finance/schemamap.xml): Index of the feeds below, in the sitemap XML format with `sf:contentType` on each entry. Advertised as `Schemamap:` in robots.txt
- [Registry feed](https://www.fume.finance/schema-feeds/registry.jsonl): Every tokenized fund as a schema.org `FinancialProduct`
- [Provider feed](https://www.fume.finance/schema-feeds/providers.jsonl): Every fund service provider as an `Organization`
- [Blog feed](https://www.fume.finance/schema-feeds/blog.jsonl): Every article as an `Article`, with its dates

One JSON-LD object per line, UTF-8, `@id` on each. These are the same nodes the
detail pages embed, so reading a feed and crawling the pages give the same
answer — take the feed and skip 150 requests.

## Agent skills

Named procedures in the agentskills.io format, for a host that loads skills
rather than tools. Read the index first; fetch a body only when a task matches.

- [Skills index](https://www.fume.finance/.well-known/agent-skills/index.json): Every published skill, with the name and description a host matches on
- [Query the tokenized fund registry](https://www.fume.finance/.well-known/agent-skills/fume-tokenized-fund-registry/SKILL.md): Which surface to use, how to filter and page, and how to cite the result
- [Find fund service providers](https://www.fume.finance/.well-known/agent-skills/fume-fund-service-providers/SKILL.md): Resolving a category before filtering, and what Fume does and does not claim about the listings
- [Answer from the documentation](https://www.fume.finance/.well-known/agent-skills/fume-docs-research/SKILL.md): Search, then read the page, then cite the canonical URL
- [Call the public API](https://www.fume.finance/.well-known/agent-skills/fume-api-integration/SKILL.md): Versioning, the error envelope, rate limits, pagination, batching and safe retries

## Authentication and pricing

- [Authentication](https://www.fume.finance/auth.md): There is none on the read surfaces — no key, no OAuth, no token endpoint. Explains what the write endpoints do instead, how to retry one safely with `Idempotency-Key`, and how to reach a human
- [Pricing](https://www.fume.finance/pricing.md): Plans and figures as plain text. Human version at `/tokenization-engine#pricing`

## Public API

Unauthenticated, CORS-open, edge-cached. No key required. The OpenAPI document
is the source of truth; the rest of this section is a summary of it.

- [OpenAPI 3.1 specification](https://www.fume.finance/openapi.json): Every endpoint, parameter, and response schema. Mirrored at `/api/openapi.json`
- [Tokenized fund registry (JSON)](https://www.fume.finance/api/v1/registry/funds): The registry as data. Filters: `chain`, `status`, `assetClass`, `jurisdiction`, `q`, `limit`, `offset`/`cursor`
- [One registry fund (JSON)](https://www.fume.finance/api/v1/registry/funds/blackrock-buidl): `/api/v1/registry/funds/{id}`, where `{id}` is the registry slug
- [Fund service provider catalog (JSON)](https://www.fume.finance/api/v1/fund-builder/providers): The Fund Builder directory as data. Filters: `category`, `q`, `limit`, `offset`/`cursor`
- [One provider (JSON)](https://www.fume.finance/api/v1/fund-builder/providers/ogier): `/api/v1/fund-builder/providers/{id}`, where `{id}` is the provider slug
- [Documentation search](https://www.fume.finance/api/v1/search?query=NAV): Ranked fragments from /docs. For bulk ingestion use `/llms-full.txt` instead
- [Batch read (JSON)](https://www.fume.finance/api/v1/batch): `POST` up to 25 of the read paths above in one request; each result carries its own status, and a list read inside a batch returns at most 50 records

The list endpoints page two ways. `limit`/`offset` still work; `cursor` is
preferable — every list response carries a `nextCursor`, and passing it back
verbatim gets the next page without arithmetic. It is `null` on the last page.

The write endpoints under `/api` are this website's own forms (contact,
newsletter, provider introductions, registry listings). They are described in
the OpenAPI document, but production gates them behind a reCAPTCHA token that
only a browser produces. An agent that wants to reach a human should email
info@fume.finance.

Every error, on every endpoint and every status code, returns the same JSON
envelope: `error`, `code`, `message`, `hint`, `status`, `docs`. Branch on
`code`, show `message`, follow `hint`.

## Company

- Legal name: FumeX AG
- Brand: Fume
- Registered: CHE-342.025.757
- Address: Passaggio del Naviglio Vecchio 4, 6600 Locarno, Switzerland
- Contact: info@fume.finance
- App: https://app.fume.finance
- LinkedIn: https://www.linkedin.com/company/fumefinance/
- X (Twitter): https://x.com/fumefinance
- Telegram: https://t.me/fumefinance