Je ninahitaji MCP client?

Hapana. Hii ni REST ya kawaida kupitia HTTPS — inayoweza kutumika kutoka curl, lugha yoyote, au agent inayozungumza HTTP. Kama unatumia MCP, vitendo vilevile vimefunuliwa kama zana (angalia connect guide).

Auth inafanyaje kazi?

Piga /auth/register kupata Bearer token (hakuna nenosiri). Itume kama header Authorization: Bearer kwenye kila authenticated call. /products ni ya umma.

Fadhili salio la awali kupitia /balance/topup (hurudisha crypto checkout URL; lipa kwa USDC/USDT). order kisha hutoa kutoka salio. Kama halijafadhiliwa, order hurudisha ankara unayolipa kupitia /invoices/{id}/pay.

Order response ina nini?

Ama paid_from_balance na service id (utayarishaji umeanza), au ankara ya kulipa. Poll GET /services/{id} hadi status iwe active, kisha soma SSH host, port, na nenosiri la root la mara moja.

Agiza VPS kwa API calls 4 (REST quickstart kwa agents)

Huhitaji MCP client kuendesha EQVPS — REST API hufanya kila kitu agent inachohitaji. Base URL: https://api.eqvps.com/api/v1/eqvps. Hii ndio mtiririko mzima katika calls nne.

0. (mara moja) Fadhili salio la awali

Ili kuagiza kuwe call moja, fadhili salio kwanza. Lipa checkout iliyorudishwa kwa USDC/USDT:

curl -s -X POST https://api.eqvps.com/api/v1/eqvps/balance/topup \
  -H "Authorization: Bearer <YOUR_BEARER>" -H "Content-Type: application/json" \
  -d '{"amount": 25}'
# → { "checkout_url": "https://payram.eqvps.com/..." }  ← ilipe kwa USDC/USDT

1. Register → Bearer token

curl -s -X POST https://api.eqvps.com/api/v1/eqvps/auth/register \
  -H "Content-Type: application/json" \
  -d '{"first_name":"Ada","last_name":"Agent","email":"ada@example.com"}'
# → { "token": "<YOUR_BEARER>", "token_type": "Bearer", "user": {...} }

Hakuna nenosiri, hakuna hatua ya mwanadamu. Hifadhi token; itume kama Authorization: Bearer <YOUR_BEARER> hapa chini.

2. Orodhesha mipango → chagua product + os_id (public)

curl -s https://api.eqvps.com/api/v1/eqvps/products
# → { "data": [ { "slug": "<product-slug>", "price": {...},
#       "specs": {...}, "available_os": [ { "id": <os_id>, "name": "Ubuntu 24.04" }, ... ] }, ... ] }

Chagua plan slug na os_id kutoka available_os ya mpango huo.

3. Agiza VPS

curl -s -X POST https://api.eqvps.com/api/v1/eqvps/orders \
  -H "Authorization: Bearer <YOUR_BEARER>" -H "Content-Type: application/json" \
  -d '{"product":"<product-slug>","os_id":<os_id from list_plans>,"ssh_key":"ssh-ed25519 AAAA..."}'
# → imelipwa kutoka salio: { "paid_from_balance": true, "service_id": <id> }
#   au halijafadhiliwa:    { "invoice": { "id": <id> } }  → lipa: POST /invoices/{id}/pay → checkout_url

Pitisha ssh_key (public key) kwa root login ya key-msingi. Na salio lililofadhiliwa oda inalipwa papo hapo na utayarishaji unaanza.

4. Soma ufikiaji

curl -s https://api.eqvps.com/api/v1/eqvps/services/<service-id> \
  -H "Authorization: Bearer <YOUR_BEARER>"
# → { "status": "active", "access": { "host": "...", "port": 22, "command": "ssh root@..." },
#     "password": "<imeonyeshwa mara moja kwa keyless servers>" , ... }

Poll hadi status iwe active. access block ina SSH host, port, na command ya ready-to-paste; kwa oda ya keyless nenosiri la root la mara moja hurudishwa kwenye read ya kwanza.

Kumbuka kwa agents

Tuma Authorization: Bearer <YOUR_BEARER> kwenye kila call isipokuwa /products.
Lipa kwa USDC/USDT (Base, Ethereum, Tron) — hakuna kadi inayohitajika. Pendelea salio la awali ili hatua 3 iwe call moja.
Vitendo nyeti (order, reset-password, reinstall, cancel) vimewekewa rate-limit; matumizi ya kawaida yako ndani ya mipaka kabisa.
Unapendelea zana kuliko HTTP ghafi? Vitendo vilevile ni zana za MCP — angalia connect guide na tools reference. Nyaraka kamili: /docs.