Use the GPU you already own
Advertise available GPU memory, supported models and processing performance to the network.
Put your GPU to work when you are not using it. Spin-Up AI Worker turns spare hardware capacity into a productive asset, rewarding qualifying completed jobs with AI Credits while helping provide accessible, affordable compute across the distributed AI network.
Beta notice: Spin-up AI Worker and the distributed network are currently in active testing. Features, compatibility, credits and availability may change, and service interruptions or defects should be expected.
Loading live network activity…
Hardware owners make spare compute available. Spin-Up AI matches that capacity with AI jobs, measures completed work and credits contributors—while customers gain another route to run AI workflows without relying only on high-cost centralized APIs.
Connect a compatible Windows machine running local AI models through Ollama.
Choose when your machine may accept work and pause it whenever you need your hardware.
The network matches supported model work with an available worker and leases the assignment.
Your local model performs inference and reports the result and performance measurements.
Qualifying completed jobs can earn credits for your own future distributed AI calls.
AI Worker gives you local control over availability, models and participation while it connects your machine to the wider Spin-Up AI network.
Advertise available GPU memory, supported models and processing performance to the network.
Define weekly availability and exceptions so contribution happens on your terms.
Earn usage credits from qualifying jobs and spend them on future distributed AI calls.
Pause, resume or drain the worker and see its current jobs and network status from the local dashboard.
Discover installed Ollama models, pull supported models and test local inference before accepting jobs.
Track token counts, response time and tokens per second for completed inference work.
A public network of contributed machines can expand available capacity and reduce dependence on premium centralized API calls for suitable AI workflow tasks.
Use community-provided capacity for supported work where a premium API is unnecessary.
Draw from a growing network rather than depending on compute from a single provider.
Route compatible workflow steps to available workers as network capacity changes.
Combine multiple AI jobs into broader workflows coordinated through Spin-Up AI.
Both options use the same inference endpoint. Live mode holds the connection briefly for a completed response; queued mode returns immediately so your application can check it later.
Set waitSeconds to keep the request open. If work finishes in time, the response includes the generated content.
curl -X POST \
"{API_BASE_URL}/api/v1/inference?waitSeconds=30" \
-H "Authorization: Bearer sk-aiw_..." \
-H "Content-Type: application/json" \
-d '{
"model": "gemma4:12b",
"input": "What is the capital of Australia?"
}'
# Completed within 30 seconds:
# { "requestId": 10, "status": "Completed",
# "response": { "content": "Canberra" } }
Omit waitSeconds for an immediate queue response, then retrieve the request by its returned ID.
# 1. Submit the request
curl -X POST \
"{API_BASE_URL}/api/v1/inference" \
-H "Authorization: Bearer sk-aiw_..." \
-H "Content-Type: application/json" \
-d '{"model":"gemma4:12b","input":"Explain async/await"}'
# Response: { "requestId": 11, "status": "Queued" }
# 2. Retrieve its current status or result
curl "{API_BASE_URL}/api/v1/inference/11" \
-H "Authorization: Bearer sk-aiw_..."
{API_BASE_URL} with your Spin-Up API address, such as your local or published API host.requestId to retrieve the result later.Join the community-powered network, earn credits from qualifying work and help make distributed AI more affordable.
Usage credits are not money or investments. Monetary contributor rewards are planned for a future programme and are not currently guaranteed.