Stellar Testnet only. No real money moves. What this means

Stellar Split developer docs

Stellar Split splits shared expenses in a group and settles the debts in USDC (or EURC, when the server enables it) on Stellar Testnet, wallet to wallet. The app never holds money or keys. These docs cover the REST API, the MCP server for agents, and how to verify payments on chain.

Testnet only

Everything here runs on Stellar Testnet. Test tokens have no value. The API refuses to start with another network and checks the Horizon network passphrase before it verifies a payment.

What you can do

  • Sign in with a Stellar wallet: the API issues a SEP-53 challenge, your wallet signs it, you get a 12-hour bearer session.
  • Create groups, add members by Stellar address, and create invite links.
  • Record expenses with equal or exact splits. An Idempotency-Key header makes retries safe.
  • Read balances and suggested transfers (who pays whom).
  • Settle a debt in two steps: reserve a settlement intent, pay it from the wallet with the intent memo, then record the transaction hash. The API verifies the payment on Horizon before it records it.
  • Read a photo of a receipt into a draft expense (demo feature, needs a Gemini key on the server).
  • Link an agent account to your account with a signed message, so the agent can pay your debts within server-side spend caps.
  • Give an AI agent (Hermes, OpenClaw or any MCP client) tools to list groups, read balances, record expenses, propose settlements and, when a signer is configured, pay.

Base URL

https://stellar-split-sooty.vercel.app/v1

All routes live under /v1. The web app and the API share one origin on Vercel. A health check needs no auth:

curl -sS https://stellar-split-sooty.vercel.app/v1/health
# {"status":"ok","network":"testnet"}

Architecture

The browser signs with Freighter and sends payments straight to Stellar Testnet. The API stores the off-chain ledger in Supabase and checks every settlement against Horizon. Agents reach the API through an MCP server that holds the agent's credential, so the model never sees it.

Stellar Split architecture The web app with Freighter calls the API, which stores data in Supabase and verifies payments on Horizon. Payments go from the wallet to Stellar Testnet directly. An agent in Telegram calls the MCP server, which calls the API with the agent token and can submit payments to Horizon. Web appReact + Freighter wallet API /v1Node on Vercel functions Supabaseoff-chain ledger Stellar TestnetHorizon, USDC / EURC AgentHermes or OpenClaw, Telegram MCP serverholds agent token, signer session + JSON service role verify tx signed payment MCP, MCP_AUTH_TOKEN agent token payment
Architecture diagram

Where to go next

Last updated 26 October 2026Edit this page on GitHub