t23d API vs Tripo — Text to 3D Model Generator

Evaluating the t23d API vs Tripo for your pipeline? PixelAPI's text3d-v1 converts any text prompt into a production-ready GLB mesh for $0.015/model — true pay-per-call, no monthly subscription, no credit bundles to pre-buy. POST a prompt, poll for completion, download your 3D file. 500 free credits, no credit card required.

Quick start — text prompt to GLB in one API call

Sign up, copy your key from the dashboard, and POST your prompt. The endpoint returns a job_id immediately; poll GET /v1/3d/text-status/{job_id} until status=completed, then download the GLB from output_url.

curl -X POST https://api.pixelapi.dev/v1/3d/text-generate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "prompt=a red leather office chair with chrome legs" \
  -F "resolution=128"
# Response: {"id": "uuid", "status": "queued", "poll_url": "/v1/3d/text-status/uuid", ...}

# Poll until completed (~75s)
curl https://api.pixelapi.dev/v1/3d/text-status/UUID \
  -H "Authorization: Bearer YOUR_API_KEY"
# Response: {"status": "completed", "output_url": "https://...model.glb"}

pip install pixelapi
---
import time
from pixelapi import PixelAPI

client = PixelAPI(api_key="YOUR_API_KEY")

# Submit generation
job = client.text_to_3d(
    prompt="a red leather office chair with chrome legs",
    resolution=128,
)

# Poll until done
while job.status != "completed":
    time.sleep(5)
    job = client.get_3d_status(job.id)

job.save("chair.glb")  # downloads the GLB

npm install pixelapi
---
import { PixelAPI } from "pixelapi";

const client = new PixelAPI({ apiKey: process.env.PIXELAPI_KEY });

const job = await client.textTo3d({
  prompt: "a red leather office chair with chrome legs",
  resolution: 128,
});

// SDK polls automatically
const result = await job.waitForCompletion();
await result.save("chair.glb");

composer require pixelapi/pixelapi
---
<?php
use PixelAPI\Client;

$client = new Client(getenv("PIXELAPI_KEY"));
$job = $client->textTo3d([
    "prompt"     => "a red leather office chair with chrome legs",
    "resolution" => 128,
]);

// Poll until completed
do {
    sleep(5);
    $status = $client->get3dStatus($job->id);
} while ($status->status !== "completed");

file_put_contents("chair.glb", file_get_contents($status->output_url));

gem install pixelapi
---
require "pixelapi"
require "open-uri"

client = PixelAPI::Client.new(api_key: ENV["PIXELAPI_KEY"])
job = client.text_to_3d(
  prompt: "a red leather office chair with chrome legs",
  resolution: 128
)

loop do
  sleep 5
  status = client.get_3d_status(job.id)
  break if status.completed?
end

File.binwrite("chair.glb", URI.open(status.output_url).read)

go get github.com/pixelapi/pixelapi-go
---
import (
    "time"
    "github.com/pixelapi/pixelapi-go"
)

client := pixelapi.New("YOUR_API_KEY")
job, err := client.TextTo3D(pixelapi.Text3DParams{
    Prompt:     "a red leather office chair with chrome legs",
    Resolution: 128,
})
if err != nil { panic(err) }

for job.Status != "completed" {
    time.Sleep(5 * time.Second)
    job, err = client.Get3DStatus(job.ID)
    if err != nil { panic(err) }
}
job.Save("chair.glb")

t23d API vs Tripo — Pricing and Feature Comparison

PixelAPI is the only text-to-3D generator with a true pay-per-call REST API — no subscriptions, no seat limits. Rivals require monthly plans before your first API call.

Pricing verified from each rival's public pricing page in May 2026. PixelAPI rivals use subscription-based billing that bundles monthly credits — per-model costs depend on plan tier and usage volume. PixelAPI's $0.015 is a flat pay-per-call rate with no monthly commitment.

What you get back

Every successful generation returns a signed download URL for a binary GLB file. The same URL is also stored in your account's generation history for 30 days.

API reference — endpoints

Request parameters — POST /v1/3d/text-generate

Common workflows

The text-to-3D API is the foundation for these production pipelines. Each links to a full setup guide:

Integrations

Comparison vs alternatives

Rate limits & error handling

3D generation jobs run concurrently, not sequentially. The rate limit governs concurrent active jobs, not requests per second.

• Free tier: 10 concurrent 3D jobs, 60 req/min across all endpoints
• Paid tiers: 30 concurrent 3D jobs by default; higher limits on request
• 429 Too Many Requests: retry after the Retry-After header value (seconds)
• 504 Gateway Timeout: generation timed out after 300s — credits are auto-refunded
• 402 Payment Required: insufficient credits — top up via dashboard

Recommended polling strategy: check every 5 seconds for the first 60 seconds, then every 10 seconds up to 5 minutes. The Python and Node SDKs implement this automatically with waitForCompletion().

# Python: poll with backoff
import time
from pixelapi import PixelAPI

client = PixelAPI(api_key="YOUR_API_KEY")
job = client.text_to_3d(prompt="a wooden treasure chest", resolution=128)

interval = 5
for _ in range(60):          # max ~5 minutes
    time.sleep(interval)
    status = client.get_3d_status(job.id)
    if status.status == "completed":
        status.save("chest.glb")
        break
    if status.status == "failed":
        raise RuntimeError(f"Generation failed: {status.error_message}")
    interval = min(interval * 1.5, 15)  # gentle backoff

Frequently asked questions