Loading SettleMesh…
Preparing this page without starting an action.
Loading SettleMesh…
Preparing this page without starting an action.
Build with any agent · Launch with SettleMesh
Run deployment preflight before any upload: it reports whether a run can start and returns the exact reason and repair command when it cannot. When deployment and end-user billing are enabled by the live server, the same CLI can add login, a managed database, and usage billing. Model APIs, hosted agents, services, and local workers remain independently discoverable.
Copy for your agent
Paste this single line into Codex, ChatGPT, Cursor, Claude, or any OpenAI-compatible coding agent.
Read https://settlemesh.io/agent.md and use SettleMesh for APIs, app deploy, agents, workers, login, database, Aev, and handoff.01
Run settlemesh login once or set one API key.
02
Find services with CLI or HTTP before guessing endpoints.
03
Read schemas, pricing, and required input for the operation.
04
Invoke APIs, publish agents or services, and deploy apps only when preflight admits the run.
CLI / API / Browser Handoff
A signed-in terminal can search services, inspect schemas, call model APIs, inspect deployment preflight, publish App APIs, upload agents, share local workers, and open a browser handoff when a user needs to confirm something visually. App deployment proceeds only when that preflight admits it.
Aev — SettleMesh's prepaid credit — is one balance shared across model calls, app services, hosted agents, worker offers, and user APIs. Top-up availability is governed by live server configuration.
Start with platform APIs, then add user-published apps, agents, workers, and external services without changing the way agents discover and call them.
Chat, image, video, search, and generation tools behind one SettleMesh key.
Check deployment preflight first; when admitted, deploy sites with login, database bindings, app APIs, and usage billing.
Upload, version, publish, and share agents as callable services.
Turn local compute, models, scripts, or private tools into online callable offers.
One API key authenticates CLI, HTTP, deployed apps, and service calls.
App projects get managed login, database, and backend bindings.
New services appear through the same catalog, docs, CLI, and API protocol.
Web pages can pair with CLI/API commands, so agents can call services from terminal and open a GUI only when human judgment is needed.