Quickstart
Integrate in minutes: point your OpenAI-compatible SDK at our baseURL.
Authentication
Every call carries your key in the Authorization header. Keys start with mt_live_ and are shown only once at creation.
Authorization: Bearer mt_live_...Endpoint
POST https://www.tokenrecarga.com.br/api/v1/chat/completions
GET https://www.tokenrecarga.com.br/api/v1/modelsExamples
curl https://www.tokenrecarga.com.br/api/v1/chat/completions \
-H "Authorization: Bearer mt_live_..." \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-flash",
"messages": [{"role": "user", "content": "Olá!"}]
}'Streaming
Pass stream: true and receive standard OpenAI SSE. Billing stays correct even if the connection drops mid-response.
Response headers
Every response reports the data destination region and the metering origin.
x-mt-data-regionCountry this call's data was sent to (LGPD transparency)
x-mt-vendor · x-mt-supplierModel vendor and the supplier this call was routed through
x-mt-cost-brl · x-mt-balance-brlCost of this call and remaining balance, in BRL (non-stream responses)
Errors
Errors follow the OpenAI format: HTTP 401 invalid key, 402 insufficient balance, 429 rate limited, 502 provider failure.