Arclode lets you make things with AI — pictures, video, 3D models, and writing — without owning any special gear. You describe what you want, and it gets made for you.

Two things you can do

• Make stuff. Type what you want and get back an image, a short video, a 3D model, or text. You only pay for what you make.
• Earn money. Got a decent computer? Let it pitch in on this AI work for other people while you’re not using it, and get paid. It only runs the jobs you allow, and you can switch it off any time.

Why it works this way

Most AI companies answer demand by building another warehouse full of computers. Arclode uses the ones people already own instead. That keeps costs down and puts the money with regular people, not just the big companies.

How to start

Sign up for a free account. Then pick a side: make things, earn, or both. Same account either way.

Arclode is an AI service with two sides that share one account. On one side you make things with AI — images, video, 3D models, and text — through the app or one simple API. On the other side, a computer you already own can earn by taking on AI work for other people when you’re not using it.

One service, two sides

Most AI tools make you bring your own expensive hardware, or pay a flat subscription whether you touch it or not. Arclode works the other way around:

• Use it. Sign up and start making right away. You pay for what you actually generate: no subscription, no idle hardware bill. Work in the app, or wire the same capabilities into your own product with one API.
• Earn from it. Install a small app and your computer picks up AI jobs in the background while it’s idle. It only takes the work you allow, and you can stop it any time. You’re paid for the real work your machine finishes.

The idea behind it

The AI industry keeps answering demand by building bigger data centers. Arclode takes the opposite bet: plenty of capable hardware already exists, sitting idle in gaming PCs, Macs, and other machines most of the day. Putting that spare capacity to work keeps AI cheaper, and sends the earnings to the people who own the machines instead of a handful of very large data centers.

One balance, shared with Zatabase

Arclode runs on the Zatabase platform, so you get one identity and one balance across both sides. Credit you earn as a provider lands in the same balance you spend as a builder. Top up when you want more, or let what you earn cover what you make.

Start on either side. It’s the same account and the same app, and you can do both.

Arclode is a generative-media service: one REST API, native SDKs on top, and a hosted app, all backed by a network of machines that do the actual compute. This is the version for people who want to know why it’s shaped this way, not just what the endpoints are. For the exact request and response shapes, see the docs.

Why one API with SDKs on top

Every SDK wraps the same hand-written core, so the language bindings can’t drift from the wire. That’s a deliberate choice against auto-generated clients, which tend to rot the moment the server moves. Use the SDK for whatever language you’re already in, or skip it and call the HTTP API with nothing but fetch. Same surface either way.

Why jobs are async

You submit a job describing the kind of generation and its input, and you get back an id, not a result. Then you either poll for the outcome or subscribe to a stream of progress events.

The reason is honest about what’s underneath: generation is slow, and it runs across a distributed set of machines that vary in speed and availability. Holding a connection open for a minute-long render on someone’s idle GPU is the wrong model. An id you can poll — or a stream you can follow, drop, and reconnect to — survives a flaky client and a busy network. A finished job hands back durable URLs for everything it produced, so the result outlives the request that made it.

Why capabilities are discoverable

The set of generators the network can run isn’t fixed. It grows as providers come online with new hardware and models. So clients ask the API what’s available rather than hardcoding a list, which means a new generator can show up on the network and existing clients route to it without shipping new code.

Credits and the two-sided part

Keys draw down a shared credit balance, and that balance is the seam between the two halves of Arclode: the credit a builder spends is what a provider earns for running the work. As a builder you never touch the supply side directly, but it’s what puts capacity on the other end of every call. That’s the whole point of building on contributed hardware instead of standing up another data center.