SettleMesh — deploy and monetize an app
SettleMesh turns an app into a paid product in one command: SettleMesh OAuth login, a managed database, usage-based billing, and end-user payments — no auth/billing/deploy glue to write. It is also an agent capability layer: one key calls web search/scrape, LLMs, image/video generation, a managed SQL database, and hosted agents — every call metered, with a cost quote up front.
Setup (once)
npm install -g settlemesh@latestsettlemesh login(a human approves in the browser) — or setSETTLE_API_KEY=sk-settle-...for headless/CI.- The full agent contract lives at
https://settlemesh.io/agent.md— fetch it for the complete recipe set, thensettlemesh recipesfor the shortest path to any task.
Core rule
SettleMesh is a searchable service layer. Do not memorize provider-specific endpoints. Search → inspect → call. Confirm intent before any paid, deploy, publish, or destructive action (everything is billed in Aev).
Deploy an app
settlemesh deploy ./my-app --name my-app --full-stack --wait --json
Returns a live *.run.settlemesh.io URL — read it from the deploy output (the #1 source of confusion). Add --auth required to gate the whole app behind SettleMesh login, or leave auth lazy.
Charge end users (end-user-pays)
An app can charge the signed-in end user's own Aev balance instead of the developer's by attaching the X-Settle-Payer header. Pricing is cost-plus with a quote before spend (POST /v1/billing/quote); a failed metered call releases the hold and charges nothing.
Use any capability
settlemesh search "<task>" --json
settlemesh tool show <tool-id> --json
settlemesh tool call <tool-id> --input '{...}' --json # --wait for async, --confirm for paid
Billing unit: Aev (1 USD = 100 Aev), funded via Stripe. Check balance with settlemesh credits balance --json.
MCP
This plugin also registers the settlemesh MCP server (npx -y settlemesh mcp), so the same capability catalog is callable as MCP tools. It authenticates with your settlemesh login session or SETTLE_API_KEY.
