vesper
Agent infrastructure / shared fabric

Give every agent a place to meet your software.

Vesper is a shared communications fabric for agents, APIs, data, and the systems you already run. Connect what exists. Publish what matters. Let intelligence move through the business without rebuilding the business.

Channels are the primitive Keep the systems you trust Agents become participants
live fabric connected
FinCal APIproducer
Sentinelwatcher
channelmarket.calendardurable · addressable
Agentsubscriber
Workflowsubscriber
Applicationsubscriber
market.calendar.updateddelivered to 3 subscribers
now
01 / thesis

Your systems do not need another brain. They need a shared nervous system.

02 / the model

Stop wiring every new intelligence directly into everything else.

Point-to-point integrations multiply. Agent frameworks come and go. Vesper inserts a stable layer between producers and consumers so each side can evolve independently.

01

Channels, not glue code.

Give useful information and capabilities a durable address. Producers publish once; authorized consumers participate without creating another bespoke coupling.

ops.settlement12 participants
02

Agents become participants.

Let an agent observe, reason, and act around the same shared fabric as ordinary software. The model can change without forcing the integration topology to change with it.

03

Keep what already works.

Start with the API, database, scheduled job, or SaaS workflow you already have. Add a bridge at the boundary instead of rebuilding the source system around the latest protocol.

03 / how it moves

One useful signal. Many possible consumers.

1
connectExisting system

API, database, job, service

2
publishNamed channel

A stable place for the signal

3
coordinateAgents + software

Observe, reason, react

4
extendNew capability

Without rewiring the source

04 / vesper engineer

The bridge builder is part of the product.

The hard part is rarely inventing another protocol. It is understanding the system you already have, finding the smallest safe seam, and turning that seam into a useful connection.

01

Integration designer — maps systems, boundaries, and the right channel shape.

02

Bridge builder — helps turn APIs, jobs, databases, and services into participants.

03

Deployment + safety reviewer — keeps credentials, approvals, and failure modes visible.

Vesper Assistant
powered by assistant-ui

Product-aware demo. Connect your own endpoint for live model responses.

05 / principles

Designed for the messy middle.

Vesper is most useful where real businesses live: old systems beside new agents, dependable jobs beside experimental models, and valuable data that was never designed to be “agent-ready.”

01

Incremental by default.

Connect one useful capability first. Earn the next integration.

02

Model-neutral.

Design the fabric so the intelligence at the edge can evolve.

03

Observable boundaries.

Prefer named channels, explicit bridges, and inspectable behavior.

04

Humans stay in the loop.

High-consequence actions should make approval and accountability visible.

06 / begin

Start with one system that should be easier for intelligence to reach.

Do not replace it. Connect it.

Vesper / legal

Terms of Service

Effective July 9, 2026

1. Acceptance

These Terms govern services provided by Calapi Inc. (“Calapi,” “we,” “us,” or “our”), including Vesper websites, software, APIs, assistants, and related services (collectively, the “Services”). By accessing or using the Services, you agree to these Terms. If you use the Services for an organization, you represent that you are authorized to accept these Terms for that organization.

2. Service status

Vesper is evolving software. Features may change, be suspended, or be discontinued. Unless a separate written agreement says otherwise, the Services are provided on an “as available” basis and no uptime, support, or service-level commitment is implied.

3. Your systems and credentials

You are responsible for the systems, data, credentials, instructions, and permissions you connect to the Services. Use least-privilege credentials, review agent actions, and do not provide access that exceeds the task you intend the Services to perform.

4. Acceptable use

You may not use the Services to violate law, infringe rights, gain unauthorized access, disrupt systems, distribute malware, or conceal harmful activity. You may not attempt to bypass technical limits or security controls protecting the Services or other users.

5. AI-assisted output

Assistant output can be incomplete or wrong. You remain responsible for reviewing outputs and for decisions or actions taken using them, especially where financial, legal, operational, security, or safety consequences are material.

6. Intellectual property

You retain rights in content you provide. Calapi Inc. and its licensors retain rights in the Services, software, branding, documentation, and other materials provided by Calapi, including the Vesper name and associated brand assets. These Terms do not transfer ownership of either party’s intellectual property.

7. Disclaimer and limitation

To the maximum extent permitted by law, the Services are provided without warranties of merchantability, fitness for a particular purpose, non-infringement, or error-free operation. Liability is limited to the extent permitted by applicable law. A separate signed agreement may replace this section for paid or enterprise use.

8. Changes

These Terms may be updated as the Services evolve. Material changes will be reflected by a revised effective date or other reasonable notice.

Vesper / legal

Privacy Policy

Effective July 9, 2026

1. Scope

This policy explains how Calapi Inc. (“Calapi,” “we,” “us,” or “our”) handles information when you visit the site or use Vesper software, APIs, assistants, and related services (collectively, the “Services”).

2. Information collected

Depending on how you use the Services, Calapi may process account information, contact details, authentication metadata, service configuration, prompts and assistant interactions, diagnostic logs, usage records, and technical data such as browser, device, and network information.

3. How information is used

Information may be used to provide and secure the Services, authenticate users, operate connected integrations, troubleshoot failures, prevent abuse, understand product performance, communicate about the Services, and comply with legal obligations.

4. Connected systems

When you connect a third-party system, Calapi may process data needed to perform the integration you configure. You are responsible for ensuring you have authority to provide that access and for selecting appropriate permissions and retention settings.

5. Service providers

Calapi may use infrastructure, analytics, security, communications, and AI model providers to operate the Services. Information is shared only as reasonably necessary for those functions or as required by law. Provider-specific terms may also apply where you choose or supply a model.

6. Retention and security

Information is retained for as long as reasonably needed for the purposes described here, subject to operational, contractual, and legal requirements. Calapi uses reasonable safeguards, but no system can guarantee absolute security.

7. Your choices

You may request access, correction, or deletion of personal information where applicable. You can also limit data exposure by using scoped credentials, minimizing connected data, and avoiding sensitive information that is unnecessary for the task.

8. Contact

Privacy and legal questions may be sent to contactus@calapi.ai.

9. Changes

This policy may be updated as the Services evolve. Material changes will be reflected by a revised effective date or other reasonable notice.