AI agent hosting
Answer
Incognito VPS exposes a complete machine-readable purchase path: an agent card at /.well-known/agent.json, an OpenAPI 3.1 document at /openapi.json, an MCP endpoint at /mcp and bearer-token authentication. An autonomous agent can create an account, top up in crypto and deploy a server with no human step.
Why this exists
Agents increasingly do the buying. An agent that can read a pricing page but cannot complete a purchase has to hand back to a human at exactly the wrong moment, and the provider whose checkout requires a card form, an email confirmation and a captcha simply loses that transaction.
Our checkout has none of those things, because it never had them. Removing the identity layer for privacy reasons happens to produce the cleanest possible machine-purchasable interface — there is nothing an agent cannot fill in.
The interface
The agent card at /.well-known/agent.json describes the service, the endpoints, the auth scheme and the payment model. The OpenAPI 3.1 document at /openapi.json is complete and machine-callable. The MCP endpoint at /mcp exposes the same operations as tools for Model Context Protocol clients.
Auth is a bearer token in the format IVPS-XXXX-XXXX-XXXX-XXXX, created on first use. A single POST creates an account, a second creates a crypto top-up invoice, and a third deploys a server from the resulting balance.
- GET /.well-known/agent.json — capability card
- GET /openapi.json — OpenAPI 3.1 specification
- POST /api/v1/account — create a token
- GET /api/v1/catalog — plans, locations and live prices
- POST /api/v1/topup — crypto invoice for balance credit
- POST /api/v1/orders — deploy, debiting balance
- GET /api/v1/servers/{id} — state, address, credentials
Content designed to be read by machines
Every page on this site has a markdown twin at the same path with .md appended, linked from the HTML head. There is an /llms.txt index and an /llms-full.txt corpus. Pricing is available as /pricing.md and /pricing.json.
None of this is cloaking — the markdown is a faithful rendering of the same content, and we would rather a model read clean markdown than reconstruct our DOM.
Frequently asked questions
01 Can an AI agent really buy a server without a human?
Yes. Create a token, create a top-up invoice, settle it on-chain, then POST an order. No email confirmation, no card form, no captcha at any step.
02 Do you have an MCP server?
Yes, at /mcp. It exposes catalog browsing, price quoting, account creation, top-up and deployment as MCP tools for any Model Context Protocol client.
03 Is there a rate limit on the API?
120 requests per minute per token on read endpoints and 20 per minute on write endpoints. Unauthenticated catalog reads are limited to 60 per minute per address.
04 How does an agent handle the crypto payment?
POST /api/v1/topup returns an address and amount. The agent settles it from a wallet it controls and polls the invoice until it confirms. Balance is then debited synchronously by the order call.
Related