Platform API

One host. Your whole company.

Banking, cap table, accounting, formation and documents — served as gRPC services behind a single address, for the people and the agents building on Lovie.

• Live
• Transport gRPC-Web
• Auth Bearer JWT
• Agents MCP
• Terminal CLI

Transport

The edge in front of this host speaks HTTP/1.1 and HTTP/2, but does not carry gRPC's h2c framing, so gRPC-Web is the transport to use.

Authentication

Every gRPC route is gated at the edge. Send a Clerk-issued JWT on each call:

authorization: Bearer <clerk-jwt>

A missing or invalid token is rejected before it reaches a service — you get 401 with a WWW-Authenticate: Bearer header, not a gRPC status.

Agents authenticate differently, and they get their own host: the MCP server at https://mcp.lovie.co is exempt from edge JWT so a client can complete an anonymous handshake, and performs per-tool OAuth itself. Nothing on this hostname is reachable without a token.

Quickstart

import { createClient } from "@connectrpc/connect";
import { createGrpcWebTransport } from "@connectrpc/connect-web";
import { TransactionService } from "@lovieco/api/lovie/transaction/v1/transaction_service_pb";

const transport = createGrpcWebTransport({
  baseUrl: "https://api.lovie.co",
  httpVersion: "1.1",
  interceptors: [
    (next) => async (req) => {
      req.header.set("authorization", `Bearer ${token}`);
      return next(req);
    },
  ],
});

const client = createClient(TransactionService, transport);
const { transactions } = await client.getListTransactions({ pageSize: 25 });

Agent surface

347 operations across 25 services are exposed to AI clients over MCP, discovered live from the running services — 38 of them callable without a sign-in. This is the agent-callable subset; the full gRPC contract lives in the protos, and what is reachable at this edge is an explicit allowlist.