Overview
What PierNode is and how it is put together.
PierNode is an API-first platform for AI media generation. You integrate against one REST API, and PierNode handles authentication, metering, billing and the asynchronous work of running generations.
How a request flows
- You create an API key in the PierNode console.
- Your application calls the API with that key.
- PierNode prices the request and reserves the cost from your balance.
- The generation runs asynchronously.
- You poll the task until it finishes, then download the result.
Results are collected by polling. There is no webhook callback for generations; if you need one, poll from a background job and notify yourself.
What is available
| Product | Input | Output |
|---|---|---|
| Text to image | prompt | image |
| Image to image | uploaded image + prompt | image |
| Text to video | prompt | video |
| Image to video | uploaded image + prompt | video |
The two image-driven products take an image you have uploaded and refer to it by id. PierNode does not fetch images from URLs you supply.
What is not available
Being explicit about the edges, so you do not design around something that is not there:
- No webhooks. Poll the task.
- No streaming or partial results. A task is pending until it is finished.
- No batch endpoint. One generation per request.
- No cancellation once a task is processing. See cancelling.
- One API key per account. Rotating replaces it immediately.
Providers
Which model runs a generation is PierNode's concern, not yours. The API exposes no provider, model or checkpoint selection, and none appears in a response. That is deliberate: it keeps your integration stable while the machinery behind it changes.