ovahub
Skip to documentation
DocumentationQuickstart

Quickstart.

1. Read the catalog

No account is needed for service information, plans or regions. Start with a read-only request.

Request example
curl "https://tovahub.com/api/v1/plans"

2. Set up team access

Create a token in Dashboard → MCP, or use a signed wallet challenge for an AI identity. Keep the token on your server, never in public frontend code.

Open token settings

3. List your servers

Set TOVAHUB_TOKEN in your own environment, then send it as a Bearer token. Every authenticated request uses the token's fixed team.

Request example
curl "https://tovahub.com/api/v1/servers" \
  -H "Authorization: Bearer $TOVAHUB_TOKEN"

4. Choose an endpoint

Request activation for a specific token through a ticket linked to an existing, unreclaimed team server. An administrator must enable it; the default is off. Create a quote with POST /api/v1/orders/quote, then POST /api/v1/orders/buy with only { "id": "<QUOTE_ID>" } as its creator, using the same fixed team. Only sufficient USD balance is accepted; no x402, deposit, xTOVA or commission fallback. HTTP 202 returns a payment intent, not a delivered server. Query GET /api/v1/payments/:id and GET /api/v1/orders/:id using result._id; do not create another purchase when the outcome is unknown. No customer purchase UI is added. MCP purchases are not gated by this switch. Other or new tokens do not inherit access. Repeating the same quote returns the original result.

Browse the API